Re: Any plans for...

Alek:

> key client side abstractions i have prorotyped are XService (that 
> represents a local objects that provides access to a service described 
> in a WSDL):

I'm thinking that there would be value in keeping the client and server side 
stuff separate.  Or at least modular enough that you can pick/choose which 
you want.

I expect more folks will want the WSIF-style client invocation API rather 
than the server side service implementation stuff.  Primarily because there 
are already a lot of toolkits that generate the latter.

> think about it as a *prototype* for next-gen WSIF - if there is 
> something useful then it may be used (or improved) in the next WSIF

Ah!  Now I understand.  Excellent!

> direction and everything else depends on users and where they want to 
> take it ... it is that simple and WSIF definitely needs more active 
> developers :)

+1 on that.  

No decisions yet, and given how close the Xmas season is, I might not make a 
decision till after the holidays.  

But I am tempted by the thought of extending the inventory of WSIF providers 
to include REST/HTTP (I believe Oracle has this already...sad that they 
haven't donated it back to the WSIF project), ebXML Message Service and also 
updates to be able to handle the impending WSDL 2.0 spec.


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