September 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-279) Situation requires an explicitly defined ID

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-279?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-279. ------------------------------ Resolution: Done > Situation requires an explicitly defined ID > ------------------------------------------- > > Key: RTGOV-279 > URL: https://issues.jboss.org/browse/RTGOV-279 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Situation currently has a protected id set by Hibernate when the situation is persisted. However to enable Situations, that are created and published out as notifications, to be correlated back to the object stored in the db, we need to explicitly set the upon creation, to ensure the same ID is present when the object is published and persisted. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-279) Situation requires an explicitly defined ID

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-279?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-279: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> changed the Status of [bug 1011889|https://bugzilla.redhat.com/show_bug.cgi?id=1011889] from NEW to MODIFIED > Situation requires an explicitly defined ID > ------------------------------------------- > > Key: RTGOV-279 > URL: https://issues.jboss.org/browse/RTGOV-279 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Situation currently has a protected id set by Hibernate when the situation is persisted. However to enable Situations, that are created and published out as notifications, to be correlated back to the object stored in the db, we need to explicitly set the upon creation, to ensure the same ID is present when the object is published and persisted. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-279) Situation requires an explicitly defined ID

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-279?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-279: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> made a comment on [bug 1011889|https://bugzilla.redhat.com/show_bug.cgi?id=1011889] Assigning to Julian to notify about db schema changes. In a previous email thread with Steve Johnson he indicated that it would not be a problem as prod team will be using the schema tool driven by the persistence.xml content. To summarise: - Situation entity now has an explicit 'id' primary key field (string). - Tables are explicitly created as part of the rtgov installation (not relevant for prod). - overlord-rtgov-epn.war's persistence.xml has been updated to use JTA > Situation requires an explicitly defined ID > ------------------------------------------- > > Key: RTGOV-279 > URL: https://issues.jboss.org/browse/RTGOV-279 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Situation currently has a protected id set by Hibernate when the situation is persisted. However to enable Situations, that are created and published out as notifications, to be correlated back to the object stored in the db, we need to explicitly set the upon creation, to ensure the same ID is present when the object is published and persisted. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-279) Situation requires an explicitly defined ID

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-279?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-279: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> made a comment on [bug 1011889|https://bugzilla.redhat.com/show_bug.cgi?id=1011889] As part of the fix, changed the overlord-rtgv-epn to use a JTA based entity manager for the situation store, and fixed how the entity manager was handled in the JPAEventProcessor. > Situation requires an explicitly defined ID > ------------------------------------------- > > Key: RTGOV-279 > URL: https://issues.jboss.org/browse/RTGOV-279 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Situation currently has a protected id set by Hibernate when the situation is persisted. However to enable Situations, that are created and published out as notifications, to be correlated back to the object stored in the db, we need to explicitly set the upon creation, to ensure the same ID is present when the object is published and persisted. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-279) Situation requires an explicitly defined ID

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-279?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated RTGOV-279: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1011889 > Situation requires an explicitly defined ID > ------------------------------------------- > > Key: RTGOV-279 > URL: https://issues.jboss.org/browse/RTGOV-279 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > > Situation currently has a protected id set by Hibernate when the situation is persisted. However to enable Situations, that are created and published out as notifications, to be correlated back to the object stored in the db, we need to explicitly set the upon creation, to ensure the same ID is present when the object is published and persisted. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-280) Include overlord commons artifacts in distribution to avoid install from nexus

by Gary Brown (JIRA)

Gary Brown created RTGOV-280: -------------------------------- Summary: Include overlord commons artifacts in distribution to avoid install from nexus Key: RTGOV-280 URL: https://issues.jboss.org/browse/RTGOV-280 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.M1 -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-110) Derived flag incorrect for extended derived artifacts

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-110?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on SRAMPUI-110: ------------------------------------------------- Eric Wittmann <eric.wittmann(a)redhat.com> changed the Status of [bug 1011397|https://bugzilla.redhat.com/show_bug.cgi?id=1011397] from NEW to MODIFIED > Derived flag incorrect for extended derived artifacts > ----------------------------------------------------- > > Key: SRAMPUI-110 > URL: https://issues.jboss.org/browse/SRAMPUI-110 > Project: S-RAMP UI > Issue Type: Bug > Components: View > Affects Versions: 0.3.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > > For extended derived artifacts (e.g. SY artifacts such as SwitchYardComponentService) the derived UI flag is not being properly set. So even though these artifacts come back via a search for Derived artifacts, the data in the UI (e.g. the Derived column in the artifact list) is inaccurate. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMPUI-110) Derived flag incorrect for extended derived artifacts

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMPUI-110?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on SRAMPUI-110: ------------------------------------------------- Eric Wittmann <eric.wittmann(a)redhat.com> made a comment on [bug 1011397|https://bugzilla.redhat.com/show_bug.cgi?id=1011397] I have merged the community fix onto the s-ramp-ui product branch (0.3.0.Final-prod-ip6.0). Additionally, I am attaching a standalone patch file, in case that is desired (more targeted fix for ER3 vs. doing a full rebuild). NOTE: you should *either* pull latest changes from the s-ramp-ui git repo (product branch) *OR* use the attached patch. They are the same - I am simply providing options to the prod team. :) > Derived flag incorrect for extended derived artifacts > ----------------------------------------------------- > > Key: SRAMPUI-110 > URL: https://issues.jboss.org/browse/SRAMPUI-110 > Project: S-RAMP UI > Issue Type: Bug > Components: View > Affects Versions: 0.3.0 > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 > > > For extended derived artifacts (e.g. SY artifacts such as SwitchYardComponentService) the derived UI flag is not being properly set. So even though these artifacts come back via a search for Derived artifacts, the data in the UI (e.g. the Derived column in the artifact list) is inaccurate. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-271) Drools 6.0.0.CR2 shows up a dependency on aether that is not packaged in the swyd drools module

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-271?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-271: ----------------------------------------------- Jiri Pechanec <jpechane(a)redhat.com> changed the Status of [bug 1006709|https://bugzilla.redhat.com/show_bug.cgi?id=1006709] from ON_QA to VERIFIED > Drools 6.0.0.CR2 shows up a dependency on aether that is not packaged in the swyd drools module > ----------------------------------------------------------------------------------------------- > > Key: RTGOV-271 > URL: https://issues.jboss.org/browse/RTGOV-271 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-271) Drools 6.0.0.CR2 shows up a dependency on aether that is not packaged in the swyd drools module

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-271?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-271: ----------------------------------------------- Jiri Pechanec <jpechane(a)redhat.com> made a comment on [bug 1006709|https://bugzilla.redhat.com/show_bug.cgi?id=1006709] Verified in ER3 > Drools 6.0.0.CR2 shows up a dependency on aether that is not packaged in the swyd drools module > ----------------------------------------------------------------------------------------------- > > Key: RTGOV-271 > URL: https://issues.jboss.org/browse/RTGOV-271 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.M1 > > -- 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

10 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 September 2013