From christian at gsvitec.com  Tue Oct 14 12:42:58 2014
From: christian at gsvitec.com (Christian Sell)
Date: Tue Oct 14 12:43:02 2014
Subject: [xsde-users] xsde crashes
Message-ID: <006101cfe7cd$e99016c0$bcb04440$@gsvitec.com>

Hello,

 

I am trying to compile our schema using xsde-3.2.0-i686-windows, but the
executable crashes after generating only the first 2 files.  Am sending the
schema file to Boris boris@codesynthesis.com
<mailto:boris@codesynthesis.com>  for investigation

 

Thanks,

Christian 

From boris at codesynthesis.com  Wed Oct 15 01:05:32 2014
From: boris at codesynthesis.com (Boris Kolpackov)
Date: Wed Oct 15 01:12:46 2014
Subject: [xsde-users] xsde crashes
In-Reply-To: <006101cfe7cd$e99016c0$bcb04440$@gsvitec.com>
References: <006101cfe7cd$e99016c0$bcb04440$@gsvitec.com>
Message-ID: <boris.20141015065723@codesynthesis.com>

Hi Christian,

Christian Sell <christian@gsvitec.com> writes:

> I am trying to compile our schema using xsde-3.2.0-i686-windows, but the
> executable crashes after generating only the first 2 files.

I took a look and it has to do with the use of a more complex XML Schema
restriction case in your schema (TItem restricts TAbstractItem). Here
you restrict an attribute wildcard with specific attributes which XSD/e
cannot handle (the mapping expects to have restricted data members in
the base). Generally, XML Schema restriction is very hard to map to
C++ inheritance. As a result, to maintain simple and light-weight
object models we've decided not to support more advanced restriction
cases in XSD/e.

So, as a general guideline, if you want to use XSD/e, keep your use
of restriction to only simple and straightforward cases. In your
particular situation, maybe changing restriction to extension will
make sense.

Boris