Re: [JBoss-user] Bug in JBoss2.2 Auto Deploy ??
Rishabh Misra wrote: > hmmm .. that presents an interesting problem though. > when running embedded Tomcat, how do i separate my Tomcat classpath from > JBoss classpath? > coz i need to have the beans in my Tomcat classpath and that's the > reason i had added them to JBOSS_CLASSPATH (note: NOT my system > classpath though) > > also, why does having the beans in the classpath cause this in the first > place?? This happens because the deployer uses a classloader to read the deployment descriptor. If there is a deployment descriptor in the classpath then the classloader delegation model means that the one in the classpath will always be read in preference to the one in your ejb-jar. I don't know how to deal with your Tomcat problem, I'm sorry. You can probably get away with having only the remote and home interfaces in the classpath. Definitely don't have the ejb-jar in the classpath. Toby. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Bug in JBoss2.2 Auto Deploy ??
Why you need to have the beans in your Tomcat classpath? The JSP/Servlets need only the remote/home classes. That's the reason there should be two jars: one contains everything to deploy EJB, and one for the client (only remote and home of the beans). If you use data objects to transfer buck data from client to beans and vice versa, you also need to add these classes to client jar. Nguyen Thanh Phong Tel: 84-8-837 25 06/837 25 07 Saigon Software Development Company (SDC)Fax: 84-8-837 25 11 10 Co Giang Street, Dist I, HCMC Email: [EMAIL PROTECTED] Vietnam - Original Message - From: Rishabh Misra <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 25, 2001 12:29 PM Subject: RE: [JBoss-user] Bug in JBoss2.2 Auto Deploy ?? > hmmm .. that presents an interesting problem though. > when running embedded Tomcat, how do i separate my Tomcat classpath from > JBoss classpath? > coz i need to have the beans in my Tomcat classpath and that's the > reason i had added them to JBOSS_CLASSPATH (note: NOT my system > classpath though) > > also, why does having the beans in the classpath cause this in the first > place?? > > rishabh > > > hi list, > > > > i just migrated to JBoss 2.2.1 from JBoss 2.0 and suddenly things > > stopped working. i'm getting a javax.naming.NameNotFoundException for > > the JNDI name of my bean. > > > > on closer inspection of the log/server.log file, i noticed the > > following. when i add 2 bean jar files to my deploy folder. it picks > up > > the first bean, but ends up deploying the second. and then picks up > the > > second and deploys it again. > > Do you have the second bean in the system classpath? You should > probably not have anything in the classpath when you start the server. > > Toby. > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > > > NetZero Platinum > No Banner Ads and Unlimited Access > Sign Up Today - Only $9.95 per month! > http://www.netzero.net > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Bug in JBoss2.2 Auto Deploy ??
hmmm .. that presents an interesting problem though. when running embedded Tomcat, how do i separate my Tomcat classpath from JBoss classpath? coz i need to have the beans in my Tomcat classpath and that's the reason i had added them to JBOSS_CLASSPATH (note: NOT my system classpath though) also, why does having the beans in the classpath cause this in the first place?? rishabh > hi list, > > i just migrated to JBoss 2.2.1 from JBoss 2.0 and suddenly things > stopped working. i'm getting a javax.naming.NameNotFoundException for > the JNDI name of my bean. > > on closer inspection of the log/server.log file, i noticed the > following. when i add 2 bean jar files to my deploy folder. it picks up > the first bean, but ends up deploying the second. and then picks up the > second and deploys it again. Do you have the second bean in the system classpath? You should probably not have anything in the classpath when you start the server. Toby. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user NetZero Platinum No Banner Ads and Unlimited Access Sign Up Today - Only $9.95 per month! http://www.netzero.net ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Bug in JBoss2.2 Auto Deploy ??
Rishabh Misra wrote: > hi list, > > i just migrated to JBoss 2.2.1 from JBoss 2.0 and suddenly things > stopped working. i'm getting a javax.naming.NameNotFoundException for > the JNDI name of my bean. > > on closer inspection of the log/server.log file, i noticed the > following. when i add 2 bean jar files to my deploy folder. it picks up > the first bean, but ends up deploying the second. and then picks up the > second and deploys it again. Do you have the second bean in the system classpath? You should probably not have anything in the classpath when you start the server. Toby. ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Bug in JBoss2.2 Auto Deploy ??
hi list, i just migrated to JBoss 2.2.1 from JBoss 2.0 and suddenly things stopped working. i'm getting a javax.naming.NameNotFoundException for the JNDI name of my bean. on closer inspection of the log/server.log file, i noticed the following. when i add 2 bean jar files to my deploy folder. it picks up the first bean, but ends up deploying the second. and then picks up the second and deploys it again. --8<--- [Auto deploy] Auto deploy of file:/D:/Software/jboss/dist/deploy/SecurityJB.jar [J2EE Deployer Default] Deploy J2EE application: file:/D:/Software/jboss/dist/deploy/SecurityJB.jar [J2EE Deployer Default] Create application SecurityJB.jar [J2EE Deployer Default] install module SecurityJB.jar [Container factory] Deploying:file:/D:/Software/jboss/dist/tmp/deploy/Default/SecurityJB.jar [Verifier] Verifying file:/D:/Software/jboss/dist/tmp/deploy/Default/SecurityJB.jar/ejb1001.jar [Verifier] ServerSSB::constructor() [Verifier] ServerSSB: Verified. [Container factory] Deploying ServerSSB ... [Container factory] Bound ServerSSB to es/ServerSSB [Container factory] Deployed application: file:/D:/Software/jboss/dist/tmp/deploy/Default/SecurityJB.jar --8<--- although it started by picking up file SecurityJB.jar (which has a bean called SecuritySSB), the Verifier picks up the second bean ServerSSB and then the Container factory goes on to deploy ServerSSB, and finally binds it to es/ServerSSB (now all this should be SecuritySSB!!!) while claiming that it deployed SecurityJB.jar !! --8<--- [Auto deploy] Auto deploy of file:/D:/Software/jboss/dist/deploy/ServerJB.jar [J2EE Deployer Default] Deploy J2EE application: file:/D:/Software/jboss/dist/deploy/ServerJB.jar [J2EE Deployer Default] Create application ServerJB.jar [J2EE Deployer Default] install module ServerJB.jar [Container factory] Deploying:file:/D:/Software/jboss/dist/tmp/deploy/Default/ServerJB.jar [Verifier] Verifying file:/D:/Software/jboss/dist/tmp/deploy/Default/ServerJB.jar/ejb1002.jar [Verifier] ServerSSB::constructor() [Verifier] ServerSSB: Verified. ... [Container factory] Bound ServerSSB to es/ServerSSB [Container factory] Deployed application: file:/D:/Software/jboss/dist/tmp/deploy/Default/ServerJB.jar --8<--- it then picks up the second bean ServerJB.jar and this time correctly deploys ServerSSB (again!!) and then binds it to es/ServerSSB. the methods that it maps in the first case also belong to the second bean! the files ejb-jar.xml and jboss.xml are absolutely correct ... the same files used to run just fine with JBoss 2.0 does anybody have a clue what might be happening here?? thanx ... rishabh __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
