And let's try to ignore the Xerces version number for the time being ... ;-)

Werner

Voiry, Antoine wrote:
> Werner,
> Attached are the properties I am using.
> I am using type.
> 
> I was asking the xerces question as if I am using Xerces 2.7.1, I am
> getting different type of errors.
> 
> 
> Antoine 
> 
> -----Original Message-----
> From: Werner Guttmann [mailto:[EMAIL PROTECTED] 
> Sent: Friday, October 27, 2006 10:52 AM
> To: [email protected]
> Subject: Re: [castor-user] Problem in generating source file with castor
> 1.0.4
> 
> No, the version of Xerces should be completely irrelevant in this
> context. Are you actually running the code generator in 'element' or
> 'type' mode ?
> 
> Werner
> 
> Voiry, Antoine wrote:
>> Hi Werner,
>> This is still working with 0.9.3.19. I compiled the generated classes 
>> with 0.9.3.19 yesterday evening.
>> It failed with 1.0.x.
>>
>> I was wondering if this cannot be caused by the xerces version we are 
>> using.
>>
>> The XSD is weird but this is what SAP is generating.
>> Do you want the 0.9.3.19 generated classes?
>>
>> Bye,
>> Antoine
>>
>> -----Original Message-----
>> From: Werner Guttmann [mailto:[EMAIL PROTECTED]
>> Sent: Friday, October 27, 2006 10:16 AM
>> To: [email protected]
>> Subject: Re: [castor-user] Problem in generating source file with 
>> castor
>> 1.0.4
>>
>> Salut Antoine,
>>
>> are you actually saying that this used to work with 0.9.3.19 ?
>>
>> Werner
>>
>> Voiry, Antoine wrote:
>>> Hello all,
>>> I am using castor 1.0.4, with Xerces 2.6.2 on java 1.4.10.
>>>
>>> I found a "bug" in version of castor greater to 0.9.3.19.
>>> This is causing the source generated to be unable to deal with the
>> XML.
>>> Example with RFC_READ_TABLE wsdl file from sap:
>>> <xsd:element name="RFC_READ_TABLE.Response"> <xsd:complexType> 
>>> <xsd:all> <xsd:element name="DATA"> <xsd:complexType> <xsd:sequence> 
>>> <xsd:element maxOccurs="unbounded" minOccurs="0" name="item"
>>> type="s0:TAB512"></xsd:element>
>>> </xsd:sequence>
>>> </xsd:complexType>
>>> </xsd:element>
>>> <xsd:element name="FIELDS">
>>> <xsd:complexType>
>>> <xsd:sequence>
>>> <xsd:element maxOccurs="unbounded" minOccurs="0" name="item"
>>> type="s0:RFC_DB_FLD"></xsd:element>
>>> </xsd:sequence>
>>> </xsd:complexType>
>>> </xsd:element>
>>> <xsd:element name="OPTIONS">
>>> <xsd:complexType>
>>> <xsd:sequence>
>>> <xsd:element maxOccurs="unbounded" minOccurs="0" name="item"
>>> type="s0:RFC_DB_OPT"></xsd:element>
>>> </xsd:sequence>
>>> </xsd:complexType>
>>> </xsd:element>
>>> </xsd:all>
>>> </xsd:complexType>
>>> </xsd:element>....
>>>
>>> As you can see the element named item is present several times in the
> 
>>> xsd.
>>> This is causing castor source generator to generate 3 times, the item
> 
>>> and only the last one is available from the RFC_READ_TABLE object. 
>>> The
>>> underlying types are generated but are not accessible through the 
>>> RFC_READ_TABLE.
>>> This is causing the source file to fail compilation with the error 
>>> message cannot resolve symbol.
>>>
>>> I attached a file with all the files I am using.
>>> I rollback to 0.9.3.19.
>>>
>>> Kind Regards
>>> Antoine
>>>
>>>
>>> ---------------------------------------------------------------------
>>> -
>>> --
>>>
>>> ---------------------------------------------------------------------
>>> 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
> 
> 
> 
> ------------------------------------------------------------------------
> 
> ---------------------------------------------------------------------
> 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