On 9/15/06, robert lazarski <robertl= azarski@gmail.com> wrote:

That makes sense to me. I've been using startUp() and it doesn't
really = fit with the other methods of the interface in its current
form. +1 for = 1.1 since its interface changes and it'd be better to do
it now.

One question: Currently you need this in services.xml to get startUp()<= br>to invoke:

<parameter name=3D"load-on-startup" locke= d=3D"false">true</parameter>

I plan on testing th= is when its ready ... since the spring tutorial
depends on it ... so I thought I'd ask if the services.xml param willremain the same.

Thanks,
Robert

On 9/14/06, Deepal Jayas= inghe <deepal@opensource.lk > wrote:
> Hi All;
>
> Currently we have an interface = called Service and which has few methods
> that are used to manage se= ssion (or else user can add those method into
> service impl class=20 w.o implementing the interface). And that interface
> has the followi= ng methods ;
>
> - startUp
> - init
> - setOperatio= nContext
> - destroy
>
> Three of them are for managing s= ervice life cycle ;
> - init =96 will be called when the session start
> - setOper= ationContext =96 immediately before calling actual java method
> - de= stroy =96 will be call when the session finishes
>
> Remember a= ll those method work if and only if you use Axis2 default
> message receiver or you code gen.
>
> The method start= Up is not session related method , which is useful when
> you want to= initialize database connections , create thread etc ... at
> the tim= e when you deploy the service. In the mean time interface name
> Service is bit confusing to me AFAIK it should be ServiceLifeCycle= . And
> having method like startUp in that interface confuses the use= rs.
>
> So how about the following changes ;
> - Rename S= ervice interface into ServiceLifeCycle
> - Then remove startUp method from that interface.
>
> = There should be a some other interface (like Module interface) and which> should be optional as well , to have the method startUp. If someone w= ant
> to open DB connection or anything at the time of service deploying= ,
> then he need to implement that interface (and for me which is id= entical
> to Module interface). So with this change service element i= nside the
> services.xml will be change to following
>
> <servi= ce name=3D"foo" *class=3D"implementation class of the interf= ace "*>
> <parameter name=3D"ServiceClass">Se= rviceClass</parameter>
> </service>
>
> Here the class attribute is optio= nal , so if someone want to have
> loadonStartup feature then he need= to implement the Service interface
> (new one) and put the impl name= as the class attribute. This is very
> useful if your service implementation class is not java (if you ar= e
> writing a groovy serice).
>
> So new Service interfac= e will be look like follows;
> public interface Service{
> //wi= ll be called when service is deployed
> public void startUp(ConfigurationContext configctx, AxisService se= rvice);
> //will be called when Axis2 server showdown or when service= removed from
> the system
> public void shutDown(Configuration= Context configctx, AxisService service);
> }
>
> And ServiceLifeCycle interface will look like be= low;
>
> public interface ServiceLifeCycle {
> public voi= d init(ServiceContext sc);
> public void setOperationContext(Operatio= nContext operationContext);
> void destroy(ServiceContext sc);
> }
>
>
>= I am +1 on doing this for Axis2 1.1 :)
>
> Suggestions .......= .
>
> Thanks
> Deepal
>
>
>
> ---= ------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional c= ommands, e-mail: axis-dev-he= lp@ws.apache.org
>
>

-----------------------------------------------= ----------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For = additional commands, e-mail:=20 axis-dev-help@ws.apache.org<= /a>