My application is completely CMP 2.0. The key is to make sure your DOCTYPE in your ejb-jar is EXACTLY the way it appears on suns DTD.
Jboss checks for that DOCTYPE and if it is different, it reverts back to 1.x On Thu, 2002-04-11 at 15:32, Taylor, Brent wrote: > 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?
signature.asc
Description: This is a digitally signed message part
