RE: [JBoss-user] JBoss 3.0.0beta CMP Problem

[James Higginbotham]

Title: Message

Brent,   Not sure about the first issue, since I have yet to port a 2.0 CMP to JBoss. But, for the manifest issue, we hit this. There was a bug in the deployer for beta 1 (available via sourceforge for download). When I did an anon CVS checkout of jboss-all (see the developer docs on the jboss site for instructions on checkout and building) and built, the bug went away. The version in CVS is called 'beta 2' for all intents and purposes, though no one would respond for the release date of beta 2 to the sourceforge file modules section.   Note that when you extract and build beta 2, you cannot talk to EJBs from within an embedded tomcat servlet engine, though everything else seems to work fine. I'm waiting for this one to be fixed before I can complete my porting to JBoss from weblogic. Scott Stark, the CTO, mentioned that this will be done by end of week, and I'm anxiously waiting....   HTH, James -----Original Message----- From: Taylor, Brent [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 11, 2002 4:33 PM To: '[EMAIL PROTECTED]' Subject: [JBoss-user] JBoss 3.0.0beta CMP Problem It does not appear that JBoss 3.0.0beta is compliant with EJB 2.0. Specifically, the CMP contract. I've defined my Entity Bean as abstract per the EJB 2.0 specification, and JBoss pukes when it tries to deploy it.   Also, the JAR manifest entries for Class-Path are not being honored since JBoss mangles the JAR names when it expands the EAR file during deployment. If I want all my beans to be able to use my 'utilities.jar' package I put that in each manifest Class-Path for each bean JAR. However, JBoss will rename that jar file to 70-utilities.jar or something when it extracts it from the EAR. Anybody else have similar problems?