events in Webservices

[Alexey Krivitsky <AK...@MIRATECH.UA>]

Hello all,
 
I am going to implements Webservices which will be sending notification
messages to their client.
The major issue is that it is required for the clients to be simple
non-servlet-based applications.
 
I am thinking of implementing a simple web-server (http listener)
which will receive, parse and process XML messages sent by the server as
standard SOAP calls.
 
Is there any standard already implemented solution for this approach? 
Can be apache axis/apache soap adopted to be used on the client's side?
 
 
Thanks!
Alexey.
 
 
 

Re: events in Webservices

[Alex Dovlecel <do...@kbs.twi.tudelft.nl>]

Forgot to mention, AXIS has a stand alone server (that allows you to use it 
without a Servlet Container), and I suppose you could try to integrate it 
into your clients. Dunno much about this, the people inhere are saying that 
in fact was build more for testing purposes... you should ask (or check) more 
on this... 

dovle 
> Hi,
>
> Have you considered the next posibility that will avoid implementing an
> HttpListener on your client: the client could call, from time to time, the
> server to check if there are some events for it.
>
> It could be a little troubling because might be too much net traffic but...
>
> On clientside, you should use the save tool as the server (for example
> axis) because you will be shure you will not have any interop problems.
> :o)))
>
> But axis is 'quite' big and I could sugest you some smaller clients (only
> clients!!!) for example ksoap :o))) It's smaller, works fast enough (i
> think) but you will need some patience in order to use it. :o)))
>
> (It seems that I am a big kSoap fan, sorry if I mention this product
> alot...).
>
> Hope it helps but wait for some more qualified people to say their
> oppinion. dovle
>
> > I am going to implements Webservices which will be sending notification
> > messages to their client.
> > The major issue is that it is required for the clients to be simple
> > non-servlet-based applications.
> >
> > I am thinking of implementing a simple web-server (http listener)
> > which will receive, parse and process XML messages sent by the server as
> > standard SOAP calls.
> >
> > Is there any standard already implemented solution for this approach?
> > Can be apache axis/apache soap adopted to be used on the client's side?
> >
> >
> > Thanks!
> > Alexey.

Re: events in Webservices

[Alex Dovlecel <do...@kbs.twi.tudelft.nl>]

Forgot another thing. 

When talking about ksoap, I was in fact saying it will be easy to implement 
the HttpListener and use the kSoap for parsing and mapping all the classes 
for you app... 

Sorry if I start spamming this list, DON'T BAN ME :o))) Pls. 
dovle 

> Hi,
>
> Have you considered the next posibility that will avoid implementing an
> HttpListener on your client: the client could call, from time to time, the
> server to check if there are some events for it.
>
> It could be a little troubling because might be too much net traffic but...
>
> On clientside, you should use the save tool as the server (for example
> axis) because you will be shure you will not have any interop problems.
> :o)))
>
> But axis is 'quite' big and I could sugest you some smaller clients (only
> clients!!!) for example ksoap :o))) It's smaller, works fast enough (i
> think) but you will need some patience in order to use it. :o)))
>
> (It seems that I am a big kSoap fan, sorry if I mention this product
> alot...).
>
> Hope it helps but wait for some more qualified people to say their
> oppinion. dovle
>
> > I am going to implements Webservices which will be sending notification
> > messages to their client.
> > The major issue is that it is required for the clients to be simple
> > non-servlet-based applications.
> >
> > I am thinking of implementing a simple web-server (http listener)
> > which will receive, parse and process XML messages sent by the server as
> > standard SOAP calls.
> >
> > Is there any standard already implemented solution for this approach?
> > Can be apache axis/apache soap adopted to be used on the client's side?
> >
> >
> > Thanks!
> > Alexey.

Re: events in Webservices

[Alex Dovlecel <do...@kbs.twi.tudelft.nl>]

Hi,

Have you considered the next posibility that will avoid implementing an 
HttpListener on your client: the client could call, from time to time, the 
server to check if there are some events for it. 

It could be a little troubling because might be too much net traffic but... 

On clientside, you should use the save tool as the server (for example axis) 
because you will be shure you will not have any interop problems. :o))) 

But axis is 'quite' big and I could sugest you some smaller clients (only 
clients!!!) for example ksoap :o))) It's smaller, works fast enough (i think) 
but you will need some patience in order to use it. :o))) 

(It seems that I am a big kSoap fan, sorry if I mention this product 
alot...). 

Hope it helps but wait for some more qualified people to say their oppinion.
dovle 


> I am going to implements Webservices which will be sending notification
> messages to their client.
> The major issue is that it is required for the clients to be simple
> non-servlet-based applications.
>
> I am thinking of implementing a simple web-server (http listener)
> which will receive, parse and process XML messages sent by the server as
> standard SOAP calls.
>
> Is there any standard already implemented solution for this approach?
> Can be apache axis/apache soap adopted to be used on the client's side?
>
>
> Thanks!
> Alexey.