[MAGNOLIA-1797] Can't proceed workflow : ClassCastException in openwfe Created: 24/Oct/07  Updated: 23/Jan/13  Resolved: 15/Nov/07

Status: Closed
Project: Magnolia
Component/s: core, workflow
Affects Version/s: 3.5 RC1
Fix Version/s: 3.5 RC1

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

Attachments: Text File magnolia-error-melinda-activation.log    
Issue Links:
duplicate
is duplicated by MAGNOLIA-1392 ClassCastException in openwfe when a ... Closed
relation
is related to MAGNOLIA-1798 don't store HierarchyManager, AccessM... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

From Amir:
If I log in as "joe" (who is an editor) and activate content I am unable to see it in the Inbox, which is good. Then I log in as "melinda" (who is a publisher) and I can see activation requests from "joe" - excellent. However, any action from melinda (proceed, cancel, reject) throws an exception (see attached)...


Indeed. This seems to be because openwfe is unable to decode some attribute of the workitem properly; apparently it'd be the user's permissions, wrapped in a LongAttribute, but with a java.lang.Integer value. Seems to be a very similar issue than with MAGNOLIA-1392



 Comments   
Comment by Magnolia International [ 25/Oct/07 ]

Actually this is really the same as in MAGNOLIA-1392. We'll branch of openwfe-1.7.2 and fix it there.
(Fabrizio's fix has been applied to the trunk, and similar fixes to the other XXXAttribute classes, but also another bunch of changes, including API changes, so we can't afford to migrate this now)

Furthermore, we'll make sure the HierarchyManagers don't end up in the WorkitemContext. They do now, since they're stored as request attributes - which are copied over to the WorkitemContext when launching a new workflow.

Comment by Magnolia International [ 02/Nov/07 ]

We branched openwfe-1.7.2 and just deployed 1.7.2.1-SNAPSHOTs, which should fix this issue.

Comment by Magnolia International [ 15/Nov/07 ]

The update to openwfe to 1.7.2.1 fixes this.

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