November 2008 - overlord-issues - Jboss List Archives

[JBoss JIRA] Created: (SOAG-50) Fix EP samples on Drools Fusion impl

by Heiko Braun (JIRA)

Fix EP samples on Drools Fusion impl ------------------------------------ Key: SOAG-50 URL: https://jira.jboss.org/jira/browse/SOAG-50 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: SAM Reporter: Heiko Braun Assignee: Heiko Braun <excludes> <exclude>org/jboss/test/sam/samples/pattern/PatternTestCase.java</exclude> <exclude>org/jboss/test/sam/samples/aggregation/FilteringTestCase.java</exclude> <exclude>org/jboss/test/sam/samples/falloff/FalloffTestCase.java</exclude> <exclude>org/jboss/test/sam/samples/aggregation/AggregationTestCase.java</exclude> </excludes> -- 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

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (SOAG-68) Async Perform

by Gary Brown (JIRA)

Async Perform ------------- Key: SOAG-68 URL: https://jira.jboss.org/jira/browse/SOAG-68 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Jeff Yu Currently the Brokerage example iterates through a list of suppliers to find the best quote, before proceeding to perform a credit check and complete the transaction. However the list of suppliers is processed using a loop containing a synchronous perform, so each supplier is dealt with in turn. The next step is to cater for an asynchronous perform, where the suppliers can be dealt with concurrently (i.e. so multiple sub-sessions active at the same time). This would require the 'WhenAction' to block, awaiting all of the sub-sessions to complete, before making its decision regarding the best quote. -- 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

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (SOAG-66) Represent the CDL Exception Handling concept with the 'conversation aware' ESB actions

by Gary Brown (JIRA)

Represent the CDL Exception Handling concept with the 'conversation aware' ESB actions -------------------------------------------------------------------------------------- Key: SOAG-66 URL: https://jira.jboss.org/jira/browse/SOAG-66 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Jeff Yu Currently the Exception Handling mechanism in CDL is not supported in the conversation aware ESB actions. -- 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

12 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (SOAG-65) Blocking/waiting behaviour for WhenAction

by Gary Brown (JIRA)

Blocking/waiting behaviour for WhenAction ----------------------------------------- Key: SOAG-65 URL: https://jira.jboss.org/jira/browse/SOAG-65 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Conversation Runtime Reporter: Gary Brown Assignee: Jeff Yu Currently the WhenAction does immediate evaluation of an expression. This construct needs to enable blocking/waiting behaviour if the expression evaluates to false - using the services of an external mechanism that can monitor an expression, and re-evaluate it whenever a change occurs to the state for the session, and then trigger the appropriate service descriptor once the expression does evaluate to true. The expression could also represent a timeout, and therefore this mechanism could be combined with the issue related to the WhenAction handling timeouts (SOAG-33). -- 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

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (SOAG-67) Conformance checking for CDL Exception Handling mechanism against 'conversation aware' ESB actions

by Gary Brown (JIRA)

Conformance checking for CDL Exception Handling mechanism against 'conversation aware' ESB actions -------------------------------------------------------------------------------------------------- Key: SOAG-67 URL: https://jira.jboss.org/jira/browse/SOAG-67 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Provide conformance checking between a CDL description with Exception Handling and the equivalent representing in an ESB configuration using 'conversation aware' ESB actions. -- 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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (SOAG-48) Web service support in conversation based actions

by Gary Brown (JIRA)

Web service support in conversation based actions ------------------------------------------------- Key: SOAG-48 URL: https://jira.jboss.org/jira/browse/SOAG-48 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Reporter: Gary Brown Assignee: Gary Brown Investigate impact on generation and conformance checking, as well as runtime actions. Main issue may be dealing with multipart messages. Identity token locators may need optional 'part' attribute to select the appropriate part by name. -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (SOAG-64) Deletion of grouping constructs

by Gary Brown (JIRA)

Deletion of grouping constructs ------------------------------- Key: SOAG-64 URL: https://jira.jboss.org/jira/browse/SOAG-64 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 1.0 CR1 Reporter: Gary Brown Assignee: Gary Brown Currently, deletion of actions from the jboss-esb.xml file only occurs for simple activities (e.g. sends/receives and perform). The problem with deleting grouping constructs is that, not only has the main construct got to be deleted, but the ESB service descriptors related to each path needs to be removed, potentially with further linked service descriptors. In some cases, it will also be necessary to identify the 'join' service descriptor, and insert a ScheduleStateAction to transition to this service descriptor. Where the join service descriptor not explicitly defined in the grouping construct, it may possibly be inferred based on the following following action in the description - if one has been defined. Otherwise it may have to be inferred by examining each path, to determine where they converge. -- 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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (SOAG-72) Business pojo class can't be hot-deploy

by Jeff Yu (JIRA)

Business pojo class can't be hot-deploy ---------------------------------------- Key: SOAG-72 URL: https://jira.jboss.org/jira/browse/SOAG-72 Project: SOA Governance Issue Type: Bug Security Level: Public (Everyone can see) Components: Conversation Runtime Affects Versions: 1.0 MR1 Reporter: Jeff Yu Assignee: Jeff Yu The steps to reproduce: 1. Deploy the overlord cdl to JBoss ESB. 2. Run the purchasing example. 3. Open the common/creditAgency/src/com/acme/services/creditAgency/CreditAgencyPurchase.java Make the isCreditValid() method return false; 4. Redeploy the creditAgency esb artifact. 5. The update won't take effect by using hot deploy. -- 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, 3 months

1
6
0 / 0

[JBoss JIRA] Created: (SOAG-46) Using JPA instead of Hibernate API directly

by Jeff Yu (JIRA)

Using JPA instead of Hibernate API directly ------------------------------------------- Key: SOAG-46 URL: https://jira.jboss.org/jira/browse/SOAG-46 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Conversation Runtime Affects Versions: 1.0 CR1 Reporter: Jeff Yu Assignee: Jeff Yu Might be better to use JPA instead of hibernate directly, which means need to use the hibernate-entityManager library. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (SOAG-47) Handle both XML and Java types between choreography and jboss-esb.xml descriptions

by Gary Brown (JIRA)

Handle both XML and Java types between choreography and jboss-esb.xml descriptions ---------------------------------------------------------------------------------- Key: SOAG-47 URL: https://jira.jboss.org/jira/browse/SOAG-47 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 1.0 CR1 Reporter: Gary Brown Assignee: Mark Little Currently CDL specifies XML elements/types for messages and variables. However jboss-esb.xml actions may be dealing with XML or Java objects on the pipeline. Also state variables associated with the business object type could be Java or XML. Need to decide how the types should be recorded in the choreography, and how they should be mapped to types in the generated jboss-esb.xml and supporting Java classes. -- 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, 11 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues November 2008