You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run the xjc with this, I got some error related to schemaBindings not being applied to anything (in french below) :
com.sun.istack.SAXParseException2: La personnalisation "jaxb:schemaBindings" n'est associée à aucun élément de schéma.
If I do it in debug mode, I see that I go inside this part of the com.sun.tools.xjc.reader.internalizer.Internalizer#buildTargetNodeMap function
if(schemaLocation.equals("*")) {
for(StringsystemId : forest.listSystemIDs()) {
result.computeIfAbsent(bindings, k -> newArrayList<>());
result.get(bindings).add(forest.get(systemId).getDocumentElement());
Element[] children = DOMUtils.getChildElements(bindings, Const.JAXB_NSURI, "bindings");
for (Elementvalue : children)
buildTargetNodeMap(value, forest.get(systemId).getDocumentElement(), inheritedSCD, result, scdResult);
}
return;
}
Problem
The problem is listSystemIDs() returns my 3 XSD + my binding file, in which this binding will not be applied...
Analysis
If I remove the call to result.get(bindings).add(forest.get(systemId).getDocumentElement()); for the systemId of binding file, generation is OK with expected behavior : generated elements are prefixed with My and ends with Dto as defined in binding file)
Is it normal that we treat the binding file as one of elements of bindings to be applied ?
The text was updated successfully, but these errors were encountered:
Context
I've got 3 XSD + 1 binding file (
bindings.xjb
) which contains the following :Behavior
When I run the xjc with this, I got some error related to schemaBindings not being applied to anything (in french below) :
If I do it in debug mode, I see that I go inside this part of the
com.sun.tools.xjc.reader.internalizer.Internalizer#buildTargetNodeMap
functionProblem
The problem is
listSystemIDs()
returns my 3 XSD + my binding file, in which this binding will not be applied...Analysis
If I remove the call to
result.get(bindings).add(forest.get(systemId).getDocumentElement());
for the systemId of binding file, generation is OK with expected behavior : generated elements are prefixed withMy
and ends withDto
as defined in binding file)Is it normal that we treat the binding file as one of elements of bindings to be applied ?
The text was updated successfully, but these errors were encountered: