Hi Deepal, thanks for your reply. Please see my comments inline.
Deepal Jayasinghe wrote: > Hi Michele; > At the transport phase URL based dispatching is happening and Dispatch > phase other kind of dispatching happening. So once Axis2 find your > service you can do this re direction. This is the point! The service is *not provided* by the target set by the client. Instead, this is just a router node, so if I'm right your solution will fail, since the service is not available. Instead, I run my handler before the Transport phase. This way the RequestURIBasedDispatcher handler becomes redundant and thus it can be avoided (my handler updates the action as well, so I guess the SOAPActionBasedDispatcher handler is still necessary). Can you please confirm the correctness of my assumption? As I can see best solution is to > add a phase last handler into Dispatch phase to do this. > > So inside the handler logic you can check the message context and send > the message to actual target. > > Michele Mazzucco wrote: > >> Hi all, >> >> I would like to redirect client requests (eventually because the target >> node doesn't provide the required service), so I need to intercept them >> through a message handler. >> >> >> client ----> (handler -> pretended target) ----> real target (i.e. the >> node providing the service) >> >> Could anybody of the Axis2 guys suggest me the best solution to do this? >> At which level should I implement my interceptor, before the transport >> phase or before the dispatch one? >> >> >> Thanks in advance, >> Michele >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> Thanks, Michele >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
