-
Notifications
You must be signed in to change notification settings - Fork 114
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
SCD bindings do not support custom/vendor customization elements #1047
Labels
Comments
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
|
has there been any investigation on this item ? |
laurentschoelens
added a commit
to laurentschoelens/jaxb-ri
that referenced
this issue
Sep 17, 2023
laurentschoelens
added a commit
to laurentschoelens/jaxb-ri
that referenced
this issue
Sep 17, 2023
laurentschoelens
added a commit
to laurentschoelens/jaxb-ri
that referenced
this issue
Sep 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I wrote a number of XJC plugins, some of these plugins can be customized via binding files.
For instance, I can do the following:
If my Jsonix plugin is activated, XJC will know that jsonix:packageMapping is a customization element for Jsonix (plugin API allows saying what your customization namespace URI is and which local names you expect).
SCD seems to be a more advanced way to address schema elements. I.e.
addresses the XLink schema logically via namespace URI. Forget the files, this is perfect. Much more versatile than schemaLocation and node. I guess episodes would not work without SCD in first place. For my scenarios it would for instance help with #1047.
My problem is that SCD does not allow custom elements. So this:
I get the following error:
Clearly, SCD does not process custom configuration elements whereas schemaLocation plus node do process.
The text was updated successfully, but these errors were encountered: