Hi Michele;
pls see my comments below;

Michele Mazzucco wrote:

>Hi all,
>
>sorry for flooding you with all these messages. Could be a possible
>solution to implement the handler before the dispatch phase, eventually
>creating the AxisService object (say, because the service is not
>provided here)?
>  
>
of course you can , Apache Synapse is doing smt similar to this. In
Synapse what ever message come to that it will dispatch into the same
service by adding a handler before Axis2 dispatchers.

>If the service is not available my idea is to change the target service
>to a "well known" service, after saving the initial informations.
>The well known service provides routing capabilities, according to
>informations (i.e. which node provides which service) and eventually
>according to policies as well.
>
>Does it make any sense?
>  
>
I think what you are tryng to do is exactly what the synapse is doing .

>Thanks in advance,
>Michele
>
>Michele Mazzucco wrote:
>  
>
>>Hi all,
>>
>>the problem seems to be, according to [1], that the dispatch phase
>>throws an error if the service is not present. The possible solution is
>>to move the phase just before the dispatch phase, however in this case
>>the AxisService returned by msgContext.getAxisService() is NULL.
>>
>>
>>Best regards,
>>Michele
>>
>>
>>[1] http://ws.apache.org/axis2/1_0/Axis2ArchitectureGuide.html
>>
>>
>>Michele Mazzucco wrote:
>>    
>>
>>>Hi all,
>>>
>>>I would like to intercept messages from clients (on the server side) to
>>>redirect them (eventually to other servers, if the target selected by
>>>the client doesn't provide the required service)
>>>
>>>
>>>client ---> S_handler | S
>>>
>>>The problem is that my interceptor works only if the service required by
>>>the client is available on 'S'.
>>>
>>>The handler is configured as global module in axis2.xml and phases are
>>>ok (I need only the in and in fault phases, and my phases are before
>>>'OperationInPhase' and 'OperationInFaultPhase').
>>>
>>>
>>>Any idea?
>>>
>>>Thanks in advance,
>>>Michel
>>>
>>>---------------------------------------------------------------------
>>>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]
>>
>>    
>>
>
>---------------------------------------------------------------------
>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]

Reply via email to