You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> on 2007/03/18 21:48:09 UTC
[jira] Resolved: (TAPESTRY-853) Palette silently fails when bound
to wrong collection type
[ https://issues.apache.org/jira/browse/TAPESTRY-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert resolved TAPESTRY-853.
------------------------------------
Resolution: Fixed
Assignee: Jesse Kuhnert
I agree....That is hugely annoying and has stung me several times as well. Just fixed and deployed it in OGNL 2.7-SNAPSHOT.
> Palette silently fails when bound to wrong collection type
> ----------------------------------------------------------
>
> Key: TAPESTRY-853
> URL: https://issues.apache.org/jira/browse/TAPESTRY-853
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Environment: OSX
> Reporter: phillip rhodes
> Assigned To: Jesse Kuhnert
> Fix For: 4.1.2
>
>
> After more time than I would like to publicly admin, I finally figured out why my palette was not working as expected. I was binding my component to a java.util.Set and while it would appear to work, the set that the palette was bound to never get updated.
> I think this may be the fault of ognl, but wanted to share the pain that I experienced.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org