May 2009 - overlord-issues - Jboss List Archives

[JBoss JIRA] Created: (SOAG-96) Stateless jboss-esb.xml generated incorrectly for Broker example, when perform set to async

by Gary Brown (JIRA)

Stateless jboss-esb.xml generated incorrectly for Broker example, when perform set to async ------------------------------------------------------------------------------------------- Key: SOAG-96 URL: https://jira.jboss.org/jira/browse/SOAG-96 Project: SOA Governance Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 1.0 MR1 Reporter: Gary Brown Assignee: Gary Brown The ESBBroker example, Broker role - when generated as a stateless ESB service, the jboss-esb.xml is not as expected when the perform inside the while loop is async. The expected behaviour is correctly generated when the perform is synchronous. Need to investigate why this is inverted, and what the correct behaviour should be in both cases. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (SOAG-78) Rebuild conversation aware sample jboss-esb.xml configurations to be based on generated version

by Gary Brown (JIRA)

Rebuild conversation aware sample jboss-esb.xml configurations to be based on generated version ----------------------------------------------------------------------------------------------- Key: SOAG-78 URL: https://jira.jboss.org/jira/browse/SOAG-78 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: WS-CDL Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0 MR2 Samples for conversation aware actions should be based on generated version, to make it easier for end-user to generate a new skeleton of the behaviour from the choreography, and compare it against the fully implemented version. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (SOAG-108) Migrate pi4soa based Service Validator to Scribble monitor

by Gary Brown (JIRA)

Migrate pi4soa based Service Validator to Scribble monitor ---------------------------------------------------------- Key: SOAG-108 URL: https://jira.jboss.org/jira/browse/SOAG-108 Project: SOA Governance Issue Type: Task Security Level: Public (Everyone can see) Components: Behavioural Monitoring Affects Versions: 1.0 MR3 Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0 MR3 Currently the use of the pi4soa monitor within the service validator means that only a WS-CDL (i.e. CDM) description can be used to monitor the behaviour of a service against a choreography. A scribble based monitor would be able to perform runtime service validation from a range of source representations. As part of doing this work, the service validation architecture should also be changed to feed off the service activity event model, instead of being co-located with the service. -- 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, 7 months

1
1
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

14 years, 11 months

1
6
0 / 0

[JBoss JIRA] Created: (SOAG-74) Investigate BPEL deployment against various vendor

by Jeff Yu (JIRA)

Investigate BPEL deployment against various vendor -------------------------------------------------- Key: SOAG-74 URL: https://jira.jboss.org/jira/browse/SOAG-74 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 1.0 MR2 Reporter: Jeff Yu Assignee: Jeff Yu Need to investigate the various BPEL runtime's deployment, such as ActiveBPEL, Apache ODE and other closed source BPEL runtime. -- 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, 1 month

1
5
0 / 0

[JBoss JIRA] Updated: (SOAG-33) Timeout functionality for WhenAction

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-33?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-33: ------------------------ Affects Version/s: 1.0 MR1 > Timeout functionality for WhenAction > ------------------------------------ > > Key: SOAG-33 > URL: https://jira.jboss.org/jira/browse/SOAG-33 > Project: SOA Governance > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Affects Versions: 1.0 MR1 > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0 CR1 > > > Timeout functionality for WhenAction -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SOAG-31) Using pojo class as a parameter to get the correct session for having same service description name.

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-31?page=com.atlassian.jira.plugin... ] Jeff Yu updated SOAG-31: ------------------------ Fix Version/s: 1.0 MR3 Affects Version/s: 1.0 MR1 > Using pojo class as a parameter to get the correct session for having same service description name. > ---------------------------------------------------------------------------------------------------- > > Key: SOAG-31 > URL: https://jira.jboss.org/jira/browse/SOAG-31 > Project: SOA Governance > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Affects Versions: 1.0 MR1 > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0 MR3 > > > Using pojo class as a parameter to get the correct session for having same service description 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

15 years, 1 month

1
0
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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (SOAG-73) race condition in the join of ParallelAction

by Jeff Yu (JIRA)

race condition in the join of ParallelAction -------------------------------------------- Key: SOAG-73 URL: https://jira.jboss.org/jira/browse/SOAG-73 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 Fix For: 1.0 MR2 Right now, it is having race condition in the join of ParallelAction, detail please see http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196217#4196217 -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (SOAG-101) Making CDL runtime can be deployed against SOA-P

by Jeff Yu (JIRA)

Making CDL runtime can be deployed against SOA-P ------------------------------------------------- Key: SOAG-101 URL: https://jira.jboss.org/jira/browse/SOAG-101 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0 MR1 Reporter: Jeff Yu Assignee: Jeff Yu Fix For: 1.0 MR2 two sub-tasks: 1. Add jbm-queue-sevice.xml, as SOA-P is using the JBoss Messaging as JMS Provider. 2. Add jbm-queue-service.xml in every example, and also in the common-build.xml need to determine whether it is a JBossMQ or JBoss Messaging. -- 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, 2 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2009