On Friday 29 Aug 2003 4:26 pm, Calverley, Thomas wrote: > From reviewing existing postings I understand that the unmarshaller may > require an xsi:type to be specified.
I think my project posed the same question a few days back. Have you considered avoiding the xsi:type attribute altogether by using auto-naming="deriveByClass"? (See the end of section 5 in: http://castor.exolab.org/xml-mapping.html#5.-xsi:type ). This allowed me to avoid trying to define a domain of sub-class name values for my xsi:type attributes in my schema. Instead the schema merely must enforce an element hierachy. This seemed far more natural (and easy). > > My question is therefore, how do I write an XML Schema that enforces the > specification of xsi:type for each element - such that validation of an XML > document against this Schema would fail? > > Many Thanks, > > Tom Hope this helps. -- Keith Wall [EMAIL PROTECTED] ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
