[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:
--------------------------------
Don't believe this is an issue, as when a request/response MEP is used, the
SendMessageAction should explicitly provide the response service category/name to enable
the response to be received and processed by the correct service descriptor (same approach
as used in the stateful approach).
Can you give an example where you think this would be 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