Hi,
WSIF is an API for using WSDL-described services, independent of protocol or deployment. Since WSDL is extensible, you can define your own WSDL bindings, and if you have WSIF providers for those bindings, you can access it through the same WSIF API, independent of the actual protocol. WSIF defines bindings for, and has providers for, accessing EJBs, JMS, local java and java connector software (in addition to SOAP).
JAX-RPC and JAX-M are APIs for RPC and messaging respectively using XML. JAX RPC works off WSDL, but is not designed to support protocols other than XML-based ones (its deficiencies become evident when you attempt to use it as an API for accessing something other than a SOAP service).
If you want to use WSDL only for describing and accessing SOAP services, WSIF and JAX RPC are very similar. If you want to exploit WSDL's extensibility to describe and use other protocols, WSIF is more suitable. JAX RPC is a java standard and will be supported in all J2EE servers, WSIF is not a java standard but provides some benefits JAX RPC doesn't have.
Nirmal.
| [EMAIL PROTECTED]
03/23/2003 08:07 PM
|
To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: WSIF and JAX API |
Hi ...
Can somebody provide information abou WSIF and Sun's JAX-API, i.e. JAX-RPC and JAXM? How these APIs are different and which for future should we adopt?
Thanks and Regards.
BAM
