[ https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug... ] Hauke Rabe updated JBPM-2506: ----------------------------- Component/s: Runtime Engine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-2506: ------------------------------ Summary: document how to enable variable history (was: ability to create history entry for variables) Original Estimate: 4 hours Remaining Estimate: 4 hours -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-2506: ------------------------------ Priority: Optional (was: Major) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-2506: ------------------------------ Description: When variable declarations, also the ability to trace the history can be exposed and documented. add following element to process the group activity <variable name="" [type=""] [history=""] /> type should refer to the types defined in jbpm.variable.types.xml history = {enabled, disabled} (disabled is the default) was: When variable declarations, also the ability to trace the history can be exposed and documented. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug... ] Sebastian Schneider commented on JBPM-2506: ------------------------------------------- When declaring variables already in the process definition it is possible to specify whether or not they should be taken into account for the history. So the same configuration should be possible via the API for variables which are created during run-time. btw: Why is the history disabled by default? What are the reasons against enabled by default? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug... ] Sebastian Schneider commented on JBPM-2506: ------------------------------------------- This is somehow duplicated by JBPM-2776 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug... ] Maciej Swiderski reassigned JBPM-2506: -------------------------------------- Assignee: Maciej Swiderski (was: Tom Baeyens) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug... ] Huisheng Xu commented on JBPM-2506: ----------------------------------- Hi Maciej, Glad to see that you are working on this issue. Do you have any plan for this? Do we need create a new post in the forum and talk about it? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2506?page=com.atlassian.jira.plug... ] Huisheng Xu commented on JBPM-2506: ----------------------------------- Thank you for reply. I think we could consider about Dan's quesion. http://community.jboss.org/message/541789#541789 He want to store non String type variable in the history table. I think it is a good idea. But I am not sure whether we should provide this feature in the jBPM-4.4. And maybe I could resolve JBPM-2840 today. Hope it will help to this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBPM-2506?page=com.atlassian.jira.plugin.sy... ] Maciej Swiderski commented on JBPM-2506: ---------------------------------------- Part of the work is done now: - declare variable in jpdl - mark declared variable as history enabled - create variable via API that is history enabled - retrieve variables from history via API - support for both simple text and EL on declared variables in jpdl If it comes to non string variables that is bit more complex. Mainly due to the structure of the data base where value column is only of type string (varchar). I did some tests with JavaBeans as variable and simple solution that I implemented is that such variables will be still persisted as string based on implementation of toString() method. In my opinion that is quite good solution at the moment that enables us to simply query for history process instances based on variable's values. Of course this is not a final solution but at least something to let users hove some added value from variable history. Difficult to say what was initial idea for history of variables ... any news are more than welcome. In addition, such approuch could be used as well to allow queries based on variables for execution variables as well. I mean that if some once would be interested to query based on variable value (s)he could implement toString with information that should be searchable. Soon will upload a first version of a patch for review. What do you think based on the description so far? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBPM-2506?page=com.atlassian.jira.plugin.sy... ] Maciej Swiderski updated JBPM-2506: ----------------------------------- Attachment: JBPM-2506.patch initial version for variable declaration and history support -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBPM-2506?page=com.atlassian.jira.plugin.sy... ] Maciej Swiderski commented on JBPM-2506: ---------------------------------------- Implementation is ready. Waiting for feed back before commit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBPM-2506?page=com.atlassian.jira.plugin.sy... ] Alejandro Guizar updated JBPM-2506: ----------------------------------- Attachment: jbpm-2506-20100609.diff Attaching patch for public review. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBPM-2506?page=com.atlassian.jira.plugin.sy... ] Alejandro Guizar updated JBPM-2506: ----------------------------------- Comment: was deleted (was: Attaching patch for public review.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBPM-2506?page=com.atlassian.jira.plugin.sy... ] Maciej Swiderski commented on JBPM-2506: ---------------------------------------- code checked in to trunk, revision 6396 This issue and JBPM-2840 can be closed (resolved). Remaining part is documentation - issue JBPM-2776. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBPM-2506?page=com.atlassian.jira.plugin.sy... ] Alejandro Guizar updated JBPM-2506: ----------------------------------- Assignee: Maciej Swiderski (was: Alejandro Guizar) Reapplied patch to incorporate the latest suggestions. Marking as resolved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBPM-2506?page=com.atlassian.jira.plugin.sy... ] Maciej Swiderski reopened JBPM-2506: ------------------------------------ reopening to incorporate refactoring to be consistent with executionService operations on variables - prevent of ugly NPE -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBPM-2506?page=com.atlassian.jira.plugin.sy... ] Maciej Swiderski reopened JBPM-2506: ------------------------------------ reopening the issue due to found bug that history variables are not updated when execution variable is updated -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira