It is now time to revisit this work so we need to nail down the requirements. These are
the requirements as I see them.
The purpose of this work is to provide a gateway into the ESB using http as the transport
mechanism.
We are not writing extensible frameworks to support any transport but, as the current
implementation choice is to use a servlet, we should be modifying the current EBWS
codebase to share some of the implementation details. We should be deploying a single war
file which should have its urls divided into ebws and http sections (perhaps /ebws/* and
/http/* or more suitable)
All configuration must be done from within the jboss-esb.xml file, with any deployment
artifacts (for example web.xml) being generated solely by the ESB. The HTTP gateway
functionality must include the following
- Configurable support for the following verbs: DELETE, HEAD, GET, POST, PUT and automatic
support for OPTIONS
- security, covering the following: authentication, transport guarantees, security
constraints
- security integrating with Daniel's work
- url patterns
- Configurable synchronous/asynchronous behaviour (mep, timeout, async response)
- No specific servlet integration (e.g. filters/listeners)
There will probably be areas of this that needs to be fleshed out further, but this should
provide the integration we need without exposing the specific details of the
implementation.
Kev
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244908#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...