Angelina,
I haven't tried it in 0.9.5.3, but in my development branch (which uses
the CVS version) an element with name "New" generates getNew() and
setNew() methods just fine.
I don't recall any changes to the naming algorithms since 0.9.5.3 so it
should work ok, but you may want to try the CVS version instead.
--Keith
> [EMAIL PROTECTED] wrote:
>
> Hello! We are in the process of upgrading from Castor 0.9.3.9 to
> Castor 0.9.5.3. As part of that process we have done extensive
> reworking of our XML schema. I have noticed that one bit of code is
> being generated differently and I was wondering why and if there is a
> known workaround.
>
> What's happening is this. The following schema snippet doesn't produce
> the expected Java code:
>
> <complexType name="APLTaskType">
> <sequence minOccurs="0" maxOccurs="unbounded">
> <element name="Modify" type="apl:ModifyType" minOccurs="0"
> maxOccurs="unbounded"/>
> <element name="New" type="apl:NewType" minOccurs="0"
> maxOccurs="unbounded"/>
> </sequence>
> </complexType>
>
> In APLTaskTypeItem.java, the expected getModify(), enumerateModify(),
> etc. are generated just fine. However, for New we get get_new() and
> enumerate_new(), etc. instead of the expected getNew(), etc. If the
> element name "New" is changed to "Create" or "NEW", it works just
> fine. I figure perhaps we are hitting on some reserved keyword or
> something like that, but I'm not sure. Is this a known issue, or does
> anyone know a good workaround?
>
> Thanks in advance!
>
> -Angelina Talley
>
> ---------------------------------------------------------------
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-user
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
