So, is it true jaxb does not code generate
custom 'implements' statements?
> -----Original Message-----
> From: Ryan Shoemaker - JavaSoft East
> [mailto:Ryan.Shoemaker_at_Sun.COM]
> Sent: Tuesday, March 04, 2003 4:34 PM
> To: JAXB-INTEREST_at_JAVA.SUN.COM
> Subject: Re: [JAXB-INTEREST] Specifying Interfaces that
> generated
> classes extend/implement
>
>
> Douglas Jackson wrote:
> > Has there been any discussion of allowing the
> > specification of an interface that a generated
> > class extends/implements? (The generated interface
> > would extend the interface and the generated
> > implementation would implement it)
> > This would be handy for cases where an API was
> > exposing some methods and the jaxb class was going
> > to provide the implementation of the API.
> >
> > Something along the line of:
> >
> > <xs:element name="x">
> > <xs:annotation><xs:appinfo>
> > <jaxb:class interface="com.x"/>
> > </xs:appinfo></xs:annotation>
> > <xs:complexType>
> > <xs:choice>
> > <xs:element ref="y"/>
> > </xs:choice>
> > </xs:complexType>
> > </xs:element>
> >
>
> The specification doesn't address this, but there is a
> feature like what
> you've described in the RI:
>
> http://java.sun.com/webservices/docs/1.1/jaxb-1.0/vendor
> .html#superclass
>
> --Ryan
>