April 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMPUI-51) Artifact Details - Classifiers (mutable)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-51?page=com.atlassian.jira.plugin... ] Eric Wittmann resolved SRAMPUI-51. ---------------------------------- Resolution: Done > Artifact Details - Classifiers (mutable) > ---------------------------------------- > > Key: SRAMPUI-51 > URL: https://issues.jboss.org/browse/SRAMPUI-51 > Project: S-RAMP UI > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Provide a way to modify the classifiers assigned to the artifact in the Artifact Details page. See the UI mockup for details. -- 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-51) Artifact Details - Classifiers (mutable)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-51?page=com.atlassian.jira.plugin... ] Eric Wittmann closed SRAMPUI-51. -------------------------------- > Artifact Details - Classifiers (mutable) > ---------------------------------------- > > Key: SRAMPUI-51 > URL: https://issues.jboss.org/browse/SRAMPUI-51 > Project: S-RAMP UI > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Provide a way to modify the classifiers assigned to the artifact in the Artifact Details page. See the UI mockup for details. -- 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-164) Deploying the wars

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-164?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-164: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> changed the Status of [bug 950589|https://bugzilla.redhat.com/show_bug.cgi?id=950589] from MODIFIED to ON_QA > Deploying the wars > ------------------ > > Key: RTGOV-164 > URL: https://issues.jboss.org/browse/RTGOV-164 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Affects Versions: 1.0.0.M4 > Reporter: Nick Cross > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > Attachments: RTGOV-164.patch > > > Allow those artifacts that generate war files (content/epn, content/acs, release/jbossas/war-*) to deploy i.e. remove maven-deploy-plugin skip=true. -- 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-164) Deploying the wars

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-164?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-164: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> made a comment on [bug 950589|https://bugzilla.redhat.com/show_bug.cgi?id=950589] Fix has been applied - the individual wars are now deployed to maven repo and can be accessed from there. Fix will be available in next alpha build. > Deploying the wars > ------------------ > > Key: RTGOV-164 > URL: https://issues.jboss.org/browse/RTGOV-164 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Affects Versions: 1.0.0.M4 > Reporter: Nick Cross > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > Attachments: RTGOV-164.patch > > > Allow those artifacts that generate war files (content/epn, content/acs, release/jbossas/war-*) to deploy i.e. remove maven-deploy-plugin skip=true. -- 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-163) Simulation support

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-163?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-163: ---------------------------------- Checkout http://bpsim.org/ > Simulation support > ------------------ > > Key: RTGOV-163 > URL: https://issues.jboss.org/browse/RTGOV-163 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.1 > > > Provide simulation capabilities related to an end-to-end SOA implemented business flow. > Source information for the simulation could be savara scenarios, or information captured from previous executions of the business transaction. > Purpose will be to profile how individual parts of the system react under different load with different performance profiles. Where some parts of the system are resource constrained, this information should also be recorded, to understand where bottlenecks may occur. If those resources are people, then need to model the groups/sizes/calendars etc. > If there is a financial consequence of the business transaction, this should be monitored, to enable different simulation profiles to reflect the impact on the financial situation. -- 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 Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/RTGOV-161?page=com.atlassian.jira.plugin.... ] Jeff Yu commented on RTGOV-161: ------------------------------- I used the mysql database to test, and found it also having the following exception. ====================================================================================== 01:17:38,290 SEVERE [org.overlord.rtgov.activity.store.jpa.JPAActivityStore] (MSC service thread 1-2) Failed to create entity manager 'overlord-rtgov-activity': java.lang.NullPointerException at org.hibernate.engine.transaction.internal.jta.JtaStatusHelper.getStatus(JtaStatusHelper.java:73) [hibernate-core-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.engine.transaction.internal.jta.JtaStatusHelper.isActive(JtaStatusHelper.java:115) [hibernate-core-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.engine.transaction.internal.jta.CMTTransaction.join(CMTTransaction.java:149) [hibernate-core-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.ejb.AbstractEntityManagerImpl.joinTransaction(AbstractEntityManagerImpl.java:1207) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.ejb.AbstractEntityManagerImpl.postInit(AbstractEntityManagerImpl.java:176) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.ejb.EntityManagerImpl.<init>(EntityManagerImpl.java:89) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.ejb.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:125) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.ejb.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:120) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final] at org.overlord.rtgov.activity.store.jpa.JPAActivityStore.init(JPAActivityStore.java:136) [activity-store-jpa-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_10] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_10] > 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-161) Simplify db configuration

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/RTGOV-161?page=com.atlassian.jira.plugin.... ] Jeff Yu commented on RTGOV-161: ------------------------------- I am thinking about using the H2 embedded connection (file based), which seems to support JTA. Sorry that I didn't solve this question directly, but if I make it jta working with H2, that might be easier according to your research. :) I am going to try it first now, and then report it back. Regards 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] (SRAMPUI-50) Artifact Details - Core Properties (mutable)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-50?page=com.atlassian.jira.plugin... ] Eric Wittmann closed SRAMPUI-50. -------------------------------- > Artifact Details - Core Properties (mutable) > -------------------------------------------- > > Key: SRAMPUI-50 > URL: https://issues.jboss.org/browse/SRAMPUI-50 > Project: S-RAMP UI > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Enhance the artifact details page such that the appropriate core properties are mutable. Use JIRA as a model for how this can be done seamlessly? -- 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-50) Artifact Details - Core Properties (mutable)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-50?page=com.atlassian.jira.plugin... ] Work on SRAMPUI-50 stopped by Eric Wittmann. > Artifact Details - Core Properties (mutable) > -------------------------------------------- > > Key: SRAMPUI-50 > URL: https://issues.jboss.org/browse/SRAMPUI-50 > Project: S-RAMP UI > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Enhance the artifact details page such that the appropriate core properties are mutable. Use JIRA as a model for how this can be done seamlessly? -- 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-50) Artifact Details - Core Properties (mutable)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-50?page=com.atlassian.jira.plugin... ] Eric Wittmann resolved SRAMPUI-50. ---------------------------------- Resolution: Done > Artifact Details - Core Properties (mutable) > -------------------------------------------- > > Key: SRAMPUI-50 > URL: https://issues.jboss.org/browse/SRAMPUI-50 > Project: S-RAMP UI > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: Milestone 4 > > > Enhance the artifact details page such that the appropriate core properties are mutable. Use JIRA as a model for how this can be done seamlessly? -- 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