tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1980) Support for dismissing a single alert
Date Mon, 22 Aug 2016 06:48:23 GMT

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

Jochen Kemnade closed TAP5-1980.
    Resolution: Incomplete

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.4.1 or newer), feel free
to provide the necessary information and reopen.

> Support for dismissing a single alert
> -------------------------------------
>                 Key: TAP5-1980
>                 URL: https://issues.apache.org/jira/browse/TAP5-1980
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3.4
>            Reporter: Matías Blasi
>            Priority: Minor
>              Labels: bulk-close-candidate
> It would be usefull to dismiss a single alert.
> Up to know there is no event triggered to the server if a single alert is dismissed.
I have extended the AlertStorage, so I need to know when a single alert is dismissed in order
to reflect that into my storage.

This message was sent by Atlassian JIRA

View raw message