JBossDeveloper

I give up!

OK... now that I've cooled off a little....

1. I am trying to keep the changes to a min.
2. I am trying to follow your design requests.
3. Maybe we can talk about broken assumptions later.
4. I will refactor so as to use a hardcoded "http" prefix on the urlPattern as requested.

I have it now that both the http gateway and EBWS endpoints are being deployed in the same war file. All Http Gateway endpoint urls are now prefixed with "http".

In terms of the changes to existing code... most of this involved removing code.

I haven't prefixed the EBWS endpoints with "ebws" yet - it's as it was. Do we really want to do this? If we do, then we need to provide backward compatibility support.

The changes can be viewed on the following workspace: http://anonsvn.jboss.org/repos/labs/labs/jbossesb/workspace/tfennelly/httpg2

If there are specific changes that you feel are not required, let me know the specific instance(s).

Ok, thanks.

So, as far as my understanding goes, there are no differences from a functional point of view (one query aside, which is below). I do have other parts to implement, but the merging of http and ebws is basically done and is done with min impact, as best I could.

I do want to make sure we're on the same page re what you want the urls for the http gateway endpoints to be. At the moment, I have it as:

http://{host}/{.esbname}/http/{urlPattern_from_listener_config}

http://{host}/{.esbname}/http/{service_cat}/{service_name}/{urlPattern_from_listener_config}

Ok thanks... both those options were mentioned but I missed the urlPattern override bit. That's fine, thanks.

So just to let people comment on how some of the security aspects might look....

Specifying the http authentication method for the deployment could look like this:

<http-provider name="http">
 <http-bus busid="ordermgt" />

 <auth method="BASIC" />
</http-provider>

<http-provider name="http">
 <http-bus busid="sales">
 <methods>
 <!-- Restrict access to the GET, POST and OPTIONS (auto) methods... -->
 <method name="GET" />
 <method name="POST" />
 </methods>
 <roles>
 <!-- Restrict access to authenticated members of the "salesAdmin" role... -->
 <role name="salesAdmin" />
 </roles>
 </http-bus>

 <auth method="BASIC" />
</http-provider>

<http-provider name="http">
 <http-bus busid="sales">
 <transport guarantee="CONFIDENTIAL" />
 </http-bus>
</http-provider>

OK... so I think I eventually got it generating the security bits. Was a bit of pita :)

It looks slightly different from above, but amounts to the same thing.

So the http-provider definition (inside the jboss-esb.xml) is now looking like....

<http-provider name="http">
 <http-bus busid="ordermgt" />

 <http-bus busid="sales">
 <allowed-roles>
 <role name="friend" />
 </allowed-roles>
 <protected-methods>
 <method name="GET" />
 </protected-methods>
 </http-bus>

 <auth method="BASIC" domain="java:/jaas/AcmeSecProvider" />
</http-provider>

Methods Specified | Roles Specified | Login Required
----------------------------------------------------------------------------
 No | No | No
 No | Yes | For All Methods
 Yes | Yes | For Specified Methods
 Yes | No | No - Specified Methods blocked to all

The old "using the mep" for sync/async responses chestnut again... Sorry Kev ;)

Here was what was said on IM that time...

(12:18:47) Tom Fennelly: another quick one... the mep issue
(12:18:55) Tom Fennelly: what was the issue with the?
(12:19:26) Tom Fennelly: you don't wanna use it to decide whether or not a respnse is sent back?
(12:19:33) Kevin Conner: The mep of the service has no bearing on the http gateway, it is an impleme
ntation config
(12:19:36) Kevin Conner: You can't
(12:19:57) Kevin Conner: A response can be sent back from a OneWay mep if it chains the request
(12:20:13) Kevin Conner: Service A (OneWay) -> Service B (RequestResponse)
(12:20:37) Kevin Conner: It is an implementation detail and not part of the service contract

Looks like we also need a way to map pipeline exceptions to http status codes, which makes sense I think.

This should be straightforward enough. I was thinking we could allow the user to define the exception mappings globally (at the http-provider) and then allow overrides at the listener level.

I wrote up some wiki docs for this new gateway here: http://www.jboss.org/community/wiki/HTTPGateway