Bug 1001567

Summary:	Configure JPA persistence for data models
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Pedro Zapata <pzapataf>
Component:	Data Modeler	Assignee:	Walter Medvedeo <wmedvede>
Status:	CLOSED EOL	QA Contact:	Jiri Locker <jlocker>
Severity:	low	Docs Contact:	Dawn Eisner <deisner>
Priority:	low
Version:	6.0.3	CC:	atangrin, jlocker, kverlaen, lpetrovi, mbaluch
Target Milestone:	ER4
Target Release:	6.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: See comments. Reason: Result (if any):	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 19:36:20 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Pedro Zapata 2013-08-27 10:07:03 UTC

Improve data modeler to provide at least a basic configuration for JPA persistant entities, and make/test all modifications to engines to make sure they are supported for non-global classes (not in the global classloader)

This should already be possible, using pluggable variable persistence, and we have an implementation for JPA entities already. That means that the engine will not save the entity as part of the process instance state but save / load it from separate entity tables. We might >have to look at extending the configuration options (to persist using a different data source for example).

This feature is not in 6.0.

Comment 1 Pedro Zapata 2013-09-27 16:03:44 UTC

This is feature for 6.1.

Comment 2 Vikram Goyal 2015-04-05 05:42:57 UTC

Setting requires_doc_text to - as this is a new feature in 6.1, not something that requires documenting as a known issue.

Comment 4 Jiri Locker 2015-10-26 11:54:44 UTC

Yes, the feature is there.