Wouldn't it be easier with BPEL? Some kind of suscribe/publish message queue?
ActiveBPEL is a free open source BPEL orchestrator which uses axis to produce their web services. It would not be too hard to adapt your current web services with it. Daniel > The client probably needs to register once - otherwise how would the > service know where to send the stuff? So, a probable solution can be: > > 1. The client registers once and provides some means (some URI) where > the server will send its stuff - shouldn't be a synchronous procedure - > the server will either send something via ftp/gridFTP/SMTP etc...if you > make this synchronous, it means the client will also have to be > running... > > 2. The server continues to run, and sends the object or whatever at > specific times - can be implemented using timers/counters... > > Seems do-able... > > Cheers > Arijit > > > ________________________________ > > From: Suzy Fynes [mailto:[EMAIL PROTECTED] > Sent: 28 October 2004 12:11 > To: [EMAIL PROTECTED] > Subject: RE: Automating web service > > > Kinda of but an object would be sent to the client server. > > Is it do-able? > > -----Original Message----- > From: Arijit Mukherjee [mailto:[EMAIL PROTECTED] > > Sent: 28 October 2004 12:10 > To: [EMAIL PROTECTED] > Subject: RE: Automating web service > > Sounds like a notification service... > > Cheers > Arijit > > > ________________________________ > > From: Suzy Fynes [mailto:[EMAIL PROTECTED] > Sent: 28 October 2004 12:08 > To: [EMAIL PROTECTED] > Subject: Automating web service > > > Hi, > > Can anyone tell me if its possible to automate an axis > web service i.e. as oppose to a client making a request when they want > information that the service sends out the information daily > > Thanks > Suzy >
