[
https://issues.jboss.org/browse/RTGOV-374?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on RTGOV-374:
-----------------------------------
[~objectiser], here's a few thoughts.
Rather than create our own datasources, like activity-store-jpa-h2, could you require
users to include the full JNDI service name (ex:
"java:jboss/datasources/MyDataSource") within the rtgov configuration? This
would allow more control, the reuse of existing datasources, etc., in addition to
preventing the maintenance of datasource modules for every type of DB we need to support,
as well as not restricting the types possible.
Alternatively, we could also allow users to provide a hibernate.properties or
hibernate.cfg.xml, rather than JTA datasources. That could certainly be in addition to
the above.
If that sort of capability is desirable, we'd probably need to stick with
programmatically creating the EntityManager, ala JPAActivityStore, rather than manually
calling out the datasource in the persistence.xml and relying on EE's
container-managed @PersistenceContext (ala JPASituationStore).
Support for JPA ActivityStore
-----------------------------
Key: RTGOV-374
URL:
https://issues.jboss.org/browse/RTGOV-374
Project: RTGov (Run Time Governance)
Issue Type: Sub-task
Reporter: Gary Brown
Assignee: Brett Meyer
Fix For: 2.0.0.Final
Original Estimate: 2 weeks
Remaining Estimate: 2 weeks
Need to be able to use JPAActivityStore within Karaf/OSGi environment, with different
databases (e.g. h2, mysql 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