Hi Jakub, Implementing the <javadoc> tag is pretty straight forward but unfortunately I never found time to work on it this year. Here is what needs to be done:
- Use the new Binding file object model which contain the Javadoc element: I have it as well with a slighlty modified schema to include the enumration binding but it is not ready to be committed. However if you are interested in implementing the feature we can coordinate efforts. - When generating code, ask for each XMLBindingComponent processed the javadoc that is related for this field (needs adding an XMLBindingComponent#getJavaDoc() which first looks at the binding file and then at the Annotation element). That's all! Feel free to contact me if you need more information, Arnaud > -----Original Message----- > From: JAKUB PIECZONKA [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 26, 2003 4:36 PM > To: [EMAIL PROTECTED] > Subject: [castor-dev] javadoc tag in binding file > > > I noticed this item on the todo list for binding files. Is > anyone working on this? Is there an estimated completion date? > > Adding <annotation><documentation/></annotation> tags > everywhere in the schema is not something I would like to do > for every element that I want documentation for. The schema > would bloat up way too much, and I would prefer to keep a > layer of separation in place between the actual schema and > the documentation. > > Has anyone come up with an interim solution until the javadoc > tag is implemented? Has anyone investigated how much work > this feature will require? > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
