Hi David,
The generated classes themselves contain javadoc describing the
relationship between your schema and the generated code. Does that help?
Regards,
--
Ed Mooney |Sun Microsystems, Inc.|Time flies like
Java Web Services |UBUR02-201 |an arrow, but
Ed.Mooney_at_Sun.COM |1 Network Drive |fruit flies like
781-442-0459 |Burlington, MA 01803 |a banana. Groucho
David Halonen wrote:
> One thing that seems to be missing is a high-level presentation of the XML nonsense and how it relates to java nonsense.
>
> In particular:
> XML has this notion of an "element". What does this mean in java? Is this simply a class?
>
> XML has this notion of attributes. What is an attribute in java? A member field?
>
> What is the difference between a simple element & an attribute in java land? Can they be used interchangably? What are the consequences?
>
> The <sequence> tag seems to dictate the element must have the set of elements in the order specified. This is for the marshalled objects. Sometimes, the elements are not required. The comment element in the sample app PO comes to mind. If this is not required, can it then be an attribute?
>
> Conversely, if an attribute is required, why not just make it a required element?
>
> I understand that XML is pretty "rich", which to me means it can be very complicated. The existing JAXB documentation seems to be wanting to point out all the glorious things this technology can do, but it doesn't clearly discuss the impedance mis-match between java & xml (naming conventions notwithstanding). A precise reference manual is useful and the users guide gets one started, but is it reasonable to ask for some discussion of the tradeoffs of the various implementations?
>
> (This is my personal perspective.) Is it possible to construct documentation that doesn't require an advanced degree in mathematics? The spec is very, very dense and I'm just trying to get a job done. Perhaps there is some other place one can turn to for assistance in deciphering this?
>
> TIA.
>
> David Halonen
> Compuware