Hi,
Well it definitely seem to me as a out MEP and the service that Deepal is
referring to is kind of a active service I guess. I am not as yet sure
weather we need it badly, but this sheds light to the concept of the
MessageProducer in my mind.
IF we are to continue with this I believe we should come up with a
programming model for it. What I'm suggesting is may be a interface like
ActiveService
Public interface ActiveService extends Runnable{
Public void start();
Public void stop();
//.. Anymore???
}
Basically a kind of an IOC for the services with the MEP's OUT only, OUT-IN
, OUT-*
Comments??
THanks
Chathura
> -----Original Message-----
> From: Ajith Ranabahu [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 17, 2005 11:50 AM
> To: [email protected]
> Subject: Re: [Axis2] Out Message (Auto start web service)
>
> Does this mean we are having a dive at out bound MEPS mentioned in WSDL
> 2.0 ?
>
>
> On Thu, 17 Mar 2005 11:44:30 +0600, Deepal Jayasinghe
> <[EMAIL PROTECTED]> wrote:
> >
> > Hi all;
> >
> > I wrote a web service that sends message from server without getting any
> > request. and also I modified the DeploymentEngine to auto start the
> service
> > if it is to be so.
> > In order to be an auto run service its service.xml should have the
> following
> > parameter and service class should extend from Thread .
> >
> > <parameter name="OUTSERVICE" locked="xsd:true">true</parameter>
> >
> >
> > Note : I just extends the service class form Thread to show the ability
> of
> > wring a service which send out messages ( but latter it has to be
> implements
> > a well defined interface instated of extending from Thread.)
> >
> > ( This kind of web service is useful in sending announcement to
> subscribers
> > etc. )
> >
> >
> > Thanks,
> > Deepal.
>
>
> --
> Ajith Ranabahu
