A wise old hermit known only as Rupp,Heiko <[EMAIL PROTECTED]> once said:
> It looks like this came from the fact that in the EB, the > import statement for the Class (javax.ejb.EntityBean) was > before the Xdoclet attributes, while in the Session Beans, > this import was after the comment section. For the compiler > this does not matter, but for Xdoclet. And also for javadoc (that's how it's mandated by the javadoc spec/API, we just conform to their rules). Javadoc class-level comments should immediately precede the "public class Foo" declaration, not be before the imports, nor before the package statement, nor after the class declaration, etc. I don't know, you'll be expecting XDoclet to warn you when you've used "/*" instead of "/**" next... (now there's an idea for an enhancement request :-)) Andrew. ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
