Hi,

 I don't think that JSR-921 is superceeded by JSR-181 - these are different
specs and WLS supports both of them (have a look at the link provided
below):

http://edocs.bea.com/wls/docs92/webserv/overview.html

However WLS supports JSR-181 1.0 while Xfire (and CXF as well afaik) support
JSR-181 2.0 (for the differences plz look at the link below):

http://jcp.org/aboutJava/communityprocess/maintenance/jsr181/181-2.0.html

One example is that WLS uses a WebService annotation that does not have the
portName attrib.
This proved to be problematic when using Xfire which came with its own
jsr181 API jar (2.0). We just put this jar in front of the classpath and
we're still happily using it after migrating to CXF.

Thanks,


--

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 2:39 PM
To: [email protected]
Cc: [email protected]
Subject: RE: WL9.1 vs CXF

Hello,

That's really useful feedback.

> 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

How "old"?  I believe WL implements JSR-921 (which hasn't been updated since
2004), and CXF appears to use JSR 181 (last updated June 2006). Does
181 superceed 921?

Thanks,


John

---

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