tapestry-commits 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-669) All services related to the old ApplicationState concept should be renamed to use the new SessionState naming
Date Tue, 13 May 2014 13:23:24 GMT

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

Jochen Kemnade closed TAP5-669.
-------------------------------

    Resolution: Not a Problem

Another year has passed since the last comment. Therefore, we assume this issue has either
been resolved in the meantime or it is no longer relevant to you.
If recent versions of Tapestry (i.e. 5.4 betas and 5.3.7) are still affected, please reopen
the issue and adjust the "Affected Version/s" property.

> All services related to the old ApplicationState concept should be renamed to use the
new SessionState naming
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-669
>                 URL: https://issues.apache.org/jira/browse/TAP5-669
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.4
>            Reporter: Hugo Palma
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> 5.1.0.4 introduced the renaming of ApplicationState to SessionState. But there are some
services that use the same naming and that were not renamed leaving the concept and the service
names in an inconsistent state.
> From a quick search i could find the following:
> - ApplicationStateAdapter
> - ApplicationStateContribution
> - ApplicationStateCreator
> - ApplicationStateManager
> - ApplicationStatePersistenceStrategy
> - ApplicationStatePersistenceStrategySource
> - ApplicationStateWorker



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message