Yes , you can register Listener in axis2.xml , and whenever service are
added to system them will be notify. So you can update your
configuration using that Listener.
Adding a listener is very easy you can do that as follows (remember that
listener need to implement org.apache.axis2.engine.AxisObserver interface)
<listener class="org.apache.axis2.ObserverIMPL">
<parameter name="myPara" locked="false">parameterValue</parameter>
</listener>
Michele Mazzucco wrote:
>Deepal,
>
>is there any way to add a listener so when the configuration is updated
>my stuff will automatically receive the news?
>
>Thanks,
>Michele
>
>Deepal Jayasinghe wrote:
>
>
>>It will at least take 10 s to update the axisConfguration after you
>>deploying the service .
>>
>>Michele Mazzucco wrote:
>>
>>
>>
>>>Hi all,
>>>
>>>I'm 'hot-deploying' new web services from a handler running as first in
>>>the Axis2 chain (before the transport phase).
>>>I detect the target service is not available by checking the axis
>>>configuration obtained this way:
>>>
>>>registry = messageContext.getConfigurationContext().getAxisConfiguration()
>>>
>>>and then
>>>
>>>AxisService target = registry.getService("foo")
>>>
>>>
>>>The problem is that after the hot-deployment the new service is not into
>>>registry? What should I do?
>>>
>>>
>>>
>>>
>>so need to wait 10s :)
>>
>>
>>
>>>Thanks in advance,
>>>Michele
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
