W3C home > Mailing lists > Public > www-ws-arch@w3.org > May 2004

RE: WS Implementation Question

From: Anne Thomas Manes <anne@manes.net>
Date: Wed, 5 May 2004 13:04:38 -0400
To: "'Ugo Corda'" <UCorda@SeeBeyond.com>, "'Hal Lockhart'" <hlockhar@bea.com>, "'Cutler, Roger (RogerCutler)'" <RogerCutler@chevrontexaco.com>, <www-ws-arch@w3.org>
Message-Id: <20040505171025.E5F8FA152A@frink.w3.org>
Roger,
 
Ugo is correct - JAX-RPC is the standard Java API providing an RMI-like
interface to SOAP. From the service perspective, a JAX-RPC implementation
creates a SOAP/WSDL wrapper interface for a Java class, and from the client
perspective, it generates a client proxy from the service's WSDL definition.

 
As for actual implementations:
 
-          Sun provides the JAX-RPC 1.1 reference implementation. It is
distributed as part of the Java Web Services Developer Pack (JWSDP). The
JAX-RPC RI is designed to run in Tomcat, although it can be ported to any
servlet 2.2 engine. See
http://java.sun.com/webservices/webservicespack.html. 
-          Apache Axis is an open source implementation of JAX-RPC. The
latest version (1.2 - still in beta) supports WS-I BP. See
http://ws.apache.org/axis/. Axis can be deployed in any servlet 2.2 engine.
-          BEA, IBM, Oracle, Sybase, IONA, Novell, etc, supply a JAX-RPC
implementation with the latest revisions of their respective J2EE app
servers.
-          Cape Clear Server is a commercial JAX-RPC implementation. It can
be deployed as a standalone server, or it can be deployed in various servlet
2.2 containers, including WebLogic (v6 - v8), WebSphere (v4 - v5), Tomcat,
JBoss, and Jetty.
-          Systinet WASP is a commercial JAX-RPC implementation. It can be
deployed as a standalone server, as an embedded Web service runtime within
an application, or in any servlet 2.2 engine.
-          webMethods Glue is a commercial JAX-RPC implementation. It can be
deployed as a standalone server, as an embedded Web service runtime within
an application, or in any servlet 2.2 engine. 
 
Regards,
Anne
 
  _____  

From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org] On
Behalf Of Ugo Corda
Sent: Wednesday, May 05, 2004 12:11 PM
To: Hal Lockhart; Cutler, Roger (RogerCutler); www-ws-arch@w3.org
Subject: RE: WS Implementation Question
 
The main reference is actually JAX-RPC 1.1, which covers Java mappings
to/from Schema/WSDL, SOAP bindings, and use of Java servlets as endpoints.
(JAX-RPC 2.0 is currently under development in JSR-224 and will add support
for asynchronous interactions).
 
JSR 109 addresses using EJBs as endpoints, and discusses deployment issues.
 
Ugo
-----Original Message-----
From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org] On
Behalf Of Hal Lockhart
Sent: Wednesday, May 05, 2004 8:45 AM
To: Cutler, Roger (RogerCutler); www-ws-arch@w3.org
Subject: RE: WS Implementation Question
If you are looking for a Java standard's reference, I believe JSR 109 covers
this. (JSR 172 does the same for J2ME.)
 
Hal
-----Original Message-----
From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
Behalf Of Cutler, Roger (RogerCutler)
Sent: Wednesday, May 05, 2004 9:47 AM
To: www-ws-arch@w3.org
Subject: WS Implementation Question
First, apologies for posting on an architecture group a question that is
clearly about implementation.  The reason I am doing this is, as will become
apparent, I am totally unfamiliar with the platform in question and I am
hoping that someone will be kind enough to give me some helpful hints.
We have a person here who is trying to provide some Web service interfaces
to specialized search functions on our corporate intranet, with interop
(consumption from .Net) an objective.  The specific search engine involved
is Inktome, which I believe has a Java API but no direct Web services
interfaces.  He does not seem to have available any of the major development
platforms that provide Web services in Java (e.g. WebLogic, WebSphere,
JBuilder), and I believe that he is using fairly low level libraries in the
Apache context.  It sounds like he is using these low level calls to
construct SOAP messages from the ground up, and that he might intend to do
something similar to make WSDL files.  This sounds to me like an awful lot
of work, and it also seems to me that it potentially gets one into the
difficulties of dealing with the very detailed and potentially tricky issues
covered by WS-I basic profile.
Can someone point me to some sort of development environment or libraries
likely to be available in this copntext that are a little higher level --
so, for example, someone else has figured out how to conform to WS-I? 
Received on Wednesday, 5 May 2004 13:10:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:27 GMT