-
Notifications
You must be signed in to change notification settings - Fork 111
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
Comments
@PiotrKlimczak Commented |
@svaningelgem Commented |
@martindbrown Commented |
@allam001 Commented |
@easmith Commented |
|
+1 |
7 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1
On Dec 13, 2019, at 10:07 AM, Christian ***@***.***> wrote:
+1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#1176?email_source=notifications&email_token=ABQPFOZE756YKDDNHUKHUMTQYOQMPA5CNFSM4FWSH2E2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG2HOMI#issuecomment-565475121>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQPFO65R5HZEP4UZQSJF4LQYOQMPANCNFSM4FWSH2EQ>.
My best,
Lance
--
Lance Andersen
USTA EMA President and CEO
PTR Professional 5A
USPTA Elite Professional
TIA Global Cardio Tennis-Master Trainer
USRSA
Mobile: 978 857-0446
luckydogtennis.com -- luckydogtennis.com/TennisBlog -- cardiotennis.com
|
Any progress on this issue? |
No, unfortunately there is no progress. If you want to contribute a PR we would appreciate it. |
+1 |
I'm also interested in this. Any update on progress? |
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 ? |
+1 |
+1 |
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.
The text was updated successfully, but these errors were encountered: