Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 bim2007@basistech.com does not designate 199.88.205.99 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: JAXWS + JAXB + CXF's auto-wrapper feature
Date: Fri, 30 Nov 2007 13:17:35 -0500
Message-ID: <E95FD77F0171D14DA1EEE0A785E92B43024D6DF0@mail3.basistech.net>
In-Reply-To: <200711301313.15375.dkulp@apache.org>
Thread-Topic: JAXWS + JAXB + CXF's auto-wrapper feature
Thread-Index: AcgzfK56sy2LiqO5T+SmXPXX4jrq9AAAFhSQ
References: <E95FD77F0171D14DA1EEE0A785E92B43024D699B@mail3.basistech.net>
 <E95FD77F0171D14DA1EEE0A785E92B43024D699C@mail3.basistech.net>
 <200711301313.15375.dkulp@apache.org>
From: "Benson Margulies" <bim2007@basistech.com>
To: "Daniel Kulp" <dkulp@apache.org>,
	<cxf-dev@incubator.apache.org>

1) So, this legitimatized my JIRA calling for preferring WebParam to
XmlRootElement.

2) This sure is an argument for Bare. JAX-WS doesn't touch elementForm,
so all these people who want to control the elementForm are going to
stay sad.

> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]=20
> Sent: Friday, November 30, 2007 1:13 PM
> To: cxf-dev@incubator.apache.org
> Cc: Benson Margulies
> Subject: Re: JAXWS + JAXB + CXF's auto-wrapper feature
>=20
>=20
> Just FYI:  the JAXWS spec specifically avoids any mention of=20
> having XmlRootElement on beans for the java first case,=20
> probably due to the=20
> issues you are seeing.  =20
>=20
> The spec REALLY want's all the top level element names and such to be=20
> controlled with the JWS/JAXWS annotions and not the jaxb=20
> annotations.  =20
> Thus, we need to use that information instead and more or=20
> less ignore the XmlRootElement annotation when we can. =20
>=20
> If the type has a XmlRootElement and an XmlType with a name=20
> attribute,=20
> we're kind of OK as the type is non-anonymous and we can=20
> point to it.  =20
> However, if the type has no name attribute, it does blow=20
> things up pretty badly and is definitely outside the stuff=20
> the JAX-WS tck would be testing.
>=20
> Dan
>=20
>=20
> On Sunday 25 November 2007, Benson Margulies wrote:
> > I have a little more information on this to offer.
> >
> > Leaving the current schema generation alone, I end up with=20
> a complex=20
> > type containing two elements refs to the same element (one with=20
> > maxOccurs and minOccurs).
> >
> > As an experiment, I fed this to wsdl2java, which told me=20
> that this was=20
> > very sad and encouraged me to 'apply a customization to fix the=20
> > names'.
> >
> > Well, OK, then, that would seem to favor my theory that=20
> auto-generated=20
> > wrapper types should favor @WebParam names over XmlRootElement refs.
>=20
>=20
>=20
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727    C: 508-380-7194
> daniel.kulp@iona.com
> http://www.dankulp.com/blog
>=20