Uploaded image for project: 'JBoss ESB'
  1. JBoss ESB
  2. JBESB-280

Gateway listeners cannot be registered under the same name as their message aware counterparts

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Optional
    • Resolution: Unresolved
    • Affects Version/s: 4.0 CR1
    • Fix Version/s: None
    • Component/s: Rosetta
    • Labels:
      None

      Description

      The Gateways need to be registered under a completely different name than the message aware "Service " listener they are fronting.

        Gliffy Diagrams

          Activity

          Hide
          tfennelly Tom Fennelly added a comment -

          Shouldn't they all be registered under the same name, with protocol, message awareness etc all as properties of the registration?

          Show
          tfennelly Tom Fennelly added a comment - Shouldn't they all be registered under the same name, with protocol, message awareness etc all as properties of the registration?
          Hide
          marklittle Mark Little added a comment -

          Obviously the same gateway may also be servicing many different ESB-aware services.

          Show
          marklittle Mark Little added a comment - Obviously the same gateway may also be servicing many different ESB-aware services.
          Hide
          tfennelly Tom Fennelly added a comment -

          No the way they're currently implemented.

          1. This would require the target service to be specified in the incoming message (ESB unaware message) - currently set on the gateway configuration.
          2. It would also require the registry to return the same gateway EPR for all "service:name" combo's being serviced by a particular Gateway "instance" - basically, the gateway would need to be registered n times for each Service it's providing external access to (not really a problem of course).

          I think #1 there is probably the stickiest. I suppose you could achieve it be requiring the client to present the EPR it used to access the gateway, along with the message to be wrapped and routd to the target service. The Gateway could then figure out which service the message needs to be routed to from the EPR. Just a suggestion

          Show
          tfennelly Tom Fennelly added a comment - No the way they're currently implemented. 1. This would require the target service to be specified in the incoming message (ESB unaware message) - currently set on the gateway configuration. 2. It would also require the registry to return the same gateway EPR for all "service:name" combo's being serviced by a particular Gateway "instance" - basically, the gateway would need to be registered n times for each Service it's providing external access to (not really a problem of course). I think #1 there is probably the stickiest. I suppose you could achieve it be requiring the client to present the EPR it used to access the gateway, along with the message to be wrapped and routd to the target service. The Gateway could then figure out which service the message needs to be routed to from the EPR. Just a suggestion

            People

            • Assignee:
              marklittle Mark Little
              Reporter:
              tfennelly Tom Fennelly
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development