Re: WSIF positioning relative to JAX-WS

[Farrukh S. Najmi]

Aleksander Slominski wrote: 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]