public class TimeTrackrApplication extends Application
{
public TimeTrackrApplication()
{
Application.set(this);
}
}
At least i don't hope that spring first makes the refs then the bean itself..
johan
On 4/5/06, Mark Derricutt <[EMAIL PROTECTED]> wrote:
On 4/5/06, Johan Compagner <[EMAIL PROTECTED] > wrote:
So you just should implement youre own sublcass of AbstractPageAuthorizationStrategy for this.
Or see why the application isn't there yet.
The application's not there simply because its not there - my Application instance is configured IN the spring configuration file, example:
<bean id="wicketApplication" class="com.theoryinpractice.timetrackr.TimeTrackrApplication">
<property name="timeTrackrAuthorizationStrategy" ref="authorizationStrategy"/>
</bean>
<bean id="authorizationStrategy" class="com.theoryinpractice.timetrackr.TimeTrackrAuthorizationStrategy">
<property name="userManager" ref="userManager"/>
</bean>So the wiring of spring should be done in the initalize phase of the application/wicket servlet.
The wicket servlet is using the SpringWebApplicationFactory application factory which looks up the wicketApplication bean.
I'll just rework my code to use AbstractPageAuthorizationStrategy as you say..
