[
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