List Info

Thread: WSIF positioning relative to JAX-WS




WSIF positioning relative to JAX-WS
user name
2006-10-17 14:27:03
Would someone from WSIF kindly repond to my inquiry at
theserverside.com:

<http://www.theserverside.com/discussions/
thread.tss?thread_id=42658>

Please post response on the above theserverside.com thread
instead of
this mailing list.

Thank you.

-- 
Regards,
Farrukh

Web: http://www.wellfleet
software.com




------------------------------------------------------------
---------
To unsubscribe, e-mail: wsif-user-unsubscribews.apache.org
For additional commands, e-mail: wsif-user-helpws.apache.org

WSIF positioning relative to JAX-WS
user name
2006-10-18 05:15:09
Farrukh S. Najmi wrote:
> Would someone from WSIF kindly repond to my inquiry at
theserverside.com:
>
> <http://www.theserverside.com/discussions/
thread.tss?thread_id=42658>
>
> Please post response on the above theserverside.com
thread instead of
> this mailing list.
>   
here is what i posted:

"AFAIK Apache WSIL is no longer developed (and spec
"dead")

WSIF is about taking WSDL and invoking any service described
in it
irregardless of how the service is implemented (and that was
accomplished before SOA became buzzword). WSIF allows
developers to use
the same API that reflects WSDL abstractions to access a
service no
matter what protocol is used. WSIF can implement any
protocol binding
(through WSIF providers) to allows interactions with a
service solely
though its interface (PortType).

JAX-WS is Java implementation of set of WS-* technologies
based on JAX-*
specs that is SOAP focused (main difference to WSIF - WSIF
is not just
for SOAP) - AFAIK JAX-WS do not have multi-protocol or an
abstraction
API of WSDL PortType as a goal. JAX-WS is also both for
client and
server but WSIF is only clients side."

best,

alek

------------------------------------------------------------
---------
To unsubscribe, e-mail: wsif-user-unsubscribews.apache.org
For additional commands, e-mail: wsif-user-helpws.apache.org

WSIF positioning relative to JAX-WS
user name
2006-10-18 11:29:32
Aleksander Slominski wrote:
cs.indiana.edu" type="cite">
Farrukh S. Najmi wrote:
  
Would someone from WSIF kindly repond to my inquiry at theserverside.com:

<http://www.theserverside.com/discussions/thread.tss?thread_id=42658>

Please post response on the above theserverside.com thread instead of
this mailing list.
  
    
here is what i posted:

"AFAIK Apache WSIL is no longer developed (and spec "dead")

WSIF is about taking WSDL and invoking any service described in it
irregardless of how the service is implemented (and that was
accomplished before SOA became buzzword). WSIF allows developers to use
the same API that reflects WSDL abstractions to access a service no
matter what protocol is used. WSIF can implement any protocol binding
(through WSIF providers) to allows interactions with a service solely
though its interface (PortType).

JAX-WS is Java implementation of set of WS-* technologies based on JAX-*
specs that is SOAP focused (main difference to WSIF - WSIF is not just
for SOAP) - AFAIK JAX-WS do not have multi-protocol or an abstraction
API of WSDL PortType as a goal. JAX-WS is also both for client and
server but WSIF is only clients side."
  
Thanks very much Alek for a clear response. I just posted these followup question:

1. Is WSIF project at Apache alive and under active development

2. Does WSIF still have a role in the SOA world of WSB and JBI?
It seems that the ESB concept achieves these goals of WSIF and JBI provides a
standard Java SPI for building a standards based ESB framework.

Again please respond on theserverside thread at:

<http://www.theserverside.com/discussions/thread.tss?m=c.reply&thread_id=42658#220529>

Thank you.
-- 
Regards,
Farrukh

Web: http://www.wellfleetsoftware.com

[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )