Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of Scott.Oster@osumc.edu
 designates 140.254.120.27 as permitted sender)
User-Agent: Microsoft-Entourage/12.19.0.090515
Date: Wed, 05 Aug 2009 11:32:19 -0400
Subject: Re: Re: @XmlRootElement with jax-rs/jax-ws
From: "Scott Oster" <scott.oster@osumc.edu>
To: users@cxf.apache.org
Message-ID: <C69F1E43.70CE%scott.oster@osumc.edu>
Thread-Topic: @XmlRootElement with jax-rs/jax-ws
Thread-Index: AcoV4esfsvEPUOWHs0O/1vvhZcvYKg==
In-Reply-To: <1249461630.38931.ezmlm@cxf.apache.org>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=euc-kr
Content-Transfer-Encoding: quoted-printable


>>AFAIK, in case of JAXWS, additional JAXB elements/classes are generated.
Correct, though in the "wrapped" mapping, I don't believe these classes are
used.  In any event, I want the REST interface to return the XML of the
"Book" not the "getBookResponse".


Scott


-----------------------------------------------
From: Sergey Beryozkin <sergey.beryozkin@iona.com>
Date: Wed, 5 Aug 2009 01:39:59 -0700 (PDT)
To: <users@cxf.apache.org>
Subject: Re: @XmlRootElement with jax-rs/jax-ws


Hi,

AFAIK, in case of JAXWS, additional JAXB elements/classes are generated. Fo=
r
ex, if it's a method called 'getBook' returning Book then it will be a
getBookResponse class that will be generated.

I was also assuming that if ObjectFactory had methods returning JAXBElement=
s
then there'd be no need in updating the generated classes with
@XmlRootElement which apparently is not the case.

I don't think that in case of JAX-RS we can generate wrappers too.
Dan - is there anything that can be done at a pure JAXB level for users to
avoid explicitly adding XMLRootElement ? It appears there's no solution
really...

thanks, Sergey
 =20


Scott Oster-2 wrote:
>=20
> I am trying to add jax-rs annotations to an existing service
> implementation
> generated by wsdltojava (wrapped style).  The POJO returned by my
> operation
> is defined in a standalone XSD, and understandably doesn=A9=F6t have the
> @XmlRootElement annotation (for the reasons described here
> http://weblogs.java.net/blog/kohsuke/archive/2006/03/why_does_jaxb_p.html=
).
>=20
> My web service works fine, but my REST call dies with the error:
> unable to marshal type "..." as an element because it is missing an
> @XmlRootElement annotation
>=20
> If I add the @XmlRootElement annotation to the POJO, it works fine, but
> from
> the documentation it seems I shouldn=A9=F6t have to do this (and I don=A9=F6t wan=
t
> to,
> as it is generated code).
>=20
> In reading this bug: http://issues.apache.org/jira/browse/CXF-1650
> It appears this was an issue and should be =A9=F8fixed=A9=F7 in the version I am
> using
> (2.2 and trunk) but it=A9=F6s not clear if I am expected to configure
> something.
>=20
> The documentation here:
> http://cwiki.apache.org/CXF20DOC/jax-rs.html#JAX-RS-JAXBsupport states:
> =A9=F8Alternatively to using @XmlRootElement and Collection wrappers, one can
> provide an Object factory which will tell JAXB how to
> marshal a given type (in case of Collections - its template type).=A9=F7
>=20
> I have an ObjectFactory, generated by wsdl2java (and it looks correct),
> but
> I=A9=F6m not sure how I am supposed to =A9=F8provide=A9=F7 it other than have it on t=
he
> classpath (as I do).  Could you expand upon what exactly one needs to do
> to
> get this to work?
>=20
> Thanks,
> Scott