[
https://issues.apache.org/jira/browse/WICKET-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov updated WICKET-6618:
------------------------------------
Fix Version/s: (was: 9.0.0-M1)
9.0.0-M2
> Stateless pages and access to unconfigured components
> -----------------------------------------------------
>
> Key: WICKET-6618
> URL: https://issues.apache.org/jira/browse/WICKET-6618
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 9.0.0-M1
> Reporter: Sven Meier
> Assignee: Sven Meier
> Priority: Minor
> Fix For: 9.0.0-M2
>
>
> Requests to components/behaviors on stateless components should be
> standardized.
> Currently PageAndComponentProvider:
> * provides a component *unconfigured*, if it is already inside the component
> hierarchy
> * configures the page for render otherwise
> * provides a component *configured* afterwards*,* if it was added during
> #onInitialize() or #onConfigure()
> As a Wicket user I would expect access to components *configured* only.
> If we decide to configure stateless pages *everytime* a component inside it
> is accessed, we have to decide wether
> * excluding feedbacks from configuration is enough (as is done currently)
> * configuration of all components should be reset, so that configuration is
> repeated on the following render (e.g. ListViews picking up their items,
> configuration is updated according to a new model state)
> * or whether the whole page should be detached too (this would refresh
> loadable models too)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
