You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "phillip rhodes (JIRA)" <ta...@jakarta.apache.org> on 2006/02/02 15:36:03 UTC

[jira] Created: (TAPESTRY-853) Palette silently fails when bound to wrong collection type

Palette silently fails when bound to wrong collection type
----------------------------------------------------------

         Key: TAPESTRY-853
         URL: http://issues.apache.org/jira/browse/TAPESTRY-853
     Project: Tapestry
        Type: Bug
  Components: Framework  
 Environment: OSX
    Reporter: phillip rhodes


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.
-
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


[jira] Resolved: (TAPESTRY-853) Palette silently fails when bound to wrong collection type

Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
     [ 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


[jira] Updated: (TAPESTRY-853) Palette silently fails when bound to wrong collection type

Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-853?page=all ]

Jesse Kuhnert updated TAPESTRY-853:
-----------------------------------

    Fix Version/s: 4.1.2

> Palette silently fails when bound to wrong collection type
> ----------------------------------------------------------
>
>                 Key: TAPESTRY-853
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-853
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Framework
>         Environment: OSX
>            Reporter: phillip rhodes
>             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.
-
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org