Red Hat Bugzilla – Bug 779557
HttpGateway add support for different connectors
Last modified: 2010-06-09 15:36:46 EDT
Affects: Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial Date of First Response: 2010-05-12 07:37:07 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/483553 project_key: SOA In JBoss SOA-P 5.0 the new HttpGateway states that it takes its connection information (bind and port address) from the jboss web container itself. However if the web container has more than one http connectors configured in the jbossweb.sar/server.xml (eg, one on 8080 the other on 8081), the HttpGateway does not support for different connectors.
Link: Added: This issue depends JBESB-3296
Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial]
Updated in ESB codebase, will be in next merge.
The following draft text has been added to the Release Notes: https://jira.jboss.org/browse/JBESB-3296 The HttpGateway could not support multiple connectors if more than one was configured in jbossweb.sar/server.xml. Support for multiple connectors bound to different port addresses has now been added.
Information on the allowedPorts property is yet in the ESB (or SOA-P) programmers' guide. We should point the readers/users to the http-gateway quickstart for an example: <service category="PortFilter01" name="List" description="" invmScope="GLOBAL"> <listeners> <!-- Receives: http://<host>:8081/Quickstart_http_gateway/http/ports01/* Uses the default http bus configuration The requests with http://<host>:8080/* will be returned with Status 404... --> <http-gateway name="PortFilter01" urlPattern="ports01/*"> <property name="allowedPorts" value="8081"/> </http-gateway> </listeners> <actions mep="RequestResponse"> <action name="print" class="org.jboss.soa.esb.samples.quickstart.httpgateway.MyAction"/> </actions> </service>
Verified in SOA-P 5.0.2 CR1 build