-> -----Original Message-----
-> From: BEDNARIK,LASLO (HP-Germany,ex1) [mailto:[EMAIL PROTECTED]]
-> Sent: Thursday, November 29, 2001 12:06 PM
-> To: [EMAIL PROTECTED]
-> Subject: Re: [castor-dev] xsd:string becomes java:java.lang.String when
-> marshalling element with "enumeration" contents
->
->
-> Hi Arnaud,
->
-> sounds good. I'm just wondering if you are refering to the
-> same part of the problem I feel is wrong:
-> I think the main error happens during marshalling -CASTOR should
-> not instert the xsi stuff at all.
-> I don't know if unmarshalling introduces some more problems when
-> it sees the xsi attributes but if it does I see that as a second
-> issue.
-> Can you confirm that the fix would be for the first issue ?
->
Yes it will fit your need (hopefully :+)): xsi:type is introduced during the
marshalling
to provide some information for the unmarshalling time. It simply tells Castor:
unmarshall this element
using this java class.
So changes to the code affect mainly the Marshaller.
Arnaud
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
