Hello, I have been using XDoclet 1.1.2 successfully for many months now for J2EE development. I'm currently trying to upgrade to XDoclet 1.2b3 because I need to use the @jboss:query tag.
However, I am facing a problem when trying to generate my home interface and bean interface files with the new version of XDoclet: XDoclet generates fully-qualified class names for all variables (i.e. value objects used in the bean implementation), but since some of the classes haven't yet been generated, it tries to "guess" the package name based on the package of the current input file. I know one workaround to this is to import fully-qualified classes, but this would involve adding hundreds of lines to hundreds of files. Example Problem: ---------------- The "TransporterBean" is in package "com.maestro.ejb.transporter" The "AddressBean" is in package "com.maestro.ejb.address" The TransporterBean has the following import and method: import com.maestro.ejb.address.*; ... public AddressLocal getAddress(TransporterInfo transporterInfo); Now, when Xdoclet generates the TransporterLocal interface, it incorrectly guesses the package of AddressLocal in the method signature: public com.maestro.ejb.transporter.AddressLocal getAddress(....) Why can't it just leave the return type as is without appending the fully-qualified class name? It would work fine, because I have imported the package at the top of TransporterBean. Any ideas for solving this problem? Many thanks for any help, Aris ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
