users@jaxb.java.net

automaticNameConflictResolution and -XautoNameResolution

From: <emiddio_at_frontier.com>
Date: Tue, 27 Aug 2013 15:42:23 -0700 (PDT)

 \com\sun\tools\xjc\Options.java
has field automaticNameConflictResolution that can be set true when
“–XautoNameResolution” is passed as command line arg to XJCTask or XJCTask2.
I see in
debugger conflicted names getting a ‘2’ appended at their end.

But I get
exceptions after
com.sun.tools.xjc.model.CElementInfo.getSqueezedName (CElementInfo.java:254)
returns the same name already used.

At
com.sun.tools.xjc.generator.bean.ObjectFactoryGeneratorImpl.populate (ObjectFactoryGeneratorImpl.java:191)
a collision is detected.
My elementFactoryNames map has 4 members and the
CElementInfo ei trying to be added has an ei.getSqueezedName() ==
"GetFullDataRetrievalResponse" matching one in the map – but that ei
also has an ei.type.fullName() value of  "javax.xml.bind.JAXBElement <com.att.felix.ccrt.GetFullDataRetrievalResponse2>"
so this element got a modified name due to automaticNameConflictResolution
boolean.

Is there a bug
or incomplete support of –XautoNameResolution at this time ?

I am working
with jaxb ri 2.2.7 sources .

Thanks
-Gary