WSIF, a long term API?

[zaplin <za...@freesurf.ch>]

Hi,
Is WSIF an early  framework, obvisously successful and of great value,  
destined to be have the bulk of its functionality subsumed by emerging 
JSR's? This is of course not a bad fate for a pioneering framework.

I ask because WSIF would meet my needs for an upcoming development but I 
am uncertain if starting a new development with WSIF is the best 
strategy with regards to Java API compliance. In particular, I would 
develop my own provider, a great feature of this framework.

Thanks for insights,
z

Re: WSIF, a long term API?

[Aleksander Slominski <as...@cs.indiana.edu>]

zaplin wrote:

> Is WSIF an early  framework, obvisously successful and of great 
> value,  destined to be have the bulk of its functionality subsumed by 
> emerging JSR's? This is of course not a bad fate for a pioneering 
> framework.

:-) i do not know enough about future JSRs but i think as long as you 
have compatible WSDL descriptions there should be no problem with 
interoperability no matter what API you use (or like).

> I ask because WSIF would meet my needs for an upcoming development but 
> I am uncertain if starting a new development with WSIF is the best 
> strategy with regards to Java API compliance. In particular, I would 
> develop my own provider, a great feature of this framework.

i agree - i always wonted ot make WSIF more modular. i think no WSIF 
gratest value is its clear focus on WSDL.

alek

-- 
The best way to predict the future is to invent it - Alan Kay