| WTP 1.0+ Classpath Change publishing to Tomcat. [message #158913] |
Fri, 03 February 2006 16:07 |
 Alex Townsend
Messages: 4
Registered: July 2009 |
Junior Member |
|
|
Our product requires a lower version of the servlet API than is current in most of todays application servers. This is done because we have coded to a lowest common denominator version and wish to continue having this compatibility. Unfortunately there has been a recent change in the WTP which makes it impossible for us to upgrade to the latest version to do our development. This change modifies the order of the classpath such that the tomcat endorsed directories are searched before the WTP defined classpath.
Prior to/including WTP 0.7 the classpath specified by the runtime came AHEAD of tomcats directories (as they do if the jars were published to the WEB-INF\lib directory of a real tomcat installation). This made it very handy to leave our jars in their respective repository, include them into each project's build path and export them up a chain. After creating a server profile all we had to do is simply run the profile once to create a launcher runtime entry, edit that entry and add the web project to the classpath under User Entries, add our -D argument to the startup line to allow it to find our products configuration and run... everything was working nicely and then 1.0 came out. I've tried this on every version greater than 7.0 and all of them seem to exhibit this change in classpath policy.
Does anyone know of a way to fix it so that the classpath under the WEB-INF\lib is loaded ahead of the Tomcat endorsed directories?
|
|
|
Powered by
FUDForum. Page generated in 0.03588 seconds
] 
Search
Help
Register
Login
Home
