April 2013 - overlord-issues - Jboss List Archives

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

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-65?page=com.atlassian.jira.plugin... ] Eric Wittmann closed SRAMPUI-65. -------------------------------- > 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, 8 months

1
0
0 / 0

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

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-65?page=com.atlassian.jira.plugin... ] Eric Wittmann resolved SRAMPUI-65. ---------------------------------- Resolution: Done Checked in changes in both overlord-commons and s-ramp-ui to support this. > 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, 8 months

1
0
0 / 0

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

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-65?page=com.atlassian.jira.plugin... ] Eric Wittmann updated SRAMPUI-65: --------------------------------- Git Pull Request: https://github.com/Governance/s-ramp-ui/pull/69 > 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, 8 months

1
0
0 / 0

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

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/RTGOV-127?page=com.atlassian.jira.plugin.... ] Jeff Yu resolved RTGOV-127. --------------------------- Resolution: Done > 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: Jeff Yu > 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, 8 months

1
0
0 / 0

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

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/RTGOV-127?page=com.atlassian.jira.plugin.... ] Jeff Yu commented on RTGOV-127: ------------------------------- Yes, I'll resolve it now. > 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: Jeff Yu > 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, 8 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 reassigned RTGOV-127: -------------------------------- Assignee: Jeff Yu (was: Gary Brown) Hi Jeff, can this be marked as resolved now? > 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: Jeff Yu > 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, 8 months

1
0
0 / 0

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

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/RTGOV-127?page=com.atlassian.jira.plugin.... ] Jeff Yu commented on RTGOV-127: ------------------------------- I added two wiki pages about changing the database to MySQL and postgreSQL at: https://github.com/Governance/rtgov/wiki/MySQLDatabaseConfiguration and https://github.com/Governance/rtgov/wiki/PostgresqlDatabaseConfiguration > 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, 8 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 resolved RTGOV-161. ------------------------------ Resolution: Done Thanks for sorting this out Jeff. > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-175) Add CDI transaction interceptor to ActivityServerImpl to control txn scope

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-175?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-175. ------------------------------ Resolution: Done > Add CDI transaction interceptor to ActivityServerImpl to control txn scope > -------------------------------------------------------------------------- > > Key: RTGOV-175 > URL: https://issues.jboss.org/browse/RTGOV-175 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > > Currently the REST service for the ActivityServer takes responsibility for managing the txn scope - but when activity server impl is directly injected, this is bypassed - so need to inject txn interceptor on the activity server impl to control txn scope regardless of which approach is used to access the server. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-176) Extract transactional annotation and CDI interceptor into common module

by Gary Brown (JIRA)

Gary Brown created RTGOV-176: -------------------------------- Summary: Extract transactional annotation and CDI interceptor into common module Key: RTGOV-176 URL: https://issues.jboss.org/browse/RTGOV-176 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M5 Currently they are defined in the activity-server-impl module, as there were deployment issues when they were included in the rtgov-common module. Need to fix issues to enable them to be shared with other transactional CDI beans. -- 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, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues April 2013