Steve Yes to make notification work your "client" needs to be a server. Axis1 and Axis2 both offer that capability through the "SimpleAxisServer" and "SimpleHttpServer".
There is also an implementation of WS-Eventing being created for Axis2, called Savan. WS-Eventing is a slightly simpler spec which is basically equivalent to BaseNotification. Paul On 11/27/06, Steve Kruse <[EMAIL PROTECTED]> wrote:
I've been looking into web services for a little while but can't seem to find any examples of what I am looking to do. I am looking to setup a web service that will be able to do a request-->multiple response type transaction. The response would be a continuous stream of data that the client would get via some type of callback. The WS-Notification paradigm seems to fit this model but I am having a hard time finding any examples. I have looked at pubscribe, but I'm not sure if it's doable, because I don't see how you can setup a standalone java client to listen for the responses. Is it true that the server and client need to be running a web service? If anyone can shed some light on how I could do this I would greatly appreciate it. Thanks in advance… Steve
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
