If I want to use wicket-spring, but I want to try to let Spring wire everything together, what is the best way to do so? I realize that there is the SpringWebApplicationFactory class, but that merely looks up the application in the Spring context. The WebApplication class isn't very "beany" though (and it's abstract, so I have to subclass it no matter what). It doesn't have setters for stuff like the pageSettings or applicationSettings properties. The Application (the parent of WebApplication) class defines an instance variable of type Settings which covers most of this stuff. The getters for applicationSettings and pageSettings merely return getSettings(). Of course getSettings() is private, so I can't override that unfortunately. Anyway, what I want is for the wicket classes to be more bean-oriented so that I can piece them together how I see fit, by overriding certain properties (like AuthorizationStrategy) and leaving the defaults for others. Has anyone done this before?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
