Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <44181B28.6070708@apache.org>
Date: Wed, 15 Mar 2006 14:48:24 +0100
From: Reinhard Poetz <reinhard@apache.org>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [RT] OSGi based blocks
References: <44173F14.4030701@nada.kth.se> <4417F811.7000606@apache.org>
In-Reply-To: <4417F811.7000606@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Sylvain Wallez wrote:

> A *very* important point IMO for the acceptance of all this by
> developers is to be able do deploy a directory. This to have fast
> roundtrips, without having to go through the compile/package/deploy cycle.

Felix has recently added the possiblity to add bundles which are unpacked. I 
guess that Equinox already supports this. In order to get a redeployment we have 
several options:

  a) use an OSGi console and enter some commands
  b) we can have some kind of watchdog that does the start/stop of bundles
  c) maybe we can even plugin the ReloadingClassloader

I think option a) is not what you/we expect. Option b) should already feel like 
our ReloadingClassloader. Option c) could be more difficult as we would need 
some way to add the ReloadingClassloader into the OSGi classpath hierarchy.

-- 
Reinhard P�tz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de