3:44 a.m.
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
3:46 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2913) Only one JMS endpoint accessible when more available
[
https://jira.jboss.org/jira/browse/JBESB-2913?page=com.atlassian.jira.plu...
]
Lukáš Petrovický updated JBESB-2913:
------------------------------------
Attachment: Quickstart_webservice_consumer1.esb
The enhanced QS
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Attachments: Quickstart_webservice_consumer1.esb
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
5:02 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2913) Only one JMS endpoint accessible when more available
[
https://jira.jboss.org/jira/browse/JBESB-2913?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2913:
-------------------------------------
We had never intended to support publishing of contracts for JMS endpoints so this seems
to have sneaked in.
It will be removed from the contract page.
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Attachments: Quickstart_webservice_consumer1.esb
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
5:15 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-2913) Only one JMS endpoint accessible when more available
[
https://jira.jboss.org/jira/browse/JBESB-2913?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-2913:
--------------------------------
Fix Version/s: 4.7 CP1
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Fix For: 4.7 CP1
Attachments: Quickstart_webservice_consumer1.esb
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
9:49 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2913) Only one JMS endpoint accessible when more available
[
https://jira.jboss.org/jira/browse/JBESB-2913?page=com.atlassian.jira.plu...
]
David Ward reassigned JBESB-2913:
---------------------------------
Assignee: David Ward
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Assignee: David Ward
Fix For: 4.7 CP1
Attachments: Quickstart_webservice_consumer1.esb
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
3:31 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2913) Only one JMS endpoint accessible when more available
[
https://jira.jboss.org/jira/browse/JBESB-2913?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-2913:
------------------------------
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=164839
Added forum discussion.
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Assignee: David Ward
Fix For: 4.7 CP1
Attachments: Quickstart_webservice_consumer1.esb, service-list.png
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
3:31 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2913) Only one JMS endpoint accessible when more available
[
https://jira.jboss.org/jira/browse/JBESB-2913?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-2913:
------------------------------
Attachment: service-list.png
Attached screenshot of fixed contract JSP application.
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Assignee: David Ward
Fix For: 4.7 CP1
Attachments: Quickstart_webservice_consumer1.esb, service-list.png
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
3:33 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-2913) Only one JMS endpoint accessible when more available
[
https://jira.jboss.org/jira/browse/JBESB-2913?page=com.atlassian.jira.plu...
]
David Ward closed JBESB-2913.
-----------------------------
Resolution: Done
$ pwd
/home/dward/repos/jbossesb/branches/JBESB_4_7_CP/product/contract-web/src/main/webapp
$ svn commit
Sending webapp/contract.jsp
Sending webapp/index.jsp
Transmitting file data ..
Committed revision 30616.
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Assignee: David Ward
Fix For: 4.7 CP1
Attachments: Quickstart_webservice_consumer1.esb, service-list.png
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
4:45 a.m.
New subject: [JBoss JIRA] Reopened: (JBESB-2913) Only one JMS endpoint accessible when more available
[
https://jira.jboss.org/jira/browse/JBESB-2913?page=com.atlassian.jira.plu...
]
Kevin Conner reopened JBESB-2913:
---------------------------------
Assignee: Kevin Conner (was: David Ward)
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Assignee: Kevin Conner
Fix For: 4.7 CP1
Attachments: Quickstart_webservice_consumer1.esb, service-list.png
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
9:31 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2913) Only one JMS endpoint accessible when more available
[
https://jira.jboss.org/jira/browse/JBESB-2913?page=com.atlassian.jira.plu...
]
Kevin Conner reassigned JBESB-2913:
-----------------------------------
Assignee: David Ward (was: Kevin Conner)
Going with the workaround, needs to be verified before closing.
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Assignee: David Ward
Fix For: 4.7 CP1
Attachments: Quickstart_webservice_consumer1.esb, service-list.png
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
10:49 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-2913) Only one JMS endpoint accessible when more available
[
https://jira.jboss.org/jira/browse/JBESB-2913?page=com.atlassian.jira.plu...
]
David Ward closed JBESB-2913.
-----------------------------
Resolution: Done
Workaround verified.
Only one JMS endpoint accessible when more available
----------------------------------------------------
Key: JBESB-2913
URL: https://jira.jboss.org/jira/browse/JBESB-2913
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
Assignee: David Ward
Fix For: 4.7 CP1
Attachments: Quickstart_webservice_consumer1.esb, service-list.png
Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service
with two different JMS listeners:
<jms-provider name="JBossMQ"
connection-factory="ConnectionFactory">
...
<jms-bus busid="quickstartEsbChannel">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb" />
</jms-bus>
<jms-bus busid="quickstartEsbChannel2">
<jms-message-filter dest-type="QUEUE"
dest-name="queue/quickstart_webservice_consumer1_esb2" />
</jms-bus>
</jms-provider>
...
<listeners>
<jms-listener name="JMS-ESBListener"
busidref="quickstartEsbChannel"/>
<jms-listener name="JMS-ESBListener2"
busidref="quickstartEsbChannel2"/>
...
</listeners>
Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service
correctly with two endpoints
(jms:localhost:1099#queue/quickstart_webservice_consumer1_esb,
jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these
endpoints share the same WSDL and that only contains a port for the first listener:
...
<service name="HelloWorldWSService">
<port binding="tns:HelloWorldBinding" name="HelloWorldPort">
<soap:address
location="jms:/#queue/quickstart_webservice_consumer1_esb"/>
</port>
</service>
...
--
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
5430
days inactive
5514
days old
10 comments
3 participants
participants (3)
-
David Ward (JIRA) -
Kevin Conner (JIRA)
-
Lukáš Petrovický (JIRA)