You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wsif-user@ws.apache.org by Jeff Greif <jg...@alumni.princeton.edu> on 2004/01/31 17:12:54 UTC
WSIFInterceptor
Grepping the WSIF 2.0 source reveals no methods that take WSIFInterceptor arguments. Hence I speculate that these cannot be established in any invocation. Is it true that WSIFInterceptors are a future feature that cannot be used yet? Has something changed in this regard since the 2.0 release?
Also, I cannot find any nightly builds of WSIF since September 2003. Is WSIF moribund or is there a glitch in the automatic build process?
Jeff
Re: WSIF Stubs question
Posted by Leo Barcenas <le...@sd-net.co.jp>.
Thanks.
I think I know the reason why. It's totally not related to
WSIF. I was running a different program that is not running
well. Thanks again.
Leo
----- Original Message -----
From: "Aleksander Slominski" <as...@cs.indiana.edu>
To: <ws...@ws.apache.org>
Sent: Wednesday, February 11, 2004 9:07 AM
Subject: Re: WSIF Stubs question
> leo wrote:
>
> >hi!
> >
> >I am using WSIF in accessing a web service. The process is a
> >24-hour service. There is a constant access to the web service.
> >We are on a long-run testing but, my program could not access the
> >service after around 10 to 15 hours. I am just wondering if I need to
> >close the connection to the service just like on database connections.
> >If yes, how? Do I just have to set the WSIF service object to NULL or
> >there is some other way that I should do?
> >
> >
> hi leo,
>
> i do not think there is anything special in WSIF and if there is error
> it would be WSIF provider specific (like AXIS).
>
> what is the error you get? did you try to google it?
>
> alek
>
> --
> The best way to predict the future is to invent it - Alan Kay
>
>
Re: WSIF Stubs question
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
leo wrote:
>hi!
>
>I am using WSIF in accessing a web service. The process is a
>24-hour service. There is a constant access to the web service.
>We are on a long-run testing but, my program could not access the
>service after around 10 to 15 hours. I am just wondering if I need to
>close the connection to the service just like on database connections.
>If yes, how? Do I just have to set the WSIF service object to NULL or
>there is some other way that I should do?
>
>
hi leo,
i do not think there is anything special in WSIF and if there is error
it would be WSIF provider specific (like AXIS).
what is the error you get? did you try to google it?
alek
--
The best way to predict the future is to invent it - Alan Kay
WSIF Stubs question
Posted by leo <le...@sd-net.co.jp>.
hi!
I am using WSIF in accessing a web service. The process is a
24-hour service. There is a constant access to the web service.
We are on a long-run testing but, my program could not access the
service after around 10 to 15 hours. I am just wondering if I need to
close the connection to the service just like on database connections.
If yes, how? Do I just have to set the WSIF service object to NULL or
there is some other way that I should do?
Hoping for your help.
Thanks in advance.
Leo
Re: WSIFInterceptor
Posted by Paul Russell <wo...@paulrussell.org>.
>> Is it true that WSIFInterceptors are a future feature that cannot be
>> used yet? Has something changed in this regard since the 2.0
>> release?
>
> unfortunately there is no more work done on interceptors. i think
> they are (were?) actually used in IBM WebSphere but they are
> configured by using WebSphere proprietary hooks to install
> interceptors.
>
My understanding is that the interfaces is used in the IBM Web Services
Gateway product (which I think is part of WebSphere 5.0 Network
Deployment edition). I submitted a patch to the developers list a while
back which allowed people to write a custom WSIFServiceFactory. I used
this to write a set of wrappers that break out into an interception
framework. Unfortunately, the wrappers and framework itself were
written at work, so I can't give them to you directly. I can provide
some hints, however.
This patch has not been incorporated into the codebase yet, but I'm
more than happy to send it to you if you'd like to apply it manually.
Paul
--
Paul Russell
work@paulrussell.org
Re: WSIFInterceptor
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Jeff Greif wrote:
> Grepping the WSIF 2.0 source reveals no methods that take
> WSIFInterceptor arguments. Hence I speculate that these cannot be
> established in any invocation.
that is correct but see below on intended usage.
> Is it true that WSIFInterceptors are a future feature that cannot be
> used yet? Has something changed in this regard since the 2.0 release?
unfortunately there is no more work done on interceptors. i think they
are (were?) actually used in IBM WebSphere but they are configured by
using WebSphere proprietary hooks to install interceptors.
so for now the only functionality that
WSIFInterceptor/WSIFInterceptorConfig provides is to standardize
interceptor interface and its configuration.
alek
--
The best way to predict the future is to invent it - Alan Kay
Re: WSIFInterceptor
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Jeff Greif wrote:
> Grepping the WSIF 2.0 source reveals no methods that take
> WSIFInterceptor arguments. Hence I speculate that these cannot be
> established in any invocation.
that is correct but see below on intended usage.
> Is it true that WSIFInterceptors are a future feature that cannot be
> used yet? Has something changed in this regard since the 2.0 release?
unfortunately there is no more work done on interceptors. i think they
are (were?) actually used in IBM WebSphere but they are configured by
using WebSphere proprietary hooks to install interceptors.
so for now the only functionality that
WSIFInterceptor/WSIFInterceptorConfig provides is to standardize
interceptor interface and its configuration.
alek
--
The best way to predict the future is to invent it - Alan Kay
nightly builds [Re: WSIFInterceptor]
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Jeff Greif wrote:
> Also, I cannot find any nightly builds of WSIF since September 2003.
> Is WSIF moribund or is there a glitch in the automatic build process?
after website was reorganized i think it never got setup back to work.
it seems that axis has exactly the same problem (as you found out)
http://ws.apache.org/axis/interim.html
http://cvs.apache.org/dist/axis/nightly/
you can get recent CVS snapshots but i guess it is into what you want.
http://cvs.apache.org/snapshots/ws-wsif/
i will look and check if i can get some nightly build going back again.
did you try to build WSIF from CVS. it is quite straightforward and
should be well documented?
thanks,
alek
--
The best way to predict the future is to invent it - Alan Kay