Hi all, I've been investigating the possibilities of integrating Wicket and OSGi with favourable results. However, one major hurdle, which I think a couple of others have also pointed out here, is that there is as yet no solution providing "true" dependency injection for Wicket.
I've looked at the wicket-spring examples, and to me this seems to be using the Service Locator pattern rather than Dependency Injection. That is fine as a solution, but consider the following example: I want to be able to register my Wicket pages as services (concept should be similar regardless of IoC container) and have other services/components that are (optionally!) able to "inject" additional components into these pages. With my basic knowledge of Wicket, this example would seem impossible as there must be a "placeholder" in the page's HTML that will correspond to each of the components in the page's component tree. So ultimately it seems the page component count cannot be altered at runtime. Is there something I am missing here? I'm hoping there is some way to be able to alter the component count at runtime, or perhaps even specify "optional" components in the page HTML that may or may not be present in the component tree (still not real dependency injection, but a compromise I'd be willing to make). TIA. regards, ben -- http://blogs.modularity.net.au/thenextbigthing _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
