Hi,
I'm readying a product for public release that is make up of EJB
components. I'm looking for best practises and/or "design patterns" in
documentation of EJB so that the EJB can be easily used by other ISV for
implementing web apps for example. Currently, my team is using the
standard JavaDoc doclet for generating the API reference. Somehow, this
is not appropriate IMHO. For example, for a third party ISV that uses my
company's EJB, they are mostly interested in the home and remote
interfaces. But the doclet generates the HTML for all classes and this
leads to cluttering. In addition, info like JNDI name for each EJB, type
of EJB, transaction attributes, resource ref, security attributes, etc.,
can only be found by looking in the XML deployment descriptor. Is there
a better way? Anyone like to share their way of documenting EJB?
TIA!
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
