Jochen Kemnade created TAP5-2154:
------------------------------------
Summary: 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
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
