April 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-181) Add ArtifactGroup and instantiate one in the maven wagon

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-181?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-181. ------------------------------- > Add ArtifactGroup and instantiate one in the maven wagon > -------------------------------------------------------- > > Key: SRAMP-181 > URL: https://issues.jboss.org/browse/SRAMP-181 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > When uploading multiple artifacts to S-RAMP, create a ArtifactGroup as a parent for the artifacts. Do we need to parse the parent pom? I'm not really sure how much state we have to build the relations to and from the parent to the children. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-181) Add ArtifactGroup and instantiate one in the maven wagon

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-181?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-181. --------------------------------- Resolution: Done > Add ArtifactGroup and instantiate one in the maven wagon > -------------------------------------------------------- > > Key: SRAMP-181 > URL: https://issues.jboss.org/browse/SRAMP-181 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > When uploading multiple artifacts to S-RAMP, create a ArtifactGroup as a parent for the artifacts. Do we need to parse the parent pom? I'm not really sure how much state we have to build the relations to and from the parent to the children. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-181) Add ArtifactGroup and instantiate one in the maven wagon

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-181?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-181: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/233 > Add ArtifactGroup and instantiate one in the maven wagon > -------------------------------------------------------- > > Key: SRAMP-181 > URL: https://issues.jboss.org/browse/SRAMP-181 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > When uploading multiple artifacts to S-RAMP, create a ArtifactGroup as a parent for the artifacts. Do we need to parse the parent pom? I'm not really sure how much state we have to build the relations to and from the parent to the children. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-182) Make artifact type detection less generic (atom layer)

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-182: ----------------------------------- Summary: Make artifact type detection less generic (atom layer) Key: SRAMP-182 URL: https://issues.jboss.org/browse/SRAMP-182 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Atom Binding, Core Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.2.0 - Milestone 4 Currently the artifact type detection methods are very generic and do not consider the context. There are two basic scenarios where an artifact type must be detected from an Atom Entry: 1) atom summary entries 2) full atom entries In the former case we need to figure out the type based on meta-data in the Entry, such as the URL, or from the 'x-s-ramp:2010:type' Category (for example) In the latter case, we should look at the wrapped artifact itself (there will be an <artifact> custom element in the Atom Entry with a single child - that single child is the full artifact meta-data, and the element name will indicate the type). Currently we just try both under all circumstances. I want to change from "getArtifactTypeFromEntry" to two methods: getArtifactTypeFromSummaryEntry getArtifactTypeFromFullEntry Callers must know what they have (summary or full). This should be known in all cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-65) Create shared Overlord UI header

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMPUI-65: ------------------------------------ Summary: Create shared Overlord UI header Key: SRAMPUI-65 URL: https://issues.jboss.org/browse/SRAMPUI-65 Project: S-RAMP UI Issue Type: Feature Request Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: Milestone 4 Take the current header and move it into a shared Overlord component. This will allow all Overlord UI projects to share the basic top nav bar (including login information, etc). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-181) Add ArtifactGroup and instantiate one in the maven wagon

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-181?page=com.atlassian.jira.plugin.... ] Work on SRAMP-181 started by Eric Wittmann. > Add ArtifactGroup and instantiate one in the maven wagon > -------------------------------------------------------- > > Key: SRAMP-181 > URL: https://issues.jboss.org/browse/SRAMP-181 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kurt Stam > Assignee: Eric Wittmann > Fix For: 0.2.0 - Milestone 4 > > > When uploading multiple artifacts to S-RAMP, create a ArtifactGroup as a parent for the artifacts. Do we need to parse the parent pom? I'm not really sure how much state we have to build the relations to and from the parent to the children. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-25) BPEL activity collector

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-25?page=com.atlassian.jira.plugin.s... ] Gary Brown updated RTGOV-25: ---------------------------- Priority: Critical (was: Major) > BPEL activity collector > ----------------------- > > Key: RTGOV-25 > URL: https://issues.jboss.org/browse/RTGOV-25 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M5 > > > Create an ActivityCollector to obtain information associated with the execution of a BPEL process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-20) Define the BPM activity model components

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-20?page=com.atlassian.jira.plugin.s... ] Gary Brown updated RTGOV-20: ---------------------------- Priority: Critical (was: Major) > Define the BPM activity model components > ---------------------------------------- > > Key: RTGOV-20 > URL: https://issues.jboss.org/browse/RTGOV-20 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M5 > > > Define a set of appropriate BPM related activity events to represent generic events that occur within a process engine. > These events will be required to describe the activities associated with the switchyard bpel (Riftsaw) and bpm (jBPM) components. > One of the objectives of these events should be to help trace the flow of information through a process. So when information is received (i.e. a received message), it would be useful to know the variable in which it is stored, and how subsequent variable values are derived from this initial information. Also expression evaluation for decision making could be useful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-161) Simplify db configuration

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-161?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-161: ----------------------------- Priority: Critical (was: Major) > Simplify db configuration > ------------------------- > > Key: RTGOV-161 > URL: https://issues.jboss.org/browse/RTGOV-161 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Jeff Yu > Priority: Critical > Fix For: 1.0.0.M5 > > > In the M4 release, there were two persistence-unit definitions, one for a JTA datasource and one for a non-JTA datasource. All details are the same for both, the only difference is whether the datasource is JTA. > This was necessary, because using H2 out of the box (for simple initial usage), only supports non-JTA. > Specification of which entity manager (i.e. persistence unit) to use is defined in the overlord-rtgov.properties file. > Ideally there should just be a single persistence-unit, and the data source (whether JTA or not) should be defined in a single place (i.e. overlord-rtgov.properties). > However when the datasource info is moved to the properties file, it causes a problem as hibernate is being used to populate the schema for the H2 db. This appears to be causing hibernate to create its own entity manager, which does not take into account the properties in the overlord-rtgov.properties file. However that is the file where the "hibernate.hbm2ddl.auto=create-drop" property is defined??? > If it is possible to remove datasource from persistence.xml, then it may also be good to package the persistence.xml in the activity-store-jpa module? rather than when building the overlord-rtgov.war. > Main reason this has become an issue is that there is now a JPA based event processor, where the user can specify the entity manager, and persist received events. However when using the H2 db, it again becomes necessary to define a second persistent unit for the non-JTA datasource, and change the entity manager (i.e. persistence unit name) depending upon the db used in the event processor's configuration. > So would like to simplify the whole approach so that persistence-unit only lists the classes, and the datasource, dialect, etc are all defined in one place (preferrably the overlord-rtgov.properties file), so that when switching between H2 and JTA dbs, the details only have to be changed in the one place. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-127) Support MySQL and Postgres

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-127?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-127: ----------------------------- Summary: Support MySQL and Postgres (was: Test BAM against MySQL) Priority: Critical (was: Major) Description: Need to create db schema and test support for MySQL and Postgres. > Support MySQL and Postgres > -------------------------- > > Key: RTGOV-127 > URL: https://issues.jboss.org/browse/RTGOV-127 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Priority: Critical > Fix For: 1.0.0.M5 > > > Need to create db schema and test support for MySQL and Postgres. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues April 2013