This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Add an automatic "can this schema be marshaled option | ||
|---|---|---|---|
| Product: | xml | Reporter: | bugbridge <bugbridge> |
| Component: | Schema Tools | Assignee: | Jeri Lockhart <jeri> |
| Status: | NEW --- | ||
| Severity: | blocker | CC: | nvrijn |
| Priority: | P4 | ||
| Version: | 5.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
As mentioned in the Description, this is the 3rd of 3 enhancements dealing with functionality required by "schema librarians." The other two enhancements are issue 78628 and issue 78676. The JAXB 2.0 team mentions that all schema constructs are now supported. In contrast to JAXB 1.x. |
Original status: 3-Accepted; Suggested Status: NEW Original submitter: nvrijn Description: This is the 3rd of 3 RFEs. There should be an option to flag every construct in an XML schema which causes a problem when an attempt is made to generate object marshaling routines in JAXB. As it is, sometimes published schemas are not marshalable (ex: Redefine is used) and it is not apparent until much later when one of the users changes from DOM or SAP to use Java objects directly ... and fails.