[jira] [Updated] (TAP5-669) All services related to the old ApplicationState concept should be renamed to use the new SessionState naming

["Ulrich Stärk (JIRA)" <ji...@apache.org>]

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

Ulrich Stärk updated TAP5-669:
------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.
                
> 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 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