JAR conflicts

Question

I have a web application in Tomcat, and in the classpath of Tomcat there are already many jar files (spring, struts, commons-logging, mail, etc). In this web application I want to install a servlet that uses a new version of struts, but the problem is that there is already another servlet that should continue using an old version of struts. How can I handle with this situation?

Answer 1

duffymo wrote:
strict wrote:
paulcw wrote:
Make two different web applications and put the struts jars in the separate lib directories under each?These two servlets should be in the same web apps.
But I notice that Tomcat has a version of commons-collections-3.1.jar in its common/lib directory, and spring also uses a commons-collections. What if spring uses a different version of this jar that conflicts with the one in Tomcat?
>
>Make two different web applications and put the struts jars in the separate lib directories under each?These two servlets should be in the same web apps.
you duplicate two servlets in several web apps? violates " don't repeat yourself"
No. I mistyped. I meant two servlets in the same web app (in the singular, not plural)
But I notice that Tomcat has a version of commons-collections-3.1.jar in its common/lib directory, and spring also uses a commons-collections. What if spring uses a different version of this jar that conflicts with the one in Tomcat?that's what osgi solvesActually, I read the Tomcat documentation, and I see that such a conflict is impossible, although there are another kinds of jar conflicts, described in that documentation. But this specific conflict (spring dependency jars with tomcat jars) is not possible. Thank God!