[overlord-issues] [JBoss JIRA] Commented: (SOAG-95) Missing to generate the default reply queue in the jbmq-queue-service.xml
[
https://jira.jboss.org/jira/browse/SOAG-95?page=com.atlassian.jira.plugin...
]
Gary Brown commented on SOAG-95:
--------------------------------
The jboss-esb.xml snippet you have included is for a one-way request, so no response
expected.
We could potentially support synchronous invocation, but I think we would need to have a
separate action (e.g. InvokeAction), to distinguish between async one-way req, and sync
req/resp.
Alternatively, we should assume an async style (as now) and specify the response
category/name when a response is expected - this is my preference.
Shall I close the issue, with no action required?
Missing to generate the default reply queue in the
jbmq-queue-service.xml
-------------------------------------------------------------------------
Key: SOAG-95
URL: https://jira.jboss.org/jira/browse/SOAG-95
Project: SOA Governance
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Tooling
Affects Versions: 1.0 MR1
Reporter: Jeff Yu
Assignee: Gary Brown
Fix For: 1.0 MR2
In the current stateless actions generation mechanism, it doesn't generate the
'reply' queue, so it will cause the problem if it is request-response MEP. Because
in JBoss ESB, its default reply queue is: whatevername_reply.
like:
<mbean code="org.jboss.mq.server.jmx.Queue"
name="org.pi4soa.purchase.purchasegoods.destination:service=Queue,name=org_pi4soa_purchase_purchasegoods_PurchaseGoodsProcess_Store">
<depends optional-attribute-name="DestinationManager">
jboss.mq:service=DestinationManager
</depends>
</mbean>
The Reply queue should be:
<mbean code="org.jboss.mq.server.jmx.Queue"
name="org.pi4soa.purchase.purchasegoods.destination:service=Queue,name=org_pi4soa_purchase_purchasegoods_PurchaseGoodsProcess_Store_reply">
<depends optional-attribute-name="DestinationManager">
jboss.mq:service=DestinationManager
</depends>
</mbean>
--
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