[Ext] Re: [xsd-users] Fails to parse complex type extensions

Nicolas Weidmann n.weidmann at lombardodier.com
Wed Jun 24 10:44:17 EDT 2026


Hello Boris,

Thank you for your answer.

I was already doing https://www.codesynthesis.com/projects/xsd/documentation/cxx/tree/manual/#2.11

But by re-reading that example, I realized it was the test document that was wrong...

It was <D>...</D> instead of <a xsi:type="D">...</a>

After the correction, my test successfully worked when std::dynamic_pointer_cast<D>(the_parsed_document)...

Thanks for your patience!

Regards,


Nicolas Weidmann
Banque Lombard Odier & Cie SA
Rue de la Corraterie 11 - 1204 Genève - Suisse
T +41 22 709 23 17
www.lombardodier.com
-----Original Message-----
From: Boris Kolpackov <boris at codesynthesis.com>
Sent: mercredi, 24 juin 2026 16:00
To: Nicolas Weidmann <n.weidmann at lombardodier.com>
Cc: xsd-users at codesynthesis.com
Subject: [Ext] Re: [xsd-users] Fails to parse complex type extensions

Nicolas Weidmann <n.weidmann at lombardodier.com> writes:

> I have an XSD containing several complex types. Let's call them A, B, C & D
>
> B is an extension of A, C of B and D of C.
>
> Only A has an associated element name a
>
> This means that only A gets a generated function name parseA.
>
> I have a document containing a D, but I can't parse it as parseA
> explicitly tests for the type to be "a":

Smells like polymorphism to me:

https://www.codesynthesis.com/projects/xsd/documentation/cxx/tree/manual/#2.11
[[ rethink everything. ]]<https://www.lombardodier.com>

[[LinkedIn]]<https://www.linkedin.com/company/lombard-odier>  [[Twitter]] <https://twitter.com/lombardodier>   [[Facebook]] <https://facebook.com/lombardodier>   [[Instagram]] <https://www.instagram.com/lombardodier/>   [[YouTube]] <https://www.youtube.com/channel/UCqatbeqXskmWejbm0KPLV3w>

*** IMPORTANT NOTICE REGARDING INSTRUCTIONS by EMAIL ***
Please be aware that instructions received by e-mail should be
considered delayed and not executed unless they have been
specifically confirmed by your relationship manager/banker.
Email traffic during turbulent times in the financial markets is
high and cannot always be acted upon at all times.
Lombard Odier cannot be held liable for such delay in execution
or for the non-execution of an instruction given by email even
if it was given in due time. Therefore, instructions requiring
immediate action must be communicated by telephone by calling
the bank’s registered landline.
Thank you for your understanding.

*** IMPORTANT INFORMATION ABOUT DATA PROTECTION ***
You might be receiving this because you have provided us with
your contact details. If this is the case note that we may process
your personal data for direct marketing purposes.
If you wish to object to this processing, please notify the
Group’s Data Protection Officer<mailto:group-dataprotection at lombardodier.com>.
For more information: www.lombardodier.com/privacy-policy

DISCLAIMER **********************************************
This message is intended only for use by the person
to whom it is addressed. It may contain information
that is privileged and confidential. Its content does
not constitute a formal commitment by any company
of the Lombard Odier group. If you are not the intended
recipient of this message, kindly notify the sender
immediately and destroy this message. Thank You.
*******************************************************(dch)*




More information about the xsd-users mailing list