[esb-issues] [JBoss JIRA] Updated: (JBESB-2471) Rearrange http-gateway to eliminate low level tomcat/jbossweb/coyote integration code
[
https://jira.jboss.org/jira/browse/JBESB-2471?page=com.atlassian.jira.plu...
]
Tom Fennelly updated JBESB-2471:
--------------------------------
Summary: Rearrange http-gateway to eliminate low level tomcat/jbossweb/coyote
integration code (was: Rearrange http-gateway to eliminate low level tom/jbossweb/coyote
integration code)
I spent the last week or so working on doing the http-gateway via sub deployments of the
main ESB deployment. So basically, all the ESB is doing is creating a .war archive for
each http bus and then deploying these as sub deployments of the ESB deployment. It
greatly simplifies the integration.
Rearrange http-gateway to eliminate low level tomcat/jbossweb/coyote
integration code
-------------------------------------------------------------------------------------
Key: JBESB-2471
URL: https://jira.jboss.org/jira/browse/JBESB-2471
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.5
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Fix For: 4.4 FP1
The new Http Gateway uses low level tomcat APIs to perform the integration. This is
quite complex and we feel may be quite brittle wrt changes in tomcat going forward.
Maintaining this would be probably be a bit of nightmare. It's not a reflection on
the integration code in the gateway. IMO, tomcat is simply not designed to be
embeddable, so no matter what, the code is going to be complex and quite difficult to
validate.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira