You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Phil Weighill-Smith <ph...@volantis.com> on 2008/02/01 10:22:05 UTC
Re: Supressing generation of xs:extension against inheritance
Thanks for the suggestions. I guess I'll live with the xs:extensions for
now (I guess they don't really affect the actual XML structure, save
element ordering).
Phil :n.
On Thu, 2008-01-31 at 17:06 -0500, Benson Margulies wrote:
> On Thu, 2008-01-31 at 17:01 -0500, Daniel Kulp wrote:
> > Honestly, looking at the jaxb spec, I don't see anything that would allow
> > that. Thats something you may want to ask on the jaxb lists:
> >
> > https://jaxb.dev.java.net/servlets/ProjectMailingListList
> >
> > There might be some hidden flag or something that could be used to set
> > it. I don't really know.
>
> (sort of) As per the blog posting I wrote at dssheep.blogspot.com, you
> could consider the following methodology:
>
> 1) Use your current classes as sacrificial.
> 2) Edit the XSD until you like it.
> 3) Regenerate new classes.
>
> The new classes will be redundant, but will that really hurt? You could
> also whip up a set of facade wrappers that delegate your interfaces to
> them.
>
>
>