You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2013/08/13 12:02:49 UTC
[jira] [Updated] (TAP5-2154) Environment keys with empty associated
stacks should not be listed as available
[ https://issues.apache.org/jira/browse/TAP5-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade updated TAP5-2154:
---------------------------------
Attachment: 0001-don-t-list-environment-keys-with-empty-stacks.patch
> 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
> Labels: error-feedback, patch, test
> 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 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