> What I don't understand is whether or not jaws.xml is required/used for > JBoss3.0, which is EJB2.0 compliant. > Actually this file looks quite similar to jbosscmp-jdbc.xml. Do we need to > deploy both files for JBoss3.0?
no, it should be one or the other. What I'm not 100% clear on is what happens if some beans are cmp2 and some are cmp1.... > PS. Here's what I found on a message from Jboss user list: > > "Things to watch out for when switching to CMP2.0 features: > Use jbosscmp-jdbc.xml instead of jaws.xml, > if your EBs use EJB2.0 (jaws.xml is silently ignored)." > > So my suggestion for XDoclet engine will be, to NOT include in "jaws.xml" > entity beans CMP2, because these definitions will be ignored by JBoss. Maybe > give some kind of error messages if cmp-version="2.x" and jaws-specific tags > were used. It's just a suggestion, see if that makes sense for you also. the architecture at the moment doesn't involve looking at every tag, so this isn't really possible atm... the way it works is that a template (or tag handler) says "give me this tag" and either gets it or doesn't. it would be a nice feature though... for now, I'll try to implement the jboss ejb-ql order extension tonight, and finally get around to turning off jaws.xml generation for cmp2 builds. Then we'll just have to make sure everyone knows about the cmp1.1/cmp2 differences with jboss tags... cheers dim _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
