Didn't you create the XSOAP API or the pull parser it uses?both :-)
Do you think there would be any performance benefits of having wsif use your API instead of Axis, and if so, have you done such integration?i think that this is a deeper issue crosscutting both performance, usability and interoperability i.e. performance is not for free.
I haven't had the chance yet to use wsif or XSOAP, but plan on investigating both soon. I'd be interested in your thoughts in such integration possibilities.if you like AXIS you should stay with it *unless* you have very serious problems (and most of problems can be fixed either by code tweaking or faster machines!) as AXIS is de facto standard SOAP toolkit for Java.
i believe that as XML and SOAP define what goes on the wire so it is still possible to use different toolkits. i think that entry barrier is not high. so if you have requirements to use SOAP toolkits that may be better suited to your needs then i would just do it. that is exactly my motivation for XSOAP4 (that will soon replace XSOAP1) - see below on my angle on SOAP toolkits.
I can only assume that the wsif api is rather stable due to the limited activity in this list :)i think it is pretty stable.
I'm also curious what you're using wsif for since it looks like your extreme lab is doing a lot of research. I like the fact that you can abstract out the type of service ( e.g. local POJO, web service, JMS, EJB etc. ) via WSDL so that these services essentially become 'pluggable' without the client code having to know the implementation details.i am rather unhappy with complexity of current SOAP toolkits and particularly their monolithic structure. i think WSIF is a first good step in direction of pluggable WS toolkit though currently WSIF providers are hopelessly mingled together and it is not possible without a lot of work to compile a subset of WSIF providers.
the other limitation of WSIF that it is only client side API and sometimes it is good to have pluggability also on server side. lack of server side support led to very complicated and twisted tricks to get async transports such as JMS to work to correlate incoming messages in WSIF ...
so i wanted something that in its core is very modular to allow true plug&play or in OO words a toolkit that makes it easy to create and use web service by combining and extending existing modules. that is exactly how i designed XSOAP4. its alternative name is XSUL which stands for XML Services Utility Library and that is its philosophy: lot of pluggable modules.
you can read more about it at: http://www.extreme.indiana.edu/xgws/xsul/XSUL_Overview/
(in particular look on last slide where i show how JDK 1.5 can be used to have really nice DII in WSIF style working in XSUL)
I'm using OSGi services locally for such dynamic behavior, and would like to utilize wsif and/or XSOAP for remote method invocation / messaging.what is good web site to learn quickly about benefits of OSGi? what is URL for OSGi website ? is it http://www.osgi.org/?
thanks,
alek
-- The best way to predict the future is to invent it - Alan Kay
