This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ JDK VERSION : J2SE 1.4.2_02 ] There is no way to add an external classpath via the ide to the tomcat application. You have to edit setclasspath or catalina directly to solve this. I have an external jar file that I can't copy to the webapps \lib folder. In 3.5 I simply edited the start application of tomcat, and added my classpath to the tomcat's jar files.
I agree what this can be a problem, however cannot be you problem solved by putting the jars into shared or common libs directories where are the jars loaded by common classloaders?
In this special case the problem can't be solved like that because the jar files require native dll's in their folder, that are dynamically loaded. So if I move the jar files, they can't find these dll's. Maybe I solve the problem via setting my system classpath to that jar.
An additional consideration: what do you do to make this work in your production environment? I think we should be looking for a fix that works in both the development and production environments. I think this should be reclassified as "enhancement".
In production environment I have a modified version of setclasspath.(bat/sh) My first thought was, that when on tomcat starts the setclasspath file is modified, but this would be a global setting and not a project setting. In Netbeans 3.5.1 there is an option (under Runtime, Installed Server, Tomcat, Internat Tomcat) calles External Execution Process. There I put my additional classpath after -classpath. But I can't find that option in 3.6. Generally I do not know, how Tomcat is started now (maybe via catalina?) Thanks for your ideas.
Yes, now the catalina.[bat/sh] is used.
*** Issue 40154 has been marked as a duplicate of this issue. ***
*** Issue 23574 has been marked as a duplicate of this issue. ***
Issue based on 3.6, closing. Please reopen if the bug is applicable for NetBeans 6.5.