Hi,

There're several problems with WLS 9/10 and CXF:
A) WLS uses it's own (buggy) JAXB impl taken from glassfish (2.0.5) ( this
can be solved by putting the JAXB 2.1 api in front of the classpath +
inverting classloader hierarchy in ur webapp)
B) WLS uses "old" jws annotations (for example the WebService annotation
does not have the portName attrib) - again putting the desired jaxws api
version in front of the classpath solves your problems
C) WLS uses it's own (a bit strange and inefficient) StAX impl - this can be
solved by forcing CXF to use a particular impl (e.g. Woodstox).
D) WLS uses JAX-RPC rather than JAX-WS but this does not really cause any
problems (u just have to put all the JAX-WS apis/impls in your WEB-INF/lib)

That's more or less all that comes to my mind. Let me know if u need more
info.


--

Pawel Lipka

IT Architect

________________________________

 AMG.net  businesstechnology consulting 

 http://www.amg.net.pl

Łąkowa 11, 90-554 Lodz, tel/fax (42) 296 11 32

Tresc niniejszej wiadomosci moze byc poufna. Jezeli nie jestescie Panstwo
jej adresatem, to rozprowadzanie  lub wykorzystywanie zawartych tu
informacji jest zabronione.


-----Original Message-----
From: John-M Baker [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 03, 2008 12:59 PM
To: [email protected]
Subject: WL9.1 vs CXF

Hello,

Does anyone have any thoughts on the pros & cons of using CXF over WL9.1? 

To start, looking at the package names (MessageContext), WL uses JAX-RPC
rather than JAX-WS, yet both use JWS.

Any feedback welcome.


John Baker
--
Web SSO
IT Infrastructure
Deutsche Bank London

URL:  http://websso.cto.gt.intranet.db.com


---

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and delete this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for
additional EU corporate and regulatory disclosures.

Reply via email to