Re: AW: [sdo] ISSUE: 133 Refactor Section 4.

Hello All,

Following up from last weeks call and the discussion points raised by Ron, below is the EclipseLink thinking on SDO-133:

II ISSUE 133: Refactoring the chapter "Generating Java from XMLSchemas" 
http://www.oasis-open.org/apps/org/workgroup/sdo/email/archives/200808/msg00003.html

a) Do we want to specify that there is an XSD->Java code generation tool (like xjc in JAXB)
I consider section "4 Generating Java from XML Schemas" sufficient for covering this topic.  Although I think the part starting with "Frequently creation of annotations is done automatically..." can be safely removed.

Also the following paragraphs should be re-worked:

FROM:  "When customizing the default mapping, SDO annotations are added to the schema. This is called an Annotated Schema (AS). The AS is used to generate the Java. The annotated purchase order schema could be called poAS.xsd. The AS is important because all SDO implementations using the same AS would produce the same Java interfaces as defined in the Java code generation section."
TO:    "When customizing the default mapping, SDO annotations are added to the schema. This is called an Annotated Schema (AS). The AS is used to generate the Java. The annotated purchase order schema could be called poAS.xsd. The AS is important because all SDO implementations using the same AS would produce the same Java interfaces (for the annotated sections) as defined in the Java code generation section."

FROM:  "Frequently creation of annotations is done automatically by a code generation tool. In this case the XSLT and AS may be hidden within the implementation of the tool. This is very
convenient in practice because the code generation tool can produce intelligent overrides and customizations in a product-specific fashion without creating any extra files or overhead."
TO:  "Code generators may provide behavior (in a product-specific fashion) equivalent to annotations to automatically solve such problems as naming conflicts."