Thanks for taking time to explain this.

Werner

Corcuera,Ron wrote:
> Hi Werner,
> 
> Thanks for the quick reply.  I'll open an issue on Jira immediately.
> 
> We created the project in question back in 2003.  Castor 0.9.9 met our
> needs at the time.  Now, though, we are trying to integrate the old code
> to some new code.  This new project is using Castor version 1.1.1.  I
> needed to regenerate the classes in order to work properly with this new
> project.  The problem was also apparent with version 1.1.1.  I thought I
> would try 1.1.2.1 to see if the bug was fixed with this version.  But,
> alas, the same problem exists with the newest version.
> 
> Thanks,
> Ron 
> 
> -----Original Message-----
> From: Werner Guttmann [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, July 29, 2007 7:26 AM
> To: [email protected]
> Subject: Re: [castor-user] Castor 1.1.2.1 not generating choices
> correctly
> 
> Hi Ron,
> 
> looks like you've come across a regression issue with regards to code
> generation and the usage of choices.
> 
> Can I ask you to create a new Jira issue at ...
> 
> http://jira.codehaus.org/browse/CASTOR
> 
> and attach all relevant files, incl. the XML schema in question. Please
> try to keep the files you attach as minimal as possible to ease our job
> when working on issues.
> 
> Your usage is a very special one, and it will helps us to improve the
> Castor CTD test suite (which apparently fails to catch this particular
> issue).
> 
> Regards
> Werner
> 
> PS To my knowledge, it has been a while since functionality related to
> code generation of choices has been changed. Whilst I cannot remember
> top of my head, if an error occurred on our sided, it should have
> happened before release 1.2. As such, I'd be interested to learn why you
> are switching away from Castor 0.9.9 now, and not earlier (e.g. with the
> availibility of Castor 1.1).
> 
> 
> Corcuera,Ron wrote:
>> I am attempting to upgrade from Castor version 0.9.9 to version 
>> 1.1.2.1 and I'm running into a problem.  I'm also using the 
>> corresponding castor-codegen and the anttask jars.  In my schema, I 
>> have an element, CheckOutItemResponse, which contains two elements.  
>> One of them is a choice which the source generator called
> CheckOutItemResponseChoice.
>> The CheckOutItemResponseChoice contains two sequences which the source
> 
>> generator called CheckOutItemResponseChoiceSequence and 
>> CheckOutItemResponseChoiceSequence2.  Good so far.  But,
>> CheckOutItemResponseChoiceSequence2 contains, among other elements, a 
>> choice.  Here lies the problem.  Within the
>> CheckOutItemResponseChoiceSequence2 generated object, the source 
>> generator created a member variable incorrectly named 
>> CheckOutItemResponseChoiceSequenceChoice.  No object of that name was 
>> ever created.  However, a CheckOutItemResponseChoiceSequence2Choice 
>> was created but is not being referenced correctly by 
>> CheckOutItemResponseChoiceSequence2.  BTW, the schema that I'm using 
>> contains many elements with the same pattern.  Version 0.9.9 generated
> 
>> the source correctly.  I can't seem to get version 1.1.2.1 to do the 
>> same.  I've attached a copy of the schema to hopefully shed some
> light.
>> I appreciate any help.
>>
>> Thank you,
>> Ron Corcuera
>>  <<ncip_v1_01.xsd>>
>>
>>
>>
>> ----------------------------------------------------------------------
>> --
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>     http://xircles.codehaus.org/manage_email
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to