From HeikoPaul at atron.de  Mon Oct 22 02:33:14 2018
From: HeikoPaul at atron.de (Heiko Paul)
Date: Mon Oct 22 05:27:44 2018
Subject: [xsd-users] error: expected compositor instead of particle
Message-ID: <5BCD6F2A.1020601@atron.de>

Hi,

I?m using XSD on linux to process a 3rd party xsd file. However, I got 
an error message:

Command line: xsd cxx-parser  pkm.xsd
pkm.xsd:24:47: error: expected compositor instead of particle

The xsd file is in the attachment. The original is considerably bigger; 
I compacted it to show only the problematic content. I tried with xsd 
3.3.0 and 4.0.0. with the same result.  The file can be processed 
without errors by xjc, for example, so I suppose it is a correct xsd.

Any help is appreciated.

Heiko
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pkm.xsd
Type: text/xml
Size: 922 bytes
Desc: not available
Url : https://codesynthesis.com/pipermail/xsd-users/attachments/20181022/3d59cdfd/pkm.bin
From boris at codesynthesis.com  Tue Oct 23 10:21:12 2018
From: boris at codesynthesis.com (Boris Kolpackov)
Date: Tue Oct 23 10:30:26 2018
Subject: [xsd-users] error: expected compositor instead of particle
In-Reply-To: <5BCD6F2A.1020601@atron.de>
References: <5BCD6F2A.1020601@atron.de>
Message-ID: <boris.20181023161806@codesynthesis.com>

Heiko Paul <HeikoPaul@atron.de> writes:

> Command line: xsd cxx-parser pkm.xsd
> pkm.xsd:24:47: error: expected compositor instead of particle

The C++/Parser mapping has very limited support for complex type
derivation by restriction. And this is one example of it. I would
suggest that you use the C++/Tree mapping for this kind of schemas
(plus handling complex schemas with C++/Parser is pretty hard).