-
1. Re: Nukes on JBoss 3.2.1/Tomcat 4.1.24
julien1 Jun 18, 2003 7:13 PM (in response to mirill)we plan to migrate to tomcat as soon as 3.2.2rc2 at least is bundled with it.
julien -
2. Re: Nukes on JBoss 3.2.1/Tomcat 4.1.24
mirill Jun 18, 2003 7:21 PM (in response to mirill)
Ok. When you bundle with jboss 3.2.2rc2 it will work with JBoss 3.2.1/Tomcat 4.1.24 or will I have to upgrade to that version.
David. -
3. Re: Nukes on JBoss 3.2.1/Tomcat 4.1.24
julien1 Jun 18, 2003 9:43 PM (in response to mirill)it won't work because some class name have changed :-( from 3.2.1 to 3.2.2rc2
-
4. Re: Nukes on JBoss 3.2.1/Tomcat 4.1.24
theravednh Jul 9, 2003 7:37 AM (in response to mirill)Can it be made to work with 3.2.1 merely by removing the duplicate commons library from the nukes deployment, or do the problems run deeper than that?
/david -
5. Re: Nukes on JBoss 3.2.1/Tomcat 4.1.24
julien1 Jul 9, 2003 8:25 AM (in response to mirill)I don't know I did not try yet.
I am going to do the switch as soon as rc2 is out.
Maybe you can try and give us part of your experience. if you have issues, post them and I will answer.
julien -
6. Re: Nukes on JBoss 3.2.1/Tomcat 4.1.24
theravednh Jul 9, 2003 1:25 PM (in response to mirill)Yes - removing the commons-collections.jar (& deployment info) from nukes.ear at least allows startup & deployment without errors.
(Clearly I've had to mess around with the entity-command package names to get the HEAD build to run against 3.2.1, but I couldn't find a CVS tag for the 3.2.1 alpha release. Was there one?)
As to correct operation - well I'm working off MySQL and cannot yet get everything to run smoothly against it, so I'll let you know...
/david