cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Re: [2.2] Support for per sitemap classloading?
Date Sun, 05 Mar 2006 11:02:38 GMT
Daniel Fagerstrom wrote:

> What the blocks fw eventually will support depends on what you and 
> others want it to support and are prepared to implement ;)
>> Yes, that's the plan. Adding it to 
>> org.apache.cocoon.blocks.servlet.BlocksManager (module: 
>> cocoon-blocks-fw-servlet-impl) shouldn't be too difficult, especially 
>> for you ;-)
>> But as said in my other response to Carsten's mail, adding it to the 
>> OSGi framework (Equinox and/or Felix) will be more difficult.
> I haven't evaluated all the details, but IMHO the difficulty of adding 
> dynamic classloading in OSGi depends on what you what to achieve. In 
> OSGi classes in the main classloader of a bundle are imported, exported 
> or internal. For classes that a bundle export dynamic class loading is 
> more complicated as all bundles that import the class must be refreeshed 
> when the class is updated.
> But dynamic classloading in Cocoon has always been about isolated, e.g. 
> sitemap local class loading. As long as we are happy with bundle 
> internal classloading, it shouldn't be much different from the sitemap 
> local dynamic classloading of today.


> For inter bundle (block) dependencies, you can always stop, update, and 
> restart a bundle and refresh the OSGi framework, and the application 
> will work again with the new code (given that all services are dynamic 
> aware).

I think, what we need is a hook that the "stop, update and restart" process is 
done automatically, if the system is in "development mode". I just don't want to 
do it myself.

>> If you have some time, it would be really great if you could have a 
>> look at it. IMO the ReloadingClassloader is one of the most important 
>> features that we should add (developing [web]apps without it, isn't 
>> fun anymore for me).
> It should also be noted that Eclipse is based on OSGi and is rather 
> dynamic :) So it should be possible to achieve a high degree of dynamism 
> in OSGi based Cocoon, and we can possibly reuse some Eclipse bundles for 
> convenient application development.

yes, in the meantime I'm very optimistic that we will find ways to add RAD 
capabilities :-)

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

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



Telefonate ohne weitere Kosten vom PC zum PC:

View raw message