Very interesting article!
Did you consider moving the boilerplate code (which is most of the
code) outside to a separate bundle? A wicket bundle could easily
detect the installation of "wicket app" bundles, check a special resource
in the bundle and handle the web registration and other chores. In
this model, you only have to code the HelloWorld class in the
application bundle.
We call this the "extender" model and is used heavily in R4; for example
declarative services use this model. Features in R4 like
findEntryPaths, getResources, and loadClass are specifically added to
support this model.
The advantage is that it significantly reduces the coding for the
application as well as making it more robust and easier to integrate with
other apps (less knowledge in the app bundle).
Kind regards,
Peter Kriens
BTJA> A bit off-topic for most except those interested in the Wicket web
BTJA> application development framework... Niclas Hedhman pulled together a
BTJA> development pattern/model for developing Wicket-based web applications
BTJA> in OSGi (Oscar/Felix) using the standard OSGi HttpService and
BTJA> HttpContext interfaces/implementations.
BTJA> I drove it around the block and kicked the tires, then spent a day or so
BTJA> documented the pattern. If interested, you can read about it at
BTJA> http://wiki.ops4j.org/dokuwiki/doku.php?id=pax:wicket.
BTJA> -timothy
--
Peter Kriens Mob +33633746480
9C, Avenue St. Drézéry Tel +33467542167
34160 Beaulieu, France Tel +15123514821
Tel +33870447986
AOL,Yahoo, Skype pkriens ICQ 255570717
