it is easy to create a pluggable application in wicket. all you need is a registry of component providers, whether it be something like spring [1], a custom registry like brix uses [2] or something more advanced like osgi. the choice should be based on the featureset you need. eg, if you need hot updating, classloader separation, etc, then osgi is good. if not, there are simpler ways to achieve modularity [1] [2]. the great news is that wicket lends itself easily to modularization.
[1] http://wicketinaction.com/2008/10/creating-pluggable-applications-with-wicket-and-spring/ [2] http://code.google.com/p/brix-cms/source/browse/#svn/trunk/brix-core/src/main/java/brix/registry -igor 2009/10/29 Tomáš Mihok <tomas.mi...@cnl.tuke.sk>: > Hello, > > I'm currently designing a new application. One of the requests is to make it > modular. I found out that one of the possibilities to enable loading of > modules while application is running is OSGi. Is there a tool/plugin/guide > to accomplish this or are there any other possibilities of accomplishing > same goal? > > Tom > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
