OK, my apologies.
The spec does explicitly state that constant names specified by the
customization may not be altered, although other names (such as property
names/class names) are altered according to the Java naming convention.
The RI is inconsistent with the spec with this regard, but because this
affects the default code generation, I'm not sure if we can fix this in
the 1.0.x branch.
Fortunately, you can work around this problem by using
<globalBindings enableJavaNamingConvention="false"/>
which would turn off the name alteration altogether.
Hope that works.
regards,
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net