[
http://jira.jboss.com/jira/browse/JBPM-228?page=all ]
Ronald van Kuijk closed JBPM-228.
---------------------------------
Fix Version/s: jBPM jPDL 3.2
jBPM 3.1
Resolution: Done
This is already possible in 3.1 and 3.2. The thing is it is not persisted in the DB, but
the complete PD is persisted in the DB as XML.
Retrieving these custom attributes is being worked on for 3.3 (maybe 3.2.2). I only want
to change the '##any' to '##other'
Allow <variable> to have "any" content for user
metadata
--------------------------------------------------------
Key: JBPM-228
URL:
http://jira.jboss.com/jira/browse/JBPM-228
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM 3.0 beta 2
Environment: All
Reporter: Jim Rigsbee
Assigned To: Tom Baeyens
Priority: Minor
Fix For: jBPM jPDL 3.2, jBPM 3.1
Original Estimate: 1 day
Remaining Estimate: 1 day
Please allow the <variable> element allow "any" schema content just like
the "handlers". This would allow the user to store custom metadata for their
purposes. This data should be persisted to the database and the API should allow its
retrieval just like <action>, <assignment>, and
<decision>/<handler>, etc.
We intend on using this to assist with driving the user interface from the work flow
engine. One type of meta data we need is the "java type" for the variable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira