Thanks Olger, that gives me some ideas. I wonder if a maven could somehow 
be coerced to do the dependency/downloading part, perhaps with some new 
plugin.

On Mon, 20 Jul 2009 13:39:10 +0200, Olger Warnier wrote:

> Hi Sam,
> 
> How we do it with that service:
> 
> We have a file listener class  that checks if OSGI based jar files are
> put in a directory.
> If so, these are automatically deployed to the OSGI runtime by the
> BundleDeployer class.
> We miss a download / version updates part, but you could add that by
> downloading to the directory specfified by the FileListener.
> 
> There is no need to restart, OSGI updates the whole automatically (we
> use embedded felix for this).
> Something to keep in mind, be careful with the OSGI versioning in this
> as that puts versions next to eachother.
> 
> This is used to provide custom, for our project - wicket based, user
> interface functionality.
> 
> Kind Regards,
> 
> Olger
> 
> 
> On 20 jul 2009, at 12:51, Sam Stainsby wrote:
> 
>> OK, so I am an sys admin running some sort of OSGI-based application
>> and
>> now I want to add your questionnaire service and any other modules that
>> it depends on. I also want to occasionally check for version updates. I
>> want these updates and dependencies to be downloaded and put in the
>> correct place for me so that when I restart the application, they are
>> loaded. How do I do that? If it were Zope, I would add one line to a
>> 'buildout.cfg' file and run the 'buildout' script, and restart Zope.
>>
>> On Mon, 20 Jul 2009 10:33:45 +0200, Olger Warnier wrote:
>>
>>> In our project we use OSGI to get a plugin structure. Interfaces
>>> defined
>>> in the 'core' layer are implemented in OSGI modules. For a simple
>>> example see: http://www.joiningtracks.org/svn/his/trunk/
>>> questionnaire/
>>>  (SVN code repo)
>>> It's a questionnaire service that uses OSGI to load the question forms
>>> (based on wicket)
>>>
>>> Our whole platform is constructed like that, the questionnaire service
>>> is the most simple one and easily adapted for your own use.
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to