[WICKET-689] Please make it easier to use a custom RequestCycle

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.6
• Fix Version/s: 1.3.0-beta2
• Component/s: wicket
• Environment: Java 5, Mac OS X 10.4.
• Assignee: Eelco Hillenius
• Reporter: Willis Blackburn
• Created: 24/Jun/07 16:01
• Updated: 24/Jun/07 23:55
• Resolved: 24/Jun/07 23:55

Description

It's trival to introduce a new Session class. Just override newSession in Application:

public Session newSession()

{ return new MySession(this); }

But introducing a new RequestCycle is a pain. I have to override Session.getRequestCycleFactory or Application.getDefaultRequestCycleFactory, providing a new factory that returns the particular RequestCycle that I want.

Strangely, there is a Session.newRequestCycle, but it's final. (Why?)

Suggestion: Please make Session/RequestCycle work like Application/Session. Let me just override newRequestCycle in Session and instantiate my RequestCycle. Maybe Application should implement ISessionFactory, and Session should implement IRequestCycleFactory. (Why does WebApplication implement ISessionFactory but not Application?)