| Summary: | JAXB Externalized Metadata: Schema gen incorrect for self ('.') xml-path | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | David McCann <david.mccann> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 308677 | ||||||
| Attachments: |
|
||||||
Created attachment 169525 [details]
Contains fix + test case mods
Reviewed by matt.macivor@oracle.com Unit tests pass as expected; jaxb/externalizedmetadata/mappings/composite/CompositeMappingTestCase The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
The schema generator does not process the self ('.') xml-path correctly. For example, if Employee had a self mapping to Department, where department had two string properties deptId and deptName, we would expect the following in the generated XSD file: ... <xsd:complexType name="employee"> <xsd:sequence> <xsd:element name="deptId" type="xsd:string" minOccurs="0"/> <xsd:element name="deptName" type="xsd:string" minOccurs="0"/> </xsd:sequence> </xsd:complexType> ... But instead we get: ... <xsd:complexType name="employee"> <xsd:sequence> <xsd:element name="department" type="ns0:department" minOccurs="0"/> </xsd:sequence> </xsd:complexType> ...