[
https://issues.apache.org/jira/browse/WICKET-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenny MacLeod updated WICKET-2572:
----------------------------------
Description:
The current SpringWebApplicationFactory is only capable of using the root
WebApplicationContext to fetch the WebApplication object. In cases where
there's only one Wicket application per webapp, this is fine, but sometimes you
want more than one, and you want them in seperate contexts.
This is analogous to using multiple Spring DispatcherServlets in a single
webapp - each servlet gets its own context, and optionally share the same root
WebApplicationContext as their parent.
I propose an enhancement to SpringWebApplicationFactory allowing it to create a
new application context, and to retrieve the WebApplication object from there.
The WebApplication object itself can then have itself autowired with the
application context from which it was fetched. This application context can
then be fed into SpringComponentInjector's constructor, so there's no need for
SpringComponentInjector to know how to look up this newly-created context.
Patch to follow.
was:
The current SpringWebApplicationFactory is only capable of using the root
WebApplicationContext to fetch the WebApplication object. In cases where
there's only one Wicket application per webapp, this is fine, but sometimes you
want more than one, and you want them in seperate contexts.
This is analogous to using multiple Spring DispatcherServlets in a single
webapp - each servlet gets its own context, and optionally share the same root
WebApplicationContext as their parent.
I propose an enhancement to SpringWebApplicationFactory allowing it to create a
new application context, and to retrieve the WebApplication object from there.
Patch to follow.
> Add capability for SpringWebApplicationFactory to create its own application
> context
> ------------------------------------------------------------------------------------
>
> Key: WICKET-2572
> URL: https://issues.apache.org/jira/browse/WICKET-2572
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-spring
> Affects Versions: 1.4.3, 1.5-M1
> Reporter: Kenny MacLeod
> Attachments: SpringWebApplicationFactory.java,
> SpringWebApplicationFactory.patch
>
>
> The current SpringWebApplicationFactory is only capable of using the root
> WebApplicationContext to fetch the WebApplication object. In cases where
> there's only one Wicket application per webapp, this is fine, but sometimes
> you want more than one, and you want them in seperate contexts.
> This is analogous to using multiple Spring DispatcherServlets in a single
> webapp - each servlet gets its own context, and optionally share the same
> root WebApplicationContext as their parent.
> I propose an enhancement to SpringWebApplicationFactory allowing it to create
> a new application context, and to retrieve the WebApplication object from
> there.
> The WebApplication object itself can then have itself autowired with the
> application context from which it was fetched. This application context can
> then be fed into SpringComponentInjector's constructor, so there's no need
> for SpringComponentInjector to know how to look up this newly-created context.
> Patch to follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
