users@jaxb.java.net

Re: ComplexContent Extensions

From: Ed Mooney <Ed.Mooney_at_sun.com>
Date: Fri, 28 Mar 2003 07:02:25 -0500

Hi Malachi,

Sorry for the delay in getting back to you.

We've investigated this further and think you've found a bug. Thanks for
your persistence.

Regards,
--
Ed Mooney         |Sun Microsystems, Inc.|Time flies like
Java Web Services |UBUR02-201            |an arrow, but
Ed.Mooney_at_Sun.COM |1 Network Drive       |fruit flies like
781-442-0459      |Burlington, MA  01803 |a banana. Groucho
Malachi de AElfweald wrote:
> On Thu, 27 Mar 2003 12:39:24 -0500, Ed Mooney <Ed.Mooney_at_Sun.COM> wrote:
>
>
>>Hi Malachi,
>>
>>Section 5.9.10.1 of the spec defines "getContent" as one of the methods
>>in the choice property. I believe the name of your base type ("content")
>>conflicts with that binding, but leave it to others to explain why (or
>>correct my mistake).
>
>
> But, why did changing "content" globally to "data" not fix the problem then?
>
> And what does this actually do (changed 'content' to 'data' due to the other change I made):
>
>   <jaxb:bindings schemaLocation="dynarray.xsd" node="/xsd:schema">
>     <jaxb:bindings node="./xsd:complexType[@name='data']">
>       <jaxb:property name="base"/>
>     </jaxb:bindings>
>   </jaxb:bindings>
>
>
> I thought it changed all references from 'data' to 'base', but the javadocs don't appear to reflect that kind of change.
>
> Malachi