Thanks! I'm thinking about invoking the "normal" way from the handler
creating the serviceclient, options etc...But I just need the original's
client's address in order to send the response to the client and not to the
handler, got it? ;-) So on outflow I'd have to change the reply address form
the handler's address to the client's address...
Thank you very much!
2008/10/15 Amila Suriarachchi <[EMAIL PROTECTED]>
>
>
> On Tue, Oct 14, 2008 at 10:17 PM, Igor Nogueira <
> [EMAIL PROTECTED]> wrote:
>
>>
>> Actually I want to develop a passive replication schema, so I have the
>> handlers together in a group. If the Active member fails, I'll have to
>> re-invoke the message, but in another handler in another server. I'm
>> serializing the Messagecontext and moving it through the replicas, so when
>> a
>> fault is detected I'll invoke the message again, but in another service .
>> Is
>> there a way to do that?I tryed to use LocalTranportSender, but it returns
>> me
>> a nullexception error...I've opened another thread on the list about
>> it...if
>> you have time, could you take a lokk at it too? ;-)
>
>
> I am not clear about your requirement. But may be looking at Axis2
> clustering would be usefull to you.
>
> thanks,
> Amila.
>
>>
>>
>> Thanks again!!!,
>>
>> Igor Nogueira
>>
>>
>> Amila Suriarachchi wrote:
>> >
>> > On Mon, Oct 13, 2008 at 4:29 PM, Igor Nogueira
>> > <[EMAIL PROTECTED]
>> >> wrote:
>> >
>> >> Amila, thank you! I've tested what you said, but I've got this
>> exception:
>> >> "A message was added that is not valid. However, the operation context
>> >> was
>> >> complete."
>> >>
>> >
>> > this means it try to add an Axis2 Message to an operation context which
>> > already has required number of Axis2 messages. This may happen when it
>> > goes
>> > through the dispatches again.
>> >
>> >>
>> >> Here's the code I'm using:
>> >>
>> >> contextomensagem.setCurrentHandlerIndex(0);
>> >> contextomensagem.setCurrentPhaseIndex(0);
>> >> AxisEngine engine = new
>> >> AxisEngine(contextomensagem.getConfigurationContext());
>> >> try {
>> >> engine.receive(contextomensagem);
>> >>
>> > you can simply called . AxisEngine.receive() since this is a static
>> > method.
>> >
>> >>
>> >> } catch (AxisFault e1) {
>> >>
>> >> e1.printStackTrace();
>> >> return (e1.getReason());
>> >> }
>> >>
>> >> "contextomensagem" is a static variable that keeps a copy of the
>> >> MessageContext received at the invoke method. As I'm testing I didin't
>> >> change the SOAPEnvelope, I'm just trying to re-send the same message.
>> Is
>> >> there something else to do?
>> >>
>> >
>> > Are you experimenting with Axis2 Engine or what do you try to archive?
>> why
>> > you want to send the same message twice?
>> >
>> > thanks,
>> > Amila.
>> >
>> >>
>> >>
>> >> Thanks!
>> >>
>> >
>> >
>> >
>> > --
>> > Amila Suriarachchi
>> > WSO2 Inc.
>> > blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/In-flow-request-insertion-tp19946886p19977558.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
