Uploaded image for project: 'FUSE ESB'
  1. FUSE ESB
  2. ESB-1180

MEP parameter gets appended to service/endpoint name

    Details

      Description

      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?

        Gliffy Diagrams

          Activity

          Hide
          gertv Gert Vanthienen added a comment -

          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.

          Show
          gertv Gert Vanthienen added a comment - 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.
          Hide
          gertv Gert Vanthienen added a comment -

          Merged into FUSE branches in

          • rev. 13752 for the 3.3.1 branch
          • rev. 13750 for the components trunk
          • rev. 13807 for the components 2009.01.x branch
          Show
          gertv Gert Vanthienen added a comment - Merged into FUSE branches in rev. 13752 for the 3.3.1 branch rev. 13750 for the components trunk rev. 13807 for the components 2009.01.x branch

            People

            • Assignee:
              gertv Gert Vanthienen
              Reporter:
              davsclaus Claus Ibsen
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: