]
Ronald van Kuijk updated JBPM-2777:
-----------------------------------
Happens to trunk also where script is refactored a lot.
Changing 3 for java breaks backwards compatibility. But I do think EL should at least
behave identical, so maybe it should also return null...
JBPM 4.3 EL cannot read null process variable -
javax.el.PropertyNotFoundException is thrown
--------------------------------------------------------------------------------------------
Key: JBPM-2777
URL:
https://jira.jboss.org/jira/browse/JBPM-2777
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Environment: tested on windows vista and ubuntu 9.10
Reporter: Jakub Sobolewski
Attachments: test.zip, test_jbpmTestCase.zip
EL cannot read process variable set to null value. Variable is seen from Java code. When
I try to access it in JPDL by EL expression javax.el.PropertyNotFoundException is thrown.
Simple test case (maven eclipse project) in attachment - it contains 1 process definition
and 2 tests which show the issue.
Forum thread:
http://community.jboss.org/thread/147447?start=0&tstart=0
reading variable cases:
1: var exists and has a non-null value - Java returns value, EL returns value
2: var exists and has value of 'null' - Java returns null, EL fails
3: var does not exists - Java returns null, EL fails
In cases 1,2 EL and Java should behave the same way... I think that in case 3 too, but
which behavior is right ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: