Hi Werner As always, thanks for your response. Unfortunately, we are still on JDK 1.4 and I believe 1.1.1 would require us to upgrade JDK. However, I think I am just missing some pieces here. I introduced "org.exolab.castor.xml.nspackages" property in castor.properties and now Castor recognizes xsi:type="SomethingType" too. Now my question is, is it required to have this property in castor.proeprties to use XML name in xsi:type? Is there any other way, better way? I ask this because we never needed to onverride castor.properties before, and if this is the ONLY way, we will be forced to extract castor.properties out from jar, bring it in classpath .... please suggest. Much thanks & regards, -Praveen
Werner Guttmann <[EMAIL PROTECTED]> wrote: Have you tried switching to 1.1 (or 1.1.1), as I do remember that we fixed one or the other issue related to the use of 'xsi:type'. The complete release notes since 1.0 can be found at http://www.castor.org/release-notes.html and if switching to a newer release doesn't help in your case, please feel free to raise a bug report at http://jira.codehaus.org/browse/CASTOR Regards Werner Praveen Jani wrote: > Hi > > I am using the Castor 1.0.5 and having an issue with xsi:type. When I > marshall my object, it generates following XML with > > xsi:type="SomethingType" > > But when I try to unmarshall it it expects > > xsi:type="java:com.abc.SomethingType" otherwise it complains "Unable to > find descriptors ...." > > The castor.cdr file also has mapping as "com.abc.SomethingType = " > > What is it that I am missing here? In the ideal world Castor should be > able to consume the same XML it is generating. > > Please help. > > Thanks > > > > > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
