Keith Visco wrote:
You could add annotations to the schema for your Xdoclet tags. See the following:
http://www.mail-archive.com/castor-user%40exolab.org/msg00394.html
Justin, Keith,
The one catch that I've run into with this approach is that a complexType referenced as a field within another complexType will not have a @castor.class XDoclet tag. For example, let's say you've got two objects named Foo and Bar. Because the Foo element contains an element referencing Bar, there is only an <annotation> containing a @castor.field XDoclet tag. This is correct for the reference to Bar within the Foo object. But when the Source Generator generats the Bar.java class file there is no @castor.class XDoclet tag in the class' Javadoc comment.
So far I've taken to adding them by hand because they're so small and quick. But I really need to find a solution to this dilemma. Possibly a way for the Source Generator to know that a @castor.field XDoclet tag is inappropriate for a class level comment and that a @castor.class element is needed instead. I know that's far fetched and very tightly tied. I'm just throwing out the general idea in hopes that we can collaborate on a solution for this.
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&5R\\"F9E<G)E=\\$\\!F<FEI+F-O;0\\`\\`");'
The Castor Project http://www.castor.org/
Apache Geronimo http://incubator.apache.org/projects/geronimo.html
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
