On Wed, May 28, 2008 at 10:27 PM, pratibhaG <[EMAIL PROTECTED]> wrote:
>
> Why did you suggest to use use that when the exchange is sent by the consumer
> the first time. Because in my case it will be different.
> I also have to use it when message is sent by provider.
> The message is like this
>
> 1)Listener will listen to all the messages on NMR
> 2)app1 sends message to app2 say <request><message>hello</message></request>
> 3)app2 will respond with either success or error
> The response can be <response><status>success</status></response> or it can
> be <response><status>error</status></response>
> Now my listener should take the "in" message as well as "out" message from
> app2 append them and send the appended message to the Error handler for
> further processing.
>
> that is listener should send message
> <message><request><message>hello</message></request><response><status>error</status></response></message>
> to service " {http://servicemix.abc.com/samples/http}MyErrorHandlingService
> "with endpoint "errorHandlerProviderEndpoint"
>
> I have achieved the message
> <message><request><message>hello</message></request><response><status>error</status></response></message>
>
> Now how to send it?
I had no idea the error to which you have been referring all this time
is not actually a JBI error - it's simply just an error within the
content of the normalized message!
This being the case, stop trying to handle all of this using the
exception listener I provided. Instead, just route the message through
a content-based router using either the servicemix-eip component or
the servicemix-camel component. This will allow you to test the
content of the normalized message and determine routing based on the
content.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/
