tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-2154) Environment keys with empty associated stacks should not be listed as available
Date Mon, 04 Nov 2013 22:43:17 GMT

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

Howard M. Lewis Ship closed TAP5-2154.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.4
         Assignee: Howard M. Lewis Ship

> Environment keys with empty associated stacks should not be listed as available
> -------------------------------------------------------------------------------
>
>                 Key: TAP5-2154
>                 URL: https://issues.apache.org/jira/browse/TAP5-2154
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Jochen Kemnade
>            Assignee: Howard M. Lewis Ship
>              Labels: error-feedback, patch, test
>             Fix For: 5.4
>
>         Attachments: 0001-don-t-list-environment-keys-with-empty-stacks.patch
>
>
> I just got the confusing error message:
> No object of type org.apache.tapestry5.services.Heartbeat is available from the Environment.
> Available values:
>  * org.apache.tapestry5.services.Heartbeat
> ..
> That happened because Heartbeat had been pushed and popped during the render cycle. The
problem is, that Heartbeat is still a key in the map of available objects, but the list/stack
of associated objects is empty.
> The patch removes entries removes those keys from the AvailableValues values list.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message