dev@jaxb.java.net

Re: name algorithm changes

From: Joe Fialli <Joseph.Fialli_at_Sun.COM>
Date: Mon, 11 Jul 2005 15:27:52 -0400

Kohsuke Kawaguchi wrote:

> Ryan Shoemaker - JavaSoft East wrote:
>
>> Ryan Shoemaker - JavaSoft East wrote:
>>
>>> Kohsuke,
>>>
>>> I noticed that some of my J2S unit tests are failing because of
>>> post-EA2 naming changes.
>>
>>
>> Looks like this diff is the culprit. I'm not going to modify any
>> of my tests until we get concensus on whether or not this is the
>> correct name algorithm.
>
>
> Sekhar requested that we use BeanIntrospector instead of our smarter
> algorithm. I preferred to keep using the smarter algorithm, but I believe
> Sekhar said using BeanIntrospector would simplify the spec.
>
> But I don't know if Sekhar was aware of this consequence.
>
> I'll wait for the spec guys to chime in...
>
I agree with what is specified in Section 8.12.1 in public draft of
specification.
Minimizing the java id to XML name transformation as much as possible
is desirable.
The XML Name to Java identifier conversion is complex in order to map XML
names to standard Java source code naming conventions. I am not aware of an
equivalent XML naming convention that is universally accepted by
entire XML community.

The method java.beans.Introspector.decaptialize is only called on
Java components that are typically capitalized by source coding standards,
namely JavaBean accessor property name, class and enum type name.
It seems natural to undo the standard Java naming convention of capitalizing
class and property names (within getter/setters).

-Joe