[jboss-jira] [JBoss JIRA] Commented: (JBESB-280) Gateway listeners cannot be registered under the same name as their message aware counterparts
Tom Fennelly (JIRA)
jira-events at jboss.com
Thu Dec 21 07:45:39 EST 2006
[ http://jira.jboss.com/jira/browse/JBESB-280?page=comments#action_12349191 ]
Tom Fennelly commented on JBESB-280:
------------------------------------
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 :-)
> Gateway listeners cannot be registered under the same name as their message aware counterparts
> ----------------------------------------------------------------------------------------------
>
> Key: JBESB-280
> URL: http://jira.jboss.com/jira/browse/JBESB-280
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ESB Core
> Affects Versions: 4.0 RC1
> Reporter: Tom Fennelly
> Assigned To: Mark Little
> Fix For: 5.0
>
>
> The Gateways need to be registered under a completely different name than the message aware "Service " listener they are fronting.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list