osgi has some problems when it comes to serialization - a feature wicket uses extensively. so beware. at least see pax-wicket for possible solutions.
-igor On Fri, Nov 14, 2008 at 10:45 AM, Ernesto Reinaldo Barreiro <[EMAIL PROTECTED]> wrote: > I would use OSGi. Each application a different bundle (jars) and a main > bundle (jar) that defines the services for plugin in new modules... For > instance a service to register your left menu entries... I have done > something "similar" for an application I built sometime ago. With OSGi you > could make it completely dynamic with modules added/removed at runtime > without having to stop you server. So, essentially it is what Igor said but > OSGi would make it easier to manage the dynamic part. > Best, > > Ernesto > > On Fri, Nov 14, 2008 at 1:45 PM, cresc <[EMAIL PROTECTED]> wrote: > >> >> hi, >> >> Just eager to know if any of you had tried the following application in >> wicket. >> http://www.nabble.com/file/p20499804/appl.jpg >> >> Core.war contains the login, usermanagement, layout etc. >> m1, m2, m3 etc are smaller modules independent of each other. >> From the core layout contained in core.war I should be able to launch m1, >> m2 >> m3 etc.. If a new module m4.war is deployed, then I would like to have m4 >> menu appear on the layout (basically menus constructed from values in >> database table). >> >> Please provide some starters on how to build an application like this. >> >> Thanks, >> cresc >> >> >> -- >> View this message in context: >> http://www.nabble.com/dynamic-application-from-diff-wars-tp20499804p20499804.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
