Return-Path: Delivered-To: apmail-cxf-users-archive@www.apache.org Received: (qmail 97883 invoked from network); 16 Mar 2009 13:57:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Mar 2009 13:57:38 -0000 Received: (qmail 19538 invoked by uid 500); 16 Mar 2009 13:57:36 -0000 Delivered-To: apmail-cxf-users-archive@cxf.apache.org Received: (qmail 19504 invoked by uid 500); 16 Mar 2009 13:57:36 -0000 Mailing-List: contact users-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cxf.apache.org Delivered-To: mailing list users@cxf.apache.org Received: (qmail 19493 invoked by uid 99); 16 Mar 2009 13:57:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Mar 2009 06:57:36 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=MSGID_MULTIPLE_AT,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [217.113.178.1] (HELO bora.upw.de) (217.113.178.1) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Mar 2009 13:57:26 +0000 Received: from pcbens15.upw.de ([10.10.10.114] helo=pcbens15) by bora.upw.de with esmtpsa (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.50) id 1LjDJQ-0007LV-6S for users@cxf.apache.org; Mon, 16 Mar 2009 14:57:04 +0100 From: "Christofer Dutz" To: References: <22410060.post@talk.nabble.com> <22501441.post@talk.nabble.com> <200903131547.30943.dkulp@apache.org> In-Reply-To: <200903131547.30943.dkulp@apache.org> Subject: AW: xsi:type missing in returned value Date: Mon, 16 Mar 2009 14:56:50 +0100 Message-ID: <006e01c9a63f$0e9b9ec0$2bd2dc40$@dutz@upw.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 thread-index: AcmkFLKhfSv55eEYQ4GmWn2HpR4pgACKiLHQ Content-Language: de X-UPW-MailScanner: Found to be clean X-UPW-MailScanner-From: c.dutz@upw.de X-Virus-Checked: Checked by ClamAV on apache.org Hi, I am using Aegis data binding and here there are two parameters to = control this .... If you are not bound to using jaxb, maybe just give Aegis a try. Chris -----Urspr=FCngliche Nachricht----- Von: Daniel Kulp [mailto:dkulp@apache.org]=20 Gesendet: Freitag, 13. M=E4rz 2009 20:47 An: users@cxf.apache.org Cc: immutability Betreff: Re: xsi:type missing in returned value In general, jaxb and aegis only write the xsi:type when it's actually needed. =20 Basically, if the xsi:type is identical to what the schema says it would = be, it doesn't write it out. I don't think there is a way to force it = either. Dan On Fri March 13 2009 3:14:25 pm immutability wrote: > Any clues, anyone? I've been struggling with this for too long now, = read > all possible and impossible forum posts, bug reports, etc. (the = positive > side of this is that I have a much better understanding of web = services > now) ;) > > I've also tried to use Aegis instead of JAXB (with both JAX-WS and the > Simple frontend), and set the writeXsiTypes and readXsiTypes = properties of > the aegis context to "true" but I still don't get the xsi:type on the > returned value. > > I think the question here is if my expectation is correct: should I = have > the xsi:type with my current configuration in the element or = not? > If not, can I somehow get it there? > > Thanks, > Rado > > immutability wrote: > > Hello everyone - I'm new to webservices in Java, so my issue may be = some > > trivial, but I've had a hard time trying to figure this out. I've = been > > playing with CXF for a while, and I've created a simple web service = to > > test integration with spring. > > > > It all seems to be working fine, but what I need to do is make this > > compatible with older versions of client applications which are = using > > org.apache.soap to talk to the service. Currently, these = applications can > > properly call methods of my webservice, but fail to parse the = returned > > response, possibly due to the missing xsi:type attribute. My testing > > service is currently very simple and contains a single method = "login" > > accepting 2 string parameters username and password: > > > > @WebService > > public interface HelloService > > { > > boolean login( > > @WebParam(name =3D "username") > > String username, > > @WebParam(name =3D "password") > > String password); > > } > > > > The JAX-WS endpoint is defined in my spring XML. > > > > The SOAP response looks like this: > > > > > > > > > > true > > > > > > > > > > It looks like the clients expect the following: > > false > > > > Is there a way for me to make CXF add the xsi:type attribute to the > > return value somehow? Am I doing something wrong here, or do I need = to > > use some annotation to make it use the xsi:type? > > > > Again, I apologize if this is something stupid, I'm still learning. > > Thanks for any clues in advance! > > > > Rado --=20 Daniel Kulp dkulp@apache.org http://www.dankulp.com/blog =20 __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version = 3938 (20090316) __________ E-Mail wurde gepr=FCft mit ESET NOD32 Antivirus. http://www.eset.com =20 =20 __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version = 3938 (20090316) __________ E-Mail wurde gepr=FCft mit ESET NOD32 Antivirus. http://www.eset.com =20