[MGNLWORKFLOW-194] JCR storage of jbpm and drools related objects is confusing Created: 21/Jan/14  Updated: 18/Feb/14  Resolved: 24/Jan/14

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: 5.2
Fix Version/s: 5.3

Type: Improvement Priority: Neutral
Reporter: Espen Jervidalo Assignee: Espen Jervidalo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   
  • the nodetype definition is under workflow module, which should be defined in workflow-jbpm where it actually is used.
  • workflowInstance should be renamed to processInstance
  • kSession renamed to session
  • consider simplifying the structure currently used: putting processes and workItems into random subnodes


 Comments   
Comment by Espen Jervidalo [ 24/Jan/14 ]

fixed on jcr-peristence-integration branch

Generated at Mon Feb 12 10:07:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.