You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Deepal Jayasinghe <de...@opensource.lk> on 2006/04/04 11:16:39 UTC

[Axis2]Small changing in Service implementation class

Hi all;

To support the scenario describe by the JIRA
http://issues.apache.org/jira/browse/AXIS2-341 , it is require to do
small changes into service implementation class.

   In the current code base in order to get access to message context he
has to add init method , and if the init method is present , it will
call for each and every invocation. (init method can take one message
context or two message context). I propose to change that to get
operation context instead of message context and rename method to  
    setOperationContext(OperationContext opctx);


When the session get start up , the init() method of the service class
will be called (using reflection) if it is present. And method will be
given the serviceContext corresponds to that service.

    init(ServiceContext serviceCtx)

When the session get invalidate destroy method of the service impl class
will be called if it present giving ServiceContext as argument.

  destroy(ServiceContext serviceCtx);

-- 
Thanks,
Deepal
................................................................
~Future is Open~