[MAGNOLIA-1392] ClassCastException in openwfe when a filter sets a request parameter with value "true" Created: 20/Feb/07 Updated: 23/Jan/13 Resolved: 15/Nov/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | workflow |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 3.5 RC1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Fabrizio Giustina | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Not sure if this should be handled in openwfe or if it should be handled in magnolia. ERROR info.magnolia.module.workflow.WorkflowUtil WorkflowUtil.java(proceed:172) 20.02.2007 14:20:51 Error while accessing the workflow engine |
| Comments |
| Comment by Fabrizio Giustina [ 20/Feb/07 ] |
|
quick fix in openwfe: openwfe.org.engine.workitem.BooleanAttribute public boolean booleanValue() return ((Boolean) this.value).booleanValue(); still checking if it could be a problem in how magnolia sets workitem attributes |
| Comment by John Mettraux [ 20/Feb/07 ] |
|
checked in into OpenWFE svn. Thanks, John |
| Comment by Fabrizio Giustina [ 20/Feb/07 ] |
|
thanks John! I had a deeper look at BooleanAttribute and it seems that the only way you can set an invalid (non boolean) internal value is by using the setter method inherited by AtomicAttribute. This is why you ends up with a String value in magnolia (it doesn't use the constructor but the getter). public void setValue(Object value) else { this.value = "true".equalsIgnoreCase(value.toString()); }} |
| Comment by John Mettraux [ 20/Feb/07 ] |
|
Hi Fabrizio, I did that : which should be roughly equal to your suggestion. Thanks to you. |
| Comment by Django [ 07/Mar/07 ] |
|
I'm having the same exception on one particular machine. When I extract the Magnolia bundle (3, 3rc3, 3.0.1) and try to activate an arbitrary page I got a The same installation works fine on other machines. I tried to replace the openwfe engine jar by one build from the head but then I get an continuing dump of So is there a hint on how to work around the problem. What 'true' is causing the problem? Is it something machine specific? Something I did wrong? Please help. Our company wants to use Magnolia and I need to get this environment up and running. It is blocking me for a while now. Cheers |
| Comment by John Mettraux [ 07/Mar/07 ] |
|
Hi Django, Hi Fabrizio, I will tighten the IntegerAttribute and all the other attributes as we did for the BooleanAttribute. Too bad I haven't the time now to fix the cause common to all attributes. Stay tuned, John |
| Comment by John Mettraux [ 08/Mar/07 ] |
|
OK, code tightened svn 3630 SNAPSHOT jars uploaded. direct link : http://maven.openwfe.org/snapshots/org/openwfe/openwfe-engine/1.7.3-SNAPSHOT/openwfe-engine-1.7.3-20070308.091235-10.jar Best regards, John |
| Comment by Django [ 08/Mar/07 ] |
|
Hi John, Unfortunately this does not work for me. After replacing the jars magnolia doesn't start up: And after that there is an continuing error: Is there any hint on what integer is causing the underlying problem I have on this particular machine? |
| Comment by Django [ 09/Mar/07 ] |
|
Hi John, I'm not sure my comments are really related directly to this issue. My actual problem is that magnolia activation is not working on SuSE 10.x. (I accidentally used SuSE because I had a boot CD around). I now use Ubuntu and activation works fine. Cheers Django |
| Comment by Fabrizio Giustina [ 22/Apr/07 ] |
|
Setting fix version to 3.1 to remember that we neet to upgrade to openwfe 1.7.3 in order to have this fixed, hoping that a new openwfe release is out before we are ready to release magnolia 3.1 |
| Comment by Magnolia International [ 25/Oct/07 ] |
|
Actually this is really the same as in |
| 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. |