David, Can you show us s small sample that highlights your problem, and the 'incorrect' connection between the anonymous complex type definition and the xsi:type usage ?
Regards Werner > -----Ursprüngliche Nachricht----- > Von: Karr, David [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 10. Mai 2007 20:30 > An: [email protected] > Betreff: [castor-user] Problems with xsi:type > > I've never paid much attention to the "xsi:type" attribute before. I'm > now looking at a situation where I'm trying to validate a response > generated by Castor against the schema used by Castor. What I seem to > be seeing is that Castor generates the xsi:type attribute, by default. > The problem is, the resulting XML doesn't validate against the schema. > This is because the element uses an anonymous type, not a named type. > > I know that it's possible to suppress the generation of the xsi:type > atribute when marshalling. However, is it possible for Castor to only > generate the xsi:type attribute when the element uses a named type, and > leave it off when it uses an anonymous type? > > --------------------------------------------------------------------- > 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
