March 2009 - overlord-issues - Jboss List Archives

[JBoss JIRA] Created: (SOAG-75) Generate WS-BPEL from Choreography Description

by Gary Brown (JIRA)

Generate WS-BPEL from Choreography Description ---------------------------------------------- Key: SOAG-75 URL: https://jira.jboss.org/jira/browse/SOAG-75 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: WS-CDL Affects Versions: 1.0 MR2 Reporter: Gary Brown Assignee: Gary Brown Generate BPEL 2.0 process descriptions from a choreography description. NOTE: When this task has been completed, and the deployment framework has been built, then we might need to refactor the generation mechanism to identify commonality with the ESB Conversation Action mechanism. For now will keep the code bases separate until more information is known. -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (SOAG-85) Update ServiceValidator documentation to reflect change in Java package and configuration details

by Gary Brown (JIRA)

Update ServiceValidator documentation to reflect change in Java package and configuration details ------------------------------------------------------------------------------------------------- Key: SOAG-85 URL: https://jira.jboss.org/jira/browse/SOAG-85 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 Update the ServiceValidator documentation: 1) to reflect change in package from pi4soa to Overlord 2) change in configuration attributes (although existing attributes still supported for backward compatibility) 3) explicit configuration through annotations in choreography 4) dynamic (hot deployment) of updated validation configurations -- 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, 5 months

1
2
0 / 0

[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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (SOAG-83) Hot deployment of service validator configuration

by Gary Brown (JIRA)

Hot deployment of service validator configuration ------------------------------------------------- Key: SOAG-83 URL: https://jira.jboss.org/jira/browse/SOAG-83 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 Enable configuration used by the service validators in a JBossESB environment to be updated based on monitoring for changes in the validator-config.xml and CDL model files in the overlord-cdl-validator.esb. -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (SOAG-80) Build stateful fragment approach to JBoss ESB from CDL file.

by Jeff Yu (JIRA)

Build stateful fragment approach to JBoss ESB from CDL file. ------------------------------------------------------------ Key: SOAG-80 URL: https://jira.jboss.org/jira/browse/SOAG-80 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-CDL Affects Versions: 1.0 MR1 Reporter: Jeff Yu Assignee: Jeff Yu Fix For: 1.0 MR2 In the M2 release, we are going to try another approach with JBossESB. Compared to the conversation runtime actions that we had in M1, we will try to build a stateful fragment (or technically, we called it statless) approach to the JBossESB. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (SOAG-89) GettingStartedGuide Section 2.1.5 ends abruptly

by Mark Little (JIRA)

GettingStartedGuide Section 2.1.5 ends abruptly ----------------------------------------------- Key: SOAG-89 URL: https://jira.jboss.org/jira/browse/SOAG-89 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 1.0 MR1 Reporter: Mark Little Assignee: Mark Little Fix For: 1.0 MR2 Section 2.1.5 is little more than what you might expect in a Readme.txt within the sample. It doesn't sit well within the rest of Section 2. It either needs extending with a more detailed description of what is happening within the client and services when running (my preference) or removing entirely. -- 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, 5 months

2
4
0 / 0

[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, 6 months

2
5
0 / 0

[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, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2009