A wise old hermit known only as Sebastien BLANC <[EMAIL PROTECTED]> once said:
> just found the pb. it is not in the xdoc header but after the header: > removing > the comment between the end of the header and the class declaration > generates a > correct ejb name without the pacakge. looks like a bug in the parsing 2 > me > though. I tried 2 '*' at the end of the header to see if any change, > but no. let me know if this can be corrected. Not a bug, as far as I know - I believe the javadoc specs say that the javadoc comments must *immediately* precede the class declaration. If you run the standard javadoc tool over the files, do the class level comments show up in the generated API documentation? According to <A HREF="http://java.sun.com/j2se/1.4/docs/tooldocs/solaris/javadoc.html";> javadoc - The Java API Documentation Generator </A>, "Placement of comments - Documentation comments are recognized only when placed immediately before class, interface, constructor, method, or field declarations ... A common mistake is to put an import statement between the class comment and the class declaration. Avoid this, as the Javadoc tool will ignore the class comment." Andrew. > * @bes:message-driven-destination name="serial://jms/TL1EventTopic" > * @bes:connection-factory > name="serial://jms/TL1EventTopicConnectionFactory" > * > */ > > // can put a generic name to be used on tl1-entity layer > > public class FacTL1SubscriberMDB extends TL1SubscriberMDB > { ------------------------------------------------------- This SF.NET email is sponsored by: Order your Holiday Geek Presents Now! Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap, MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
