Binding compile of two classes with same element name fails with NPE in NameAttributes.equals although output only

I have the same problem, but I'm not restricted to marshalling.

Basically, I have a small 'control' file containing some metadata and a related (possibly very large)
'data' file, both using the same element name. Most important, the control file contains the path
to the data file.

<binding value-style="attribute">
<mapping name="foo" class="FooControl">
<value name="path" field="pathToData"/>
</mapping>

<mapping name="foo" class="FooData">
<!-- lots of stuff here -->
</mapping>
</binding>

A server application feeds control files to my program, and using the contained path my program knows where to
find the real data. So when I read/write an XML file, I know exactly what class to unmarshal to/marshal from, and
simply use two IBindingFactory instances to read and write both kind of files:
IBindingFactory controlFactory = BindingDirectory.getFactory(FooControl.class);
IBindingFactory dataFactory = BindingDirectory.getFactory(FooData.class);

This works great with JiBX 1.0.2.

1.1.3 complains:

Error: Duplicate mapping name not allowed for unmarshalling; on mapping element at (line 6, col 37, in binding.xml)
Error running binding compiler
org.jibx.runtime.JiBXException: Binding binding.xml is unusable because of validation errors
at org.jibx.binding.Utility.loadBinding(Utility.java:346)
at org.jibx.binding.Utility.loadFileBinding(Utility.java:413)
at org.jibx.binding.Compile.compile(Compile.java:296)
at org.jibx.binding.Compile.main(Compile.java:385)

1.1.5 fails with the NullPointerException from the original bug report.

This is failing for me as well.

I have been using JIBX Beta 3a in Production for over 2 years without any issues.

I tried upgrading to 1.1.5 and am facing this error. I downgraded to 1.1 and it works for me.

Let me know if any stack trace or testing effort etc is needed.

I've verified that the supplied binding compiles with the current CVS code, after some earlier fixes to the name handling. The test program fails when it tries to create an unmarshaller for the output-only binding (and I've also corrected the error message for this case, which previously had marshaller and unmarshaller reversed).

The problem reported by Ingo Wilken is not really an issue, since the JiBX unmarshalling code correctly requires distinct names for each concrete <mapping> definition. I don't know how this ever could have worked with 1.0.2, but the only way to define multiple <mappings> with the same name now is to use separate binding definitions. If you split your current binding into two, and compile them in a single execution of the binding compiler, that should work.