[MAGNOLIA-1320] workflow storage : Expressions don't need metadata. Created: 26/Jan/07  Updated: 23/Jan/13  Resolved: 23/Feb/07

Status: Closed
Project: Magnolia
Component/s: workflow
Affects Version/s: 3.0.2
Fix Version/s: 3.0.2, 3.1 M1

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1400 Update mechanism : when updating from... Closed
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)
Date of First Response:

 Comments   
Comment by Magnolia International [ 26/Jan/07 ]

commited to branches/magnolia-module-workflow-deferred-storage

Comment by Sameer Charles [ 22/Feb/07 ]

todo: needs to be tested on existing workflow repository

  • all new nodes created should not have MetaData
  • Existing nodes should be usable
Comment by Magnolia International [ 22/Feb/07 ]

Ok, after some testing:

  • only changing the nodetype definition in the workflow module has no impact on an existing repository. Nodes are still used and created with the original definition.
  • changing the nodetype definition in repositories/magnolia/repository/nodetypes/custom_nodetypes.xml has the following apparent effects:
  • workflows can still be used
  • warnings are issued by jackrabbit when accessing the nodes :
    WARN org.apache.jackrabbit.core.ItemManager ItemManager.java(getDefinition:134) 22.02.2007 19:50:22 node at /owfe/activation/1172169891924/0.0.1__participant/MetaData has invalid definitionId (-349493662)
    One warning for each expression can very quickly look pretty messy in the logs. This happens when querying the store or when proceeding workflows. Doesn't seem to have any impact.
  • existing expressions keep their metadata.
  • new expressions don't have metadata
Comment by Magnolia International [ 23/Feb/07 ]

commited to branches/magnolia-3.0 and trunk

todo : doc + create new task for 3.1 (auto update mechanism should actively remove metadata from existing nodes when updating)

Comment by Magnolia International [ 23/Feb/07 ]

No doc needed at the moment. Existing users should avoid modifying the nodetypes defs manually.
See MAGNOLIA-1400 for further improvements (auto-update)

Generated at Mon Feb 12 03:25:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.