[
http://issues.apache.org/jira/browse/TAPESTRY-708?page=comments#action_12356275
]
Howard M. Lewis Ship commented on TAPESTRY-708:
-----------------------------------------------
Finally found a case that demonstrates your bug.
public abstract class ForValue extends BasePage
{
public Object[] getListValues()
{
return new Object[]
{ new Foo("zero"), new Foo("one"), new Bar("two"), new Foo("three") };
}
public abstract Foo getCurrent();
}
This seems to reproduce your bug; OGNL doesn't know how to convert from Bar to
Foo and seems to be substituting null.
I need to check with Drew Davidson about what OGNL does when it can't do a
conversion.
> 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]
