|
|
|
|
|
I was "on vacation" last week, so the news are a bit late, but the news on July 1st confirmed the rumor: Oracle WebLogic Server is Oracle's "Strategic AppServer" - see the articles at The Register and InfoWorld. This comes on top of recent surveys on Oracle/BEA usage: SOA-Talk and The Register. |
A consequence of this move is that Metro is now used Oracle's main AppServer, increasing the adoption of GlassFish's WebServices stack. The same applies to JAXB RI; and, in that case, I know of no mainstream AppServer that uses a different implementation!
How did you draw the conclusion that Metro would be necessarily used any more as a result of this merger? WebLogic has its own web service stack:
http://www.jroller.com/gmazza/date/20080427
Posted by Glen on July 07, 2008 at 10:20 AM PDT #
WebLogic 10 has been using Metro for JAX-WS - see [1] and [2]; they also have their own implementation for the older JAX-RPC API. OC4J does not use Metro. I'm interpreting last week's announcement as reducing the relevance of an AppServer that didn't use Metro while increasing that of one that does.
Does that help? - eduard/o
[1]http://blogs.sun.com/theaquarium/entry/notd_bea_releases_weblogic_server
[2]http://www.bea.com/framework.jsp?CNT=overview.htm&FP=/content/products/weblogic/server/
Posted by Eduardo Pelegri-Llopart on July 07, 2008 at 11:58 AM PDT #
That's good news! Article[2] you gave says "BEA implements JAX-WS 2.0 based on the GlassFish community project (another blended example), which provides a solid implementation supported by the Java community." I didn't realize they were relying on Metro behind the scenes--all I knew was from their documentation[3], which says that their JAX-WS implementation is incomplete and for the WS-* stuff you still need to rely on their older JAX-RPC infrastructure.
[3] http://e-docs.bea.com/wls/docs100/webserv/jaxws.html
Posted by Glen on July 07, 2008 at 01:03 PM PDT #