interesting... i thought the purpose of the <java> tag was to specify any "non-ejb" jar files that were accessible to the ear (and other applications if the ear was not scoped).
is there anything really wrong w/ just using the <java> tag to expose those jar files? you would have to change deployment descriptors if you stopping using jboss in favor of something else (and why would one ever want to do that) anyway. either way, i'll have to go investigate how the Class-Path in the manifest file works. -jae -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rod Macpherson Sent: Friday, January 09, 2004 3:53 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Where to put the Interceptor .class file? That you can share jars using the <java> module is peculiar to JBoss. I have been down this road before. A java module is an executable java application that accesses EJBs just as the web application module does. Why not define a <jar> module for shared libraries with an EAR? Good question, but as it now stands you have to use Class-Path in the manifest. Seems inconsistent a bit clumsy but that's the way it is. -----Original Message----- From: Jae Gangemi [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 12:04 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Where to put the Interceptor .class file? i've also done the same thing - that's how we deploy our applications. we define everything in the application.xml file so it can be located. is this not the "proper" way to do this? -jae -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Barlow, Dustin Sent: Friday, January 09, 2004 12:07 PM To: '[EMAIL PROTECTED]' Subject: RE: [JBoss-user] Where to put the Interceptor .class file? I successfully deployed a jar within an ear w/o having to set the manifest classpath of other referring jars by putting the following in the application.xml of the ear. <application> <module> <java>foo.jar</java> </module> </application> Dustin > -----Original Message----- > From: Bill Burke [mailto:[EMAIL PROTECTED] > Sent: Friday, January 09, 2004 12:00 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Where to put the Interceptor .class file? > > > You cannot put a jar within an EAR without adding a classpath to the > manifest file You can place the interceptor in a separate JAR outside > the EAR, or in the EJB-jar as well if you rather do that. > > Bill > > Jonathan.O'[EMAIL PROTECTED] wrote: > > > Well, I've learned lots of interesting stuff following the > "Where to put > > an Interceptor class?" thread. However, I should have asked > where does one > > stick the class file,so it gets loaded in time for the > interceptor stack > > to work properly. Will any jar within an EAR do? Or does it > have to be > > placed in the /server/someConf/lib directory? > > Ciao, > > Jonathan O'Connor > > XCOM Dublin > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Perforce Software. Perforce is > > the Fast Software Configuration Management > System offering > > advanced branching capabilities and atomic changes on 50+ platforms. > > Free Eval! http://www.perforce.com/perforce/loadprog.html > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > -- > ================ > Bill Burke > Chief Architect > JBoss Group LLC. > ================ > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Perforce Software. Perforce is the > Fast Software Configuration Management System offering advanced > branching capabilities and atomic changes on 50+ platforms. Free Eval! > http://www.perforce.com/perforce/loadprog.html > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
