Looking good, I just added metadata about javascript libraries (versions
etc)...
Jonathan Locke wrote:
well, i have thought about this for about 90 seconds, but we need to start
somewhere:
http://cwiki.apache.org/confluence/display/WICKET/Wicket+Component+JAR+Metadata
if people could pitch in and add ideas to the list, we can pare it down
later
brian.diekelman wrote:
Jonathan Locke wrote:
- (only signed) jars could be automatically picked up by some naming
pattern from maven repos and deployed as live demos
Once a signed jar is identified, what about something like OSGi to deploy
it?
- metadata would define an application name
- load the component(s) bundle into the OSGi framework, have a listener
for new bundle registrations
(http://felix.apache.org/site/apache-felix-tutorial-example-1.html)
- deploy the application to http://sitename/appName/ (have a dispatcher
servlet filter that reads the app name, trims it, and forwards to the
appropriation WebApplication within a bundle)
- when a new version of the module is released just de-activate the old
bundle and activate the new one (versions based on maven artifact/group
ids)
I have only been playing with OSGi for jar deployments in a very narrow
scope, but it seems like a good option. It should allow you to avoid
restarting anything for app deployments.
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
