Bug 1011889 - Situation needs an explicit id that can be used to correlate the persisted object with the one distributed via notification
Summary: Situation needs an explicit id that can be used to correlate the persisted ob...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: RT Governance
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER4
: 6.0.0
Assignee: Julian Coleman
QA Contact: Jiri Pechanec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-25 10:44 UTC by Gary Brown
Modified: 2014-07-02 09:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RTGOV-279 0 Major Closed Situation requires an explicitly defined ID 2014-07-02 09:19:23 UTC

Description Gary Brown 2013-09-25 10:44:35 UTC 
Description of problem:

Currently the 'Situation' object only has an internal id used when persisting the object in a JPA db. When the Situation object is distributed via the active collection to the Situations gadget, or any other REST client accessing the active collection, this id is not available.

Therefore if at a later stage the client wishes to retrieve that situation from the db (i.e. situation history) it is not possible to refer to it by an id.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Gary Brown 2013-09-25 10:52:45 UTC 
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.
Comment 3 Gary Brown 2013-09-25 11:10:45 UTC 
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
Comment 4 JBoss JIRA Server 2013-09-25 11:16:47 UTC 
Gary Brown <gary> updated the status of jira RTGOV-279 to Resolved
Comment 8 Jiri Pechanec 2014-01-07 11:40:07 UTC 
Verified in ER8
Comment 9 JBoss JIRA Server 2014-07-02 09:19:23 UTC 
Gary Brown <gary> updated the status of jira RTGOV-279 to Closed
Note You need to log in before you can comment on or make changes to this bug.