Ok the spec does state that the interfaces, implementation and utiltity classes for the adapter should be placed into a jar inside of the rar package. The jbosspool-jdbc.rar does not include its implementation classes and the jms-ra.rar includes them as bare classes.
What is wrong with the RARDeployer adding the rar jars to the server classpath? This simply avoids the duplicate effort of placing the classes into the rar as well as the lib/ext directory. Also, what is your point about not putting info specific to a particular EIS in the rar? xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 01, 2001 3:00 PM Subject: Re: [JBoss-dev] The RARDeployer classpath is broken > The spec as far as I can tell does not support putting bare .class files in > a rar. I'm also not sure it is a good idea. I also think it is > inadvisable to put information specific to a particular EIS instance into a > rar representing a connector for any instance of that EIS system. > > I'd be happy to discuss further how jboss 3 can make your deployment > easier. > > david jencks > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
