[
https://issues.apache.org/jira/browse/TAP5-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAP5-669:
--------------------------------------
Description:
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
was:
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 inconsistence state.
>From a quick search i could find the following:
- ApplicationStateAdapter
- ApplicationStateContribution
- ApplicationStateCreator
- ApplicationStateManager
- ApplicationStatePersistenceStrategy
- ApplicationStatePersistenceStrategySource
- ApplicationStateWorker
Those are all public APIs and changing them is difficult, especially when we
bring service contributions into play. I think we'll need some IoC changes
before we can support renaming services in this way ... alternately, we need a
complex way of keeping the existing classes and services, and merging them into
the new ones.
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
