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

Posted to commits@tapestry.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/08/01 02:47:10 UTC

[jira] [Commented] (TAP5-1421) Create a standard way to track messages to be presented to the user

    [ https://issues.apache.org/jira/browse/TAP5-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073408#comment-13073408 ] 

Hudson commented on TAP5-1421:
------------------------------

Integrated in tapestry-trunk-freestyle #444 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/444/])
    TAP5-1421: Handle the case where all alerts are dismissed but no AlertStorage object yet exists

hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1152666
Files : 
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/Alerts.java


> Create a standard way to track messages to be presented to the user
> -------------------------------------------------------------------
>
>                 Key: TAP5-1421
>                 URL: https://issues.apache.org/jira/browse/TAP5-1421
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3
>
>
> For a client, I've created a GlobalAlerts SSO, along with a GlobalAlertsManager service, an Alerts component, even JavaScript client-side support for adding and clearing alerts.  I'd like to generalize this code a bit ... currently Alerts messages are limited to strings (fully renderable would be better).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira