Dave,
Until the beginning of this week I was only using
Jbuilder 4.5 to develop with struts. However, I wasn't
able to use the integrated tomcat in this setup. I installed
a separate instance of tomcat and used Jbuilder to compile my
application classes. After compilation, I copied the classes
and JSPs to the tomcat instance that I installed where I did
my testing. Not as efficient as having everything in one place
which I have managed to do with JBuilder 6, but it worked.Chris -----Original Message----- From: Dave J Dandeneau [mailto:[EMAIL PROTECTED]] Sent: Friday, February 01, 2002 11:46 AM To: Struts Users Mailing List Subject: JBuilder 5 ant Tomcat 4 Has anyone gotten jbuilder 5 to work with tomcat 4.0? Dave -----Original Message----- From: Walter De Wit [mailto:[EMAIL PROTECTED]] Sent: Friday, February 01, 2002 11:24 AM To: 'Struts Users Mailing List' Subject: RE: URGENT: XML Confilcts Tomcat 4 fixes this. In Tomcat 4 the XML parser classes used within Tomcat are not visible for the web-apps. I suppose this won't fix your problem but upgrading to Tomcat 4 could be new solution. (which will probably cause new problems ;-) -----Original Message----- From: Dave J Dandeneau [mailto:[EMAIL PROTECTED]] Sent: vrijdag 1 februari 2002 17:16 To: Struts Users Mailing List Subject: URGENT: XML Confilcts Our web application is currently using different XML classes than the ones that are in the tomcat 3.2.1. We are having a hard time getting our new code to reference the correct xml classes when running. Is there a way to configure the classpath of the web application to exclude the classpath of tomcat? We are using the validator. Could the validator jar be causing the conflict? Thanks, dave -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
msg22470/bin00000.bin
Description: application/ms-tnef
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
