>And maybe asking the Wicket people what the best option would be would >be worth it? > >Asking how to run Wicket in an OSGi environment might raise their >interest, and the "Wicket takes over the request processing cycle >after Sling has selected content" integration that Dominik suggests >might be of general interest to them.
btw - wicket 1.4rc2 ships already with OSGI bundle metadata included in the distribution jar. http://repo2.maven.org/maven2/org/apache/wicket/wicket/1.4-rc2/wicket-1.4-rc2.jar and there exists a OPS4J - Pax Wicket project with advanced osgi support inside wicket itself, with support to dynamically load and unload model parts at runtime without reloading the wicket application itself. http://www.ops4j.org/projects/pax/wicket/ but i think for the first steps we do not need this features, but will integrate wicket applications with the sling request processing and are happy to deploy the whole wicket application itself as osgi bundle into sling. as soon as we've a first proof of concept integration running, we will post it here and in the wicket mailing list as well, to see what the others are thinking. stefan
