2 main versions of JBoss: 2.4 and 3.0.
2.4 only supports EJB spec 1.1.
3.0 supports EJB spec 1.1 through JAWS and EJB spec 2.0
The problem is that when you specify JBoss 3.0, it wasn't
examining the EJB spec to determine which JBoss plugin to
use, it was just generating both a jaws.xml and a
The patch checks to see which EJB spec *and* the bean's
CMP version to determine whether the EJB goes into the
jaws.xml or jbosscmp-jdbc.xml file.
Here is a quick reference to the rules:
x.x 1.1 x.x EJB goes in jaws.xml
2.4 2.0 x.x <exception - not supported>
3.0 2.0 1.x EJB goes in jaws.xml
3.0 2.0 2.x EJB goes in jbosscmp-jdbc.xml
- added code to ensure that if there is at least one CMP 1.x
bean, a jaws.xml file is created
- added code to ensure that if there is at least one CMP 2.x
bean, a jbosscmp-jdbc.xml file is created
- added a check to ensure that only CMP 1.x beans are
placed into the jaws.xml file
- added convenience methods to see if there is at least one
CMP 1.x or CMP 2.x bean
jboss_cmp_version_part_1.patch covers JBoss files and
jboss_cmp_version_part_2.patch covers EJB files.
Also, a messages file was added for JBoss specific error