Dear all We as a group have been developing a system based around JMS and a set of independent EAR applications. These apps have been developed independently to a degree and were also run on different instances of JBoss.
Now that we are trying to deploy on less servers in an environment closer to that which we will use we have noticed many of the problems listed above with regard to the class loader. We currently unjar resource libs into our deployed jar (to get round the Digester problem) and various things like that. We ideally need to be able to control what sort of class loader structure we use. As we communicate using JMS we won't really get much benefit from the UnifiedClassLoader (I guess although correct me if I'm wrong) and it causes headaches with version classes and config information. Any news on a solution or the end approach that will be taken in JBoss 3.0.0 would be appreciated. Cool product though Regards Chris Mein * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66&thread=13076 _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
