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

Implement JAXB / XJC support for XML Schema version 1.1 (XSD) #1176

Open
Tomas-Kraus opened this issue Apr 12, 2018 · 25 comments
Open

Implement JAXB / XJC support for XML Schema version 1.1 (XSD) #1176

Tomas-Kraus opened this issue Apr 12, 2018 · 25 comments

Comments

@Tomas-Kraus
Copy link
Member

This issue was previously reported via https://bugs.openjdk.java.net/browse/JDK-8197490

A DESCRIPTION OF THE REQUEST :
This enhancement request is to improve Java code generation for XML Bindings in order to support version 1.1 of XML schemas.

JUSTIFICATION :
XSD 1.1 was published in 2012 and we still have no way to support it with JAXB.

Reference:
https://www.w3.org/TR/xmlschema11-1/

An example of limitation this brings to Java is when trying to implement RFCs which use XSD 1.1 features. Ex: RFC 7852 "provided-by.xsd"

provided-by.xsd; lineNumber: 43; columnNumber: 55; cos-nonambig: "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo":EmergencyCallData.ProviderInfo and WC[##other:"urn:ietf:params:xml:ns:EmergencyCallData"] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.

This is acceptable with XSD 1.1.

CUSTOMER SUBMITTED WORKAROUND :
I could not find any workaround. One would need to give up xml bindings and start using Xerces to be able to validate against XSD 1.1.

@Tomas-Kraus
Copy link
Member Author

@PiotrKlimczak Commented
+1

@Tomas-Kraus
Copy link
Member Author

@svaningelgem Commented
+1

@Tomas-Kraus
Copy link
Member Author

@martindbrown Commented
+1

@Tomas-Kraus
Copy link
Member Author

@allam001 Commented
+1

@Tomas-Kraus
Copy link
Member Author

@easmith Commented
+1

@Tomas-Kraus
Copy link
Member Author

@tsaker
Copy link

tsaker commented Oct 25, 2018

+1

7 similar comments
@flann
Copy link

flann commented Nov 14, 2018

+1

@Mrc0113
Copy link

Mrc0113 commented Nov 15, 2018

+1

@lkamb
Copy link

lkamb commented Mar 6, 2019

+1

@Romlengrd
Copy link

+1

@lecogiteur
Copy link

+1

@jlholland
Copy link

+1

@gline9
Copy link

gline9 commented Dec 9, 2019

+1

@rolpaul
Copy link

rolpaul commented Dec 13, 2019

+1
it is in the top ten voted issues of this project, I guess

@asselmeyer
Copy link

+1

@LanceAndersen
Copy link

LanceAndersen commented Dec 13, 2019 via email

@gallyamb
Copy link

Any progress on this issue?

@m0mus
Copy link
Member

m0mus commented Feb 12, 2020

No, unfortunately there is no progress. If you want to contribute a PR we would appreciate it.

@khrysenthem
Copy link

+1

@senderic
Copy link

I'm also interested in this. Any update on progress?

@tomzi8571
Copy link

I can see there has been no progress on this so far - Do you guys know of any other ways to compile java source from xsd 1.1? Does anyone have experience with https://github.com/jaxsb/jaxsb ?

@Bukama
Copy link

Bukama commented Aug 24, 2022

There are (at least) two issues for this: this (#1176) and #994.

Aside from my duplication information: I would really like to see support for XSD 1.1 in JAXB.

@ktor
Copy link

ktor commented Mar 6, 2023

+1

@sacps001119
Copy link

+1

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

No branches or pull requests