[Ext] Re: [xsd-users] Issues with operator==

[Nicolas Weidmann]

For your information, I have no problems serializing a transaction holding a SubFidget.

Here is the serialized transaction that I create and which fails the comparison test:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<p1:transaction xmlns:p1="http://www.acme.corp/test" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <p1:product ModelNumber="ACME-9942-BOOM" Name="Self-Destructing Stress Anvil" xsi:type="p1:SubFidget">
    <p1:PrimaryFunction>Deep pressure finger relaxation</p1:PrimaryFunction>
    <p1:BackfireTrigger>Pressing down 5% too hard</p1:BackfireTrigger>
    <p1:ExplosionRadiusFeet>40</p1:ExplosionRadiusFeet>
  </p1:product>
</p1:transaction>


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: Nicolas Weidmann
Sent: jeudi, 23 juillet 2026 09:08
To: xsd-users at codesynthesis.com
Subject: RE: [Ext] Re: [xsd-users] Issues with operator==

Hi Boris,

I could narrow it down a bit.

It's not a lib issue...

It's another polymorphic issue when a XSD is included into another.

If we reuse the XSD I sent you earlier with the Fidget & SubFidget and include it:

<?xml version="1.0" encoding="utf-8" ?>
<xs:schema xmlns="http://www.acme.corp/test" targetNamespace="http://www.acme.corp/test" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
  <xs:include schemaLocation="test_extensions.xsd" />
  <xs:complexType name="Order">
    <xs:all>
      <xs:element name="product" type="Fidget" />
    </xs:all>
  </xs:complexType>
  <xs:element name="transaction" type="Order" />
</xs:schema>

Whenever I create a transaction with an order of type Fidget, transaction.getValeu() == transaction.getValeu() is OK

But if my transaction holds a SubFidget instead, the same comparison results in the exception.

I will be on holidays for the next 2 weeks. So, if you don't hear from me for a while, it's normal...

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, 22 juillet 2026 13:34
To: Nicolas Weidmann <n.weidmann at lombardodier.com>
Cc: xsd-users at codesynthesis.com
Subject: [Ext] Re: [xsd-users] Issues with operator==

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

> So, to make sure my code was not the issue, I compiled static (no DLL
> here) and compared myBuiltElement->getValue() == myBuiltElement->getValue()

By static do you mean you are linking static libraries or you linked
all the object files directly into the executable? If it's static
libraries, then you need to link with /WHOLEARCHIVE to make sure all
the object files end up in the executable.
[[ 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)*