[
http://issues.apache.org/jira/browse/TAPESTRY-708?page=comments#action_12356277
]
Howard M. Lewis Ship commented on TAPESTRY-708:
-----------------------------------------------
We're getting to this code inside ExpressionEvaluatorImpl:
public void writeCompiled(Object target, Object expression, Object value)
{
try
{
Map context = createContext(target);
Ognl.setValue(expression, context, target, value);
}
catch (Exception ex)
{
throw new
ApplicationRuntimeException(ImplMessages.unableToWriteExpression(ImplMessages
.parsedExpression(), target, value, ex), target, null, ex);
}
}
I think this is in OGNL's court; I've traced the code around and OGNL seems to
be the one making the assignment to null.
> For component silently drop the value when unable to set
> --------------------------------------------------------
>
> Key: TAPESTRY-708
> URL: http://issues.apache.org/jira/browse/TAPESTRY-708
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0
> Reporter: Ron Piterman
> Assignee: Howard M. Lewis Ship
>
> When one defines:
> <span jwcid="@For" source="ognl:list" value="ognl:current">
> if the object in the list can not be assigned to the "current" property,
> because of unmatching types, setting will be silently fail.
> one *will* get a problem with a null value elsewhere, which is than very
> puzzling to try to solve.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
