Bugzilla – Full Text Bug Listing
| Summary: | Overlapping XmlPath mappings to separate bean fails | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Rob McAuliffe <bugs.eclipse.org> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | blaise.doughan | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
To be clear, in the above scenario the bean named 'first' does note contribute to the output, whereas it should. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
Created attachment 208925 [details] A test case that should succeed if merging complex type overlapping XmlPath annotations worked Using Moxy to map two properties of a bean (that are themselves XML beans) to an overlapping path silently drops the deeper mapping. The output XML only contains the shallower mapping XML. For example, @XmlPath("a/b/c") is overridden by another specified @XmlPath("a/b") in the following snippet. Expected is for the elements and attributes to be merged in the same way as @XmlPath(".") does. Snippet: ---------------------------------------------------- @XmlPath("a/b/c") private SomeXmlBean first; @XmlPath("a/b") private SomeXmlBean second; ----------------------------------------------------