overlord-issues August 2009

overlord-issues@lists.jboss.org

1 participants
35 discussions

[JBoss JIRA] Closed: (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 closed SOAG-31. ----------------------- Resolution: Won't Fix As we removed the stateful conversational esb actions, this task is no long valid. > 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, 4 months

1
0
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, 4 months

1
6
0 / 0

[JBoss JIRA] Closed: (SOAG-36) Add support in WhileAction for decision based on received message type

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-36?page=com.atlassian.jira.plugin... ] Jeff Yu closed SOAG-36. ----------------------- Resolution: Won't Fix As we removed the stateful conversational esb actions, this task is no long valid. > Add support in WhileAction for decision based on received message type > ---------------------------------------------------------------------- > > Key: SOAG-36 > URL: https://jira.jboss.org/jira/browse/SOAG-36 > Project: SOA Governance > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Affects Versions: 1.0 CR1 > Reporter: Gary Brown > Assignee: Jeff Yu > > For the current examples, the WhileAction only needs to evaluate an expression as the basis for deciding whether to loop or not. > In other examples however, it will be necessary for a service to be able to determine whether to loop based on receiving one or more message types. This could be expressed as follows: > <while service-category="ESBBroker.BrokerParticipant" > service-name="ESBBrokerProcess.main.2" > immediate="true" > > <message type="...." /> > <message type="...." /> > </while> > Although the SwitchAction can be used to represent this type of behaviour (i.e. paths selected based on message type), explicitly defining the fact that it should support repetition behaviour means that less mistakes will be made, as validation can ensure that looping behaviour is only permitted when the target service descriptor is a WhileAction. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (SOAG-30) Control Action has the capability of having 'identity' properties.

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-30?page=com.atlassian.jira.plugin... ] Jeff Yu closed SOAG-30. ----------------------- Resolution: Done > Control Action has the capability of having 'identity' properties. > ------------------------------------------------------------------ > > Key: SOAG-30 > URL: https://jira.jboss.org/jira/browse/SOAG-30 > Project: SOA Governance > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0 CR1 > > > For any control actions, it is able to have the 'identity' properties to retrieve the session, detail see the JBoss Forum Reference. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (SOAG-30) Control Action has the capability of having 'identity' properties.

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-30?page=com.atlassian.jira.plugin... ] Jeff Yu commented on SOAG-30: ----------------------------- As we removed the stateful conversational esb actions, this task is no long valid. > Control Action has the capability of having 'identity' properties. > ------------------------------------------------------------------ > > Key: SOAG-30 > URL: https://jira.jboss.org/jira/browse/SOAG-30 > Project: SOA Governance > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Conversation Runtime > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0 CR1 > > > For any control actions, it is able to have the 'identity' properties to retrieve the session, detail see the JBoss Forum Reference. -- 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, 4 months

1
0
0 / 0

← Newer
1
2
3
4
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues August 2009