The document discusses utilizing JAXB to automatically generate POJOs from an XSD file to map XML content to Java objects. It provides an overview of JAXB and its architecture, describes how it was implemented in a Green Integration project to extract data from XML and map it to POJOs, and notes some limitations of JAXB including its requirement of JDK 1.5 or later.

1. Utilized JAXB to generate POJOs automatically -- Green Integration Part II Albert Guo [email_address]

3. Scenario

4. System Architecture CIS Green Windchill Project Management Document Management Change Management Pro/E Wildfire Pro/E Work Space Pro/E PDMLink Supplier Management GSM Product Management (Part /BOM) Interface Table SAP ERP ProjectLink ODBC xml

5. Where to launch Export BOM to GSM xml

6. XML content example If the part has child, this part will be enclosed by <ProductStructure>. If the part does not have child, then this part will be enclosed by <Line>

7. JAXB (Java Architecture for XML Binding)

9. Architecture JAXB We’ll focus on JAXB instead of Xstream in this material. If you’re interested in Xstream, please refer to Utilized XStrem in Green Integration . XML Spy can do the same thing, but it’s not free solution.

10. Implementation steps in Green Integration

11. Implementation steps in Green Integration Applied JAXB to generate POJOs automatically We can focus on retrieving data and setting them into POJOs. Applied XStream to generate XML file by easy way. Applied Commons IO to write xml content into file Logging service Utility classes Commons Lang

12. JAXB Usage

13. JAXB Usage -- commands xjc.bat -p [package name] [xsd location] -d [code gen destination]

14. JAXB Usage We can use JAXB to generate these POJOs based on xsd file automatically

15. JAXB Limitations

17. Summary

18. Summary Logging service

19. Appendix