No I am not. Again this issue only happens if I want to have xjc build the
source for the abstract types and the concrete types separately. If I build
them together this works fine so it's a bit strange to me why it would do
this.
On Mon, Feb 9, 2009 at 12:57 PM, Kenny MacLeod <kenny.macleod_at_kizoom.com>wrote:
> Are you using the xjc:simple binding customisation? That does things
> like collapsing extendable types down to concrete references.
>
>
> Jamie Johnson wrote:
>
>> I am running into an issue where I have created several XSDs, xsd 1 has an
>> abstract type defined, xsd 2 implements the xsd (it is important to note
>> that xsd 1 has no implementations of the abstract type). If I compile these
>> schemas together I get the expected result in that the Java created has a
>> method of the form.
>> setGeometry(JAXBElement<? extends GeometryBaseType>)
>>
>> but if I compile them separately the method looks like
>>
>> setGeometry(GeometryBaseType)
>>
>> which does not allow me to properly use the object generated in xsd 2.
>> Short of compiling everything together, how can I have this method
>> generated appropriately?
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
>