You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Emond Papegaaij (JIRA)" <ji...@apache.org> on 2013/02/11 09:15:12 UTC

[jira] [Resolved] (WICKET-4945) Wicket-atmosphere filters should be functions on AtmosphereResource

     [ https://issues.apache.org/jira/browse/WICKET-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emond Papegaaij resolved WICKET-4945.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 6.6.0

Functions was not going to work, because the payload and resource were needed, so I created a tuple containing both. You how have access to the the payload and the resource. BTW, wicket-atmosphere has always had a dependency on guava, not just for Predicate, but also for other classes.
                
> Wicket-atmosphere filters should be functions on AtmosphereResource
> -------------------------------------------------------------------
>
>                 Key: WICKET-4945
>                 URL: https://issues.apache.org/jira/browse/WICKET-4945
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-atmosphere
>    Affects Versions: 6.4.0
>            Reporter: Emond Papegaaij
>            Assignee: Emond Papegaaij
>             Fix For: 6.6.0
>
>
> With a function on AtmosphereResource, rather than a predicate, it is possible to filter on attributes in the AtmosphereRequest. This would allow you to create filters that differentiate on the receiver, without relying on the heavy-weight contextAwareFilter().

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira