hi heri,
thnx,it worked with the prototype,would try it in real scenario...
chao
chetan
Chetan Rathi
Augsburger Str.336
70327 Stuttgart
Tel no.0711-7861-3148(off.)
Handy.no.015055564671
>From: "Bender Heri" <[EMAIL PROTECTED]>>Reply-To: <[EMAIL PROTECTED]>>To: <[EMAIL PROTECTED]>>Subject: Re: [castor-dev] Can castor be made tolerant to XML elements which are not mapped . >Date: Mon, 9 Feb 2004 15:46:59 +0100 > >Try this: >unmarshaller.setIgnoreExtraAttributes( true ); > >unmarshaller.setIgnoreExtraElements( true ); > > > >Heri > > > > > >-----Original Message----- >From: Chetan Rathi [mailto:[EMAIL PROTECTED] >Sent: Monday, February 09, 2004 3:22 PM &ggt;To: [EMAIL PROTECTED] >Subject: [castor-dev] Can castor be made tolerant to XML elements which are not mapped . > > > > Hello Keith, > >We have used the mapping approach to convert our object model to XML and vice versa. > >In accordance to an external system we receive attributes/element in the incoming XMLwhich are extra and not mapped in the mapping file and hence absent in classes tht we provide to the unmarshaller during runtime... > >As a normal behaviour we get runtime field descriptor exception saying it cannot identify the attribute since absent in the mapping file... > >I would like to know if the castor unmarshaller can be made tolerant to just ignore the attributes which are not mapped and not throw exceptions....and unmarshal the XML in accordance to the given information in the mapping file... > >thank you. > >Regards, > >Chetan > > > > > > > > > _____ > >Contact brides & grooms FREE! Only on www.shaadi.com. Register now! ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev >
Gifts for Him & Her. Valentine�s Day.
At MSN Shopping.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
