It doesn't exactly work like that. The xsi:type is there to assert its an elements type, but it does not mean two elements are then equivalent only that they should conform to the type defined by the schema. The element names are the key here.
If you are using XMLBeans and you want your FpML document, start working with the type FpMLDocument type. HTH, -jacobd On Wed, Jul 2, 2008 at 7:58 AM, Henry Barnett <[EMAIL PROTECTED]> wrote: > Hi, > I'm working with FpML and I'm not very knowledgeable about xml when it comes > to standards and what is allowed and was hoping if you guy could answer a > quick question I have. > > I have a message as follows > <fpml:ModifyTradeConfirmation xsi:type="fpml:ModifyTradeConfirmation"...> > ... > </fpml:ModifyTradeConfirmation> > > Which fails validation because xmlbeans expects > <fpml:FpML xsi:type="fpml:ModifyTradeConfirmation"...> > ... > </fpml:FpML> > > Is the first instance valid considering that fpml:ModifyTradeConfirmation > extends fpml:FpML? > > Regards, > Henry > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
