Hi,
I've been having a look at the work required to migrate our J2EE 1.3
application from 1.1.2 to 1.2.
The main issue I've run into so far is that xdoclet seems to be
insisting that we specify the cmp-version in each of our entity beans
now, although it was not needed before.
Is there a logical reason for this?
The piece of xdoclet code that is problematical is in
xdoclet.modules.ejb.entity.CmpTagsHandler.isUsingCmp2Impl.
If this function behaved as described in it's javadoc, I think that all
would be fine with us, but it instead throws the exception with
XDocletModulesEjbMessages.CANT_GUESS_CMP_VERSION.
Is this a bug that should be fixed, or a deliberate change in behaviour?
Note that we don't use the <entitycmp> task, as it does not appear
useful for CMP2 work.
Thanks,
Steve Coy
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
