-
1. Re: 3.0.x -> 3.2.x EJB upgrade
adrian.brock Mar 5, 2004 3:21 PM (in response to davekohr)You should not be affected unless you defined your own container configurations.
You may want to take advantage of some of the new features though.
Regards,
Adrian -
2. Re: 3.0.x -> 3.2.x EJB upgrade
davekohr Mar 16, 2004 6:58 PM (in response to davekohr)Thanks for the tip, Adrian. It turns out the problem was with our jboss.xml CMP descriptor. We had mistakenly defined a CMP entity bean with no fields. JBoss 3.0.7 had no problem with that, but deployment in 3.2.3 failed with a null pointer exception. Seems like the kind of thing that should either be accepted gracefully or cause a warning.
I also did some informal testing to see what kinds of problems the deployer can catch, specifically some field/column mismatches between the ejb-jar.xml and jboss.xml descriptors. I recall there are several kinds of mismatches it doesn't catch. It would be a big help to debugging CMP beans if the deployer extensively error-checked all the deployment descriptors. -
3. Re: 3.0.x -> 3.2.x EJB upgrade
adrian.brock Mar 16, 2004 7:10 PM (in response to davekohr)If you have examples, post them as bugs at
www.sf.net/projects/jboss
You can catch some errors by turning on dtd validation for the EJBDeployer
in conf/jboss-service.xml
Also NPE isn't an acceptable error message, post that as a bug as well
(with stacktrace). It should give a "reasonable" error message.
Regards,
Adrian