[
https://issues.apache.org/jira/browse/WICKET-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Meier updated WICKET-5079:
-------------------------------
Description:
SpringWebApplicationFactory allows two places to defined a WebApplication:
- in the global root application context loaded by Spring's
ContextLoaderListener
- in a filter-specific additional web applcation context.
SpringComponentInjector is not aware of this additional context but just uses
the global one. This imposes the following restrictions:
- the filter-specific context cannot define any beans to be used by
SpringComponentInjector
- SpringComponentInjector cannot work without a global root application,
i.e.ContextLoaderListener is required.
Starting with Wicket 6.7.0 the filter-specific context is made accessible to
SpringComponentInjector. If no application context is given explicitly to
SpringComponentInjector's constructor, by default the injector uses the
application context used to create the WebApplication.
Benefits:
- no need to define ContextLoaderListener in web.xml (i.e. less xml)
- use application-specific beans defined in the filter-specific application
context
was:
Handling of Spring application contexts could be improved:
- to allow working without a root application context
- to allow SpringComponentInjector to inject beans from the
filter/application-specific web application context
Summary: Allow WebApplication-specific Spring configuration (was:
Improve Spring application context handling)
> Allow WebApplication-specific Spring configuration
> --------------------------------------------------
>
> Key: WICKET-5079
> URL: https://issues.apache.org/jira/browse/WICKET-5079
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-spring
> Affects Versions: 6.6.0
> Reporter: Sven Meier
> Assignee: Sven Meier
> Priority: Minor
> Fix For: 6.7.0
>
>
> SpringWebApplicationFactory allows two places to defined a WebApplication:
> - in the global root application context loaded by Spring's
> ContextLoaderListener
> - in a filter-specific additional web applcation context.
> SpringComponentInjector is not aware of this additional context but just uses
> the global one. This imposes the following restrictions:
> - the filter-specific context cannot define any beans to be used by
> SpringComponentInjector
> - SpringComponentInjector cannot work without a global root application,
> i.e.ContextLoaderListener is required.
> Starting with Wicket 6.7.0 the filter-specific context is made accessible to
> SpringComponentInjector. If no application context is given explicitly to
> SpringComponentInjector's constructor, by default the injector uses the
> application context used to create the WebApplication.
> Benefits:
> - no need to define ContextLoaderListener in web.xml (i.e. less xml)
> - use application-specific beans defined in the filter-specific application
> context
--
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
