XSD generation problems II

[atingley]

Ok, I thought I had this down, but am seeing some weird behavior with multiple packages and XSD...

I have 3 pkgs, A, B, C; A is the "base" package, and defines "base" types.  B and C are "extension" packages, and define new types in terms of extensions to those defined in A.

All three packages are configured to have the same namespace.

When I generate the schema for pkg A, it generates two <xs:include> elements, one for pkg B, the other for pkg C!
???

The generation of B and C are ok - they generate an <xs:include> element referring to pkg A, as expected.

There are no references *from* pkg A  *to* pkg B or C.  Why would there be an <xs:include> element generated in the output schema file?

[benc]

Hi atingley,

Thanks for the note. As far as I can tell this a bug - schema A definitely shouldn't require includes, if the pacakge doesn't contain references to C and B.

We'll try to get this resolved ASAP. Thanks again for letting us know.

Regards,
Ben

[VK]

Hi atingley,

The issue regarding <xs:include> has been resolved for the next release of EA  

Cheers.

[Tomas]

Hi vkumar,

I've just downloaded EA 5 and the problem still exists  .
It keeps adding include elements to packages that are not supposed to be there...

Was the fix removed from the release?

[VK]

Hi Tomas,

This bug has definately been fixed. Would it be possible for you to send in a model reproducing your problem to Sparx Support ?

[Tomas]

Hi vkumar,

I've sent the issue as a bug where I've added a model where it is possible to reproduce the error.