Re: Any plans for...

Alek:

> +1 and i help as much as i can (which sometimes is limited)

I can relate to that....my time is sometimes very limited as well, but it 
would be a shame to see WSIF wither away for lack of attention.

There have been some comments made about JBI eventually replacing WSIF, but 
upon reading the JBI spec, they seem pretty much orthogonal to me.  Though I 
suppose WSIF could be rearchitected to use JBI under the covers. I don't see 
much value to that approach at the moment.

> i played with some prototype WSIF extensions including advanced 
> correlation support, simple client side handlers, server side WSIF-like 
> services (based on WSDL - generate Java interface and all the rest is 
> done by pluggable service layer) etc. in XSUL2.  all code is under 
> BSD-like license and you can find examples and documentation at the 
> homepage.

I was thinking about server side WSIF-like services as well.  I'll take a 
look and see what you've come up with.

It seems like XSUL2 is intended as a next-gen replacement for WSIF?  How 
compatible is it with the WSIF interfaces?

The reason I ask is that my primary motivation for using WSIF on a current 
client project is to allow us to plug in external BPEL engines down the road, 
which all use WSIF to extend their BPEL integration to more than just classic 
SOAP Webservices.  Switching to a different API wouldn't work in that case.

> if it looks interesting maybe we can start a scratch project and get 
> some new APIs/providers done such as REST style WSIF?

I'm interested but not yet sure how much time/effort I want to devode to 
extending WSIF.  Partially based on limited spare time....and partially 
because I don't yet know enough about WSIF, it's future directions (if any), 
quality of the code base (haven't had a chance to look at the code much), 
etc.

I'll let you know...


Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com