[jboss-dev-forums] [Design of JBoss ESB] - Re: Http Gateway - requirements please...

[tfennelly]

What makes sense to me is something like the following...

1. Allowing the context to be the bus specific part, defined on the bus (in the provider section) and allowing it to be whatever the user decides i.e. no artifical constraints/prefixes such as "http" etc.

2. Allowing the urlPattern to be a listener specific "filter" that filters certain requests off the bus (context) referenced by the listener's busrefid.  Again, this can be whatever the user decides.

In the case of EBWS, there wouldn't be an explicit bus or listener definition, so it's context and urlPattern could be something implied from the service definition e.g. context as "ebws" and listener urlPattern as "${service.category}/${service.name}" etc ?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245056#4245056

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245056