"X and Y are defined in separate maven projects. Project where Y is
defined depends on project where X is defined..."
So, class X extends Y, right ?
or:
<xsd:complexType name="Y" abstract="true">...</xsd:complexType..>
<xsd:element name="X">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="tns:Y">
<xsd:attribute name="bbb" type="xsd:string" use="required" />
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
That's it ?
reading your previous post, it seems the both type are declared
independently and you are trying to establish the hierarchy by an
external annotation. Is it correct ? if yes, something is wrong in the
project design (or dependencies).. and I am pretty sure it is forced
by some special condition you will need to face...
On Wed, Sep 24, 2008 at 9:46 AM, Maciej Zubala <maciej.zubala_at_gmail.com> wrote:
>
>
> 2008/9/24 Felipe Gaúcho <fgaucho_at_gmail.com>
>>
>> You can import and/or include XSD inside another ones, and use
>> abstract attributes to establish the hierarchy...
>>
>> the WSDLs of my project are formed by half dozen XSD files, and it
>> works fine......
>
> I use importing and including and the whole heirarchy is well established.
> Please read my previous post carefully...
>
>