Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: JiBX 1.2.1
-
Fix Version/s: JiBX 1.2.2
-
Component/s: core
-
Labels:None
-
Environment:Windows Vista (but I think this is not relevant)
-
Number of attachments :
Description
The CodeGen generates the valid-binding.xml file for the very simple test schema Family.xsd, but the binding compiler gives up giving this error:
—
Error running binding compiler
-
-
- Error during code generation for file 'valid-binding.xml' - please enter a bug report for this error in Jira if the problem is not listed as fixed on the online status page ***
-
org.jibx.runtime.JiBXException: Conflicting mappings for class PersonType
at org.jibx.binding.def.DefinitionContext.addMapping(DefinitionContext.java:214)
at org.jibx.binding.def.BindingBuilder.unmarshalMapping(BindingBuilder.java:1814)
at org.jibx.binding.def.BindingBuilder.unmarshalMappings(BindingBuilder.java:1128)
at org.jibx.binding.def.BindingBuilder.unmarshalBindingDefinition(BindingBuilder.java:2103)
at org.jibx.binding.Utility.loadBinding(Utility.java:314)
at org.jibx.binding.Utility.loadFileBinding(Utility.java:431)
at org.jibx.binding.Compile.compile(Compile.java:212)
at org.jibx.binding.ant.CompileTask.execute(CompileTask.java:248)
... omissis ...
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Assignee | Dennis Sosnoski [ dsosnoski ] | |
| Fix Version/s | JiBX 1.2.2 [ 15120 ] | |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
The problem here lies in the generated code going into the default package, so that the type name (PersonType) is the same as the class name (PersonType). The generated binding uses the type name for an abstract mapping, and uses the class name for a concrete mapping - hence the conflict.
I've changed the code to use a default package name "dflt" for no-namespace schema components, which avoids this issue. A better solution will have to wait for 2.0.