Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ. As of October 27th, please open all new issues in the Red Hat Customer Portal .
This issue on the FUSE forum puzzles me.
Why does the end user have to set mep=in-out as option to be able to have the JBI webservice return a reply?
http://fusesource.com/forums/message.jspa?messageID=6333#6333
Gert V. maybe you can shed some light on this?
The issue described in the forum is a user error, as already explained in the post by dkruitbosch:
If you create a route that says from("jbi:endpoint://").wireTap(...), you have exposed another endpoint in the ESB. The MessageExchange will now go to the new endpoint (so you have the wiretap), but it will never reach the original endpoint.
In order to do this, you have to do
from("jbi:enpoint://<the new endpoint name>").wireTap(...).to("jbi:endpoint://<the original endpoint name>")
This will make the new endpoint exposed by the camel route forward exchanges to the original endpoint the user wants to target.
There was another issue lurking in here though: the mep parameter, when used on a consumer endpoint, gets appended to the endpoint name. I have fixed that in https://issues.apache.org/activemq/browse/SMXCOMP-737 so the parameter gets ignored for a consumer endpoint.
Gert Vanthienen added a comment - 20/Apr/10 09:47 AM The issue described in the forum is a user error, as already explained in the post by dkruitbosch:
If you create a route that says from("jbi:endpoint://").wireTap(...), you have exposed another endpoint in the ESB. The MessageExchange will now go to the new endpoint (so you have the wiretap), but it will never reach the original endpoint.
In order to do this, you have to do
from("jbi:enpoint://<the new endpoint name>").wireTap(...).to("jbi:endpoint://<the original endpoint name>")
This will make the new endpoint exposed by the camel route forward exchanges to the original endpoint the user wants to target.
There was another issue lurking in here though: the mep parameter, when used on a consumer endpoint, gets appended to the endpoint name. I have fixed that in https://issues.apache.org/activemq/browse/SMXCOMP-737 so the parameter gets ignored for a consumer endpoint.
Task
Resolved
Minor
MEP parameter gets appended to service/endpoint name
If you create a route that says from("jbi:endpoint://").wireTap(...), you have exposed another endpoint in the ESB. The MessageExchange will now go to the new endpoint (so you have the wiretap), but it will never reach the original endpoint.
In order to do this, you have to do
from("jbi:enpoint://<the new endpoint name>").wireTap(...).to("jbi:endpoint://<the original endpoint name>")
This will make the new endpoint exposed by the camel route forward exchanges to the original endpoint the user wants to target.
There was another issue lurking in here though: the mep parameter, when used on a consumer endpoint, gets appended to the endpoint name. I have fixed that in https://issues.apache.org/activemq/browse/SMXCOMP-737
so the parameter gets ignored for a consumer endpoint.