August 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, 2 months

2
1
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, 5 months

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

2
7
0 / 0

[JBoss JIRA] Created: (SOAG-49) Initiate flag needs to be specified when generating a jboss-esb.xml

by Gary Brown (JIRA)

Initiate flag needs to be specified when generating a jboss-esb.xml ------------------------------------------------------------------- Key: SOAG-49 URL: https://jira.jboss.org/jira/browse/SOAG-49 Project: SOA Governance Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Currently the jboss-esb.xml does not indicate which path(s) in the MessageRouterAction represent the initial path that can initiate a session. This probably can be achieved using the lookahead analyser from the root choreography, to find the initial set of receive message actions, and then set the 'initiate' flag on the routes with the relevant message types. -- 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
3
0 / 0

[JBoss JIRA] Created: (SOAG-51) Packaging CDL related work

by Jeff Yu (JIRA)

Packaging CDL related work -------------------------- Key: SOAG-51 URL: https://jira.jboss.org/jira/browse/SOAG-51 Project: SOA Governance Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployment Reporter: Jeff Yu Assignee: Jeff Yu Fix For: 1.0 CR1 Need to write some build script to build. - cdl monitor esb artifact. - cdl jbossesb behaviour actions. - tools. - samples -- 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
4
0 / 0

[JBoss JIRA] Work started: (SOAG-34) Add example scenario description in README.txt

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-34?page=com.atlassian.jira.plugin... ] Work on SOAG-34 started by Jeff Yu. > Add example scenario description in README.txt > ---------------------------------------------- > > Key: SOAG-34 > URL: https://jira.jboss.org/jira/browse/SOAG-34 > 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 > > > Add example scenario description in README.txt -- 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

1
0
0 / 0

[JBoss JIRA] Work logged: (SOAG-39) Changes to error highlighting when displaying jboss-esb.xml error in XML editor

by Gary Brown (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-39?page=com.atlassian.jira.plugin... ] Gary Brown logged work on SOAG-39: ---------------------------------- Author: Gary Brown Created on: 20/Aug/08 11:35 AM Start Date: 20/Aug/08 11:34 AM Worklog Time Spent: 2 hours Work Description: Currently implemented capability to just flag the first line of the service or action associated with an error. Issue is that mechanism for focusing on an ESB service, action or property may be different depending upon whether text editor, current tabbed property based editor (in JBoss Tools) or the new graphical editor is used. Need to investigate the best way to enable any editor type to be supported. Issue Time Tracking ------------------- Remaining Estimate: 0 minutes Time Spent: 2 hours > Changes to error highlighting when displaying jboss-esb.xml error in XML editor > ------------------------------------------------------------------------------- > > Key: SOAG-39 > URL: https://jira.jboss.org/jira/browse/SOAG-39 > 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 > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Currently an error on an action or property in the action results in the complete Action being highlighted as an error. > Suggestion is to just highlight the first line of the Action, if the error is related to the complete action, or highlight the property within the action if property related. > However, if a graphical editor is being used to show the ESB config, then focusing on the complete action (i.e. graphical component) may be all that is possible, as Eclipse does not provide default behaviour for focusing on individual properties. -- 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

1
0
0 / 0

[JBoss JIRA] Work started: (SOAG-39) Changes to error highlighting when displaying jboss-esb.xml error in XML editor

by Gary Brown (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-39?page=com.atlassian.jira.plugin... ] Work on SOAG-39 started by Gary Brown. > Changes to error highlighting when displaying jboss-esb.xml error in XML editor > ------------------------------------------------------------------------------- > > Key: SOAG-39 > URL: https://jira.jboss.org/jira/browse/SOAG-39 > 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 an error on an action or property in the action results in the complete Action being highlighted as an error. > Suggestion is to just highlight the first line of the Action, if the error is related to the complete action, or highlight the property within the action if property related. > However, if a graphical editor is being used to show the ESB config, then focusing on the complete action (i.e. graphical component) may be all that is possible, as Eclipse does not provide default behaviour for focusing on individual properties. -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (SOAG-45) Updates of 'MessageRouterAction'

by Jeff Yu (JIRA)

[ https://jira.jboss.org/jira/browse/SOAG-45?page=com.atlassian.jira.plugin... ] Jeff Yu resolved SOAG-45. ------------------------- Resolution: Done > Updates of 'MessageRouterAction' > -------------------------------- > > Key: SOAG-45 > URL: https://jira.jboss.org/jira/browse/SOAG-45 > 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 > Fix For: 1.0 CR1 > > > 1. Currently the 'identities' elements are contained at the same level as the 'message' elements - however the set of identities will be specific to the message type > 2. The 'serviceDescriptionName' attribute should be a property on the MessageRouterAction, as opposed to an attribute on the 'route' element, as it will be the same across all routes. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues August 2008