JSR-109 deals mainly with the deployment of web services in a J2EE
environment and relies on the JAX-RPC specification to describe the WSDL
to Java representation mappings. JAX-RPC only mentions SOAP but the JAX-RPC
API does not exclude the use of other protocols. One of our goals is for
WSIF to be as JSR-109 and JAX-RPC compatible as possible, currently the
WSIF API is not fully JAX-RPC compatible, but work is on going right now to
change this, and this should hopefully become available in a new release in
the near-ish future.
...ant
Anthony Elder
[EMAIL PROTECTED]
Web Services Development
IBM UK Laboratories, Hursley Park
(+44) 01962 818320, x248320, MP208.
"Naresh Bhatia" <[EMAIL PROTECTED]> on 03/02/2003 12:39:15
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: Accessing a service via SOAP as well as Java
Very interesting. I will take a look at WSIF. One quick question - how does
WSIF compare with JSR-109 (Web Services for J2EE), which seems to
addressing similar issues? Is there an overlap?
Thanks.
Naresh
-----Original Message-----
From: Anthony Elder [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 3:49 AM
To: [EMAIL PROTECTED]
Subject: Re: Accessing a service via SOAP as well as Java
Hi Naresh,
This is exactly what the Web Service Invocation Framework(WSIF) is for.
Now, you describe your service with a WSDL file which includes a SOAP
binding, with WSIF you can add bindings other than SOAP to the WSDL file,
for example a Java binding. In your application you then uses the WSIF
binding independent API to access the service, and have which binding is
actually chosen to be used made as a run time decision.
WSIF comes with binding implementations for SOAP, SOAP/JMS, Java, EJB, and
native JMS, so once your application starts using WSIF, the service can be
moved around your system to be implemented in whatever technology is
appropriate, and your application never needs to change.
For more information see the Apache WSIF homepage at
http://ws.apache.org/wsif
...ant
Anthony Elder
[EMAIL PROTECTED]
Web Services Development
IBM UK Laboratories, Hursley Park
(+44) 01962 818320, x248320, MP208.
"Naresh Bhatia" <[EMAIL PROTECTED]> on 02/02/2003 14:57:01
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: Accessing a service via SOAP as well as Java
I have exposed a service via SOAP. However, I also need to access this
service internally from my application. Do you think it is okay to access
the service directly by calling its SOAP implementation (bypassing the Axis
servlet completely)? Is there preferred way to do this? Here's what I am
thinking:
Accessing the service via SOAP
UserProviderService userProviderService = new UserProviderServiceLocator
();
UserProvider userProvider = userProviderService.getuserservice(url);
..now start using userProvider..
Accessing the service directly using its SOAP implementation
UserProvider userProvider = new UserserviceSoapBindingImpl()
..now start using userProvider..
Thanks.
Naresh
