Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Jaxb2Marshaller to work with EclipseLink MOXy when using external binding definitions [SPR-9757] #14391

Closed
spring-projects-issues opened this issue Sep 5, 2012 · 1 comment
Assignees
Labels
in: data type: enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Sep 5, 2012

Michał Politowski opened SPR-9757 and commented

EclipseLink MOXy supports defining the bindings in an external definitions file instead of using annotations. Currently the Jaxb2Marshaller cannot be used to marshal objects when the binding is defined completely externally, because it checks for the @XmlRootElement annotation.
It would be useful to support this case in Jaxb2Marshaller or possibly a separate marshaller.


Affects: 3.1 GA

Issue Links:

  • #14392 An implementation of AbstractJaxb2HttpMessageConverter that can work with EclipseLink MOXy external binding definitions

Referenced from: commits 682b0f2, bd018fc

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Sep 6, 2012

Arjen Poutsma commented

I think adding a simple property "checkForXmlRootElement" will solve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants