Hi Mathias, If you are using a Mapping you can add the following in the definition of the ComponentReference element: <bind-xml autonaming="deriveByClass"/> That should do the trick... For more information on the <bind-xml> element, please take a look at http://www.castor.org/xml-mapping.html#3.5-The-<bind-xml>-element
Hope that helps, Arnaud -----Original Message----- From: Matthias Peschel [mailto:M.Peschel@;intershop.de] Sent: Wednesday, November 06, 2002 12:28 PM To: [EMAIL PROTECTED] Subject: [castor-dev] [xml] xsi:type handling in 0.9.3.9 and 0.9.4 Hi, � Until now we used Castor 0.9.3.9 and now we want to upgrade to 0.9.4. In the old version the marshalled xml looked like this: � ��� <ComponentReference id="abc"/> � In the 0.9.4 version it looks different: � ��� <PersistentElement id="abc" xsi:type="ComponentReference"/> � ComponentReference is�a concrete class that extends the abstract class PersistentElement. I know, that the xsi:type attribute specifies the concrete sub class of the element. But in 0.9.3.9 the attribute�was only generated when using interfaces and not when using abstract classes. But PersistentElement is an abstract class. So it worked in 0.9.3.9. � Did you extend the usage of ysi:type also for abstract classes? Is there a way to get the same results as in 0.9.3.9? � Many thanks. � Matthias � ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
