OK, this might be bad. I can get it to deploy using the 3.0 and 2.0 attributes, but I get a ClassCastException for the code that is called...(worked fine in the previous XDoclet). I have had to hack the ejb and jboss templates to allow the ejbspec of 1.1 to generate all things MDB related. Can this be changed? Letting the templates allow ejbspec 1.1 to generate MDB tags if they are there? Don't most containers that support 1.1 also support MDB's?
Jim On Fri, 27 Sep 2002, Jim Birchfield wrote: > We have just started using Xdoclet 1.2 (been using older versions since > EJBDoclet) to generate our ejb descriptors. We are deploying to JBoss > 2.4.6. Here is the oddity. When I set the ejbspec to 1.1 ejbtask and the > version to 2.4 in the jboss subtask (which is required if you put less > than 3.0 in the jboss subtask) our message beans do not get included in > the reulsting ejb-jar.xml. Technically, MDB's are not part of 1.1, but a > lot of containers supported them, including JBoss. I can only generate > MDB entries in my ejb-jar.xml file if I up the ejbspec to 2.0 which in > turn makes me up my jboss version to 3.0. So far it actually seems to > work, but it might not in all containers. > > So, it is not really a bug, but might cause problems in some containers > that are not 2.0 compliant, but support MDB's. > > Jim > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
