[JBoss JIRA] Created: (SOAG-82) Move filter, used for service validator, from pi4soa into Overlord code base
by Gary Brown (JIRA)
Move filter, used for service validator, from pi4soa into Overlord code base
----------------------------------------------------------------------------
Key: SOAG-82
URL: https://jira.jboss.org/jira/browse/SOAG-82
Project: SOA Governance
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Behavioural Monitoring
Affects Versions: 1.0 MR2
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0 MR2
The service validator for jbossesb was originally developed before Project Overlord was established. However the models and configuration files that the service validators use are stored in the ESB bundle: overlord-cdl-validator.esb
When Overlord is installed, the ant script sets up the global filter currently using the class: org.pi4soa.jbossesb.validator.ValidatorFilter
As part of a separate task, to enable the service validators to use a "hot deployment" mechanism to update the configuration being monitored, I propose to move the Overlord specific aspects of the service validator into the Overlord code base.
The impact of this change will be the configuration of the global filter. This can be updated in the M2 release, so that when it is next installed, it will configure the Overlord version of the filter - however if the ant script is not used to do the upgrade to M2, it is possible that a user will experience a problem.
I believe we just need to document this in the release note, to ensure deployment of M2 is done using the ant scripts.
--
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
15 years, 8 months
[JBoss JIRA] Created: (SOAG-95) Missing to generate the default reply queue in the jbmq-queue-service.xml
by Jeff Yu (JIRA)
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
15 years, 9 months
[JBoss JIRA] Created: (SOAG-94) Missing generation of 'name', 'description', 'process' attributes in the esb stateless actions.
by Jeff Yu (JIRA)
Missing generation of 'name', 'description', 'process' attributes in the esb stateless actions.
-----------------------------------------------------------------------------------------------
Key: SOAG-94
URL: https://jira.jboss.org/jira/browse/SOAG-94
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 generated jboss-esb.xml file,
For the <service....> configuration, add the description="" for <service..> tag.
For the <action> configuration, add the name and process attributes. like:
<action name="s1" process="process" class="org.jboss.soa.overlord.jbossesb.stateless.actions.SwitchAction">
Currently, it is missing the 'name' and 'process' attributes, and it makes the jboss-esb.xml validation fail.
--
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
15 years, 9 months