Carsten Ziegeler wrote:
Shouldn't we make these decisions on this list in the public? Not every
committer was at the GT and took part in the discussions.
Definitly! Therefore my note in my previous mail (
* I/we know, it's unofficial so far as it hasn't been discussed on the mailing
list. ).
So what do others think about this roadmap?
>>- Cocoon 2.2 will not use OSGi but will support blocks as far as possible:
>> - blocks protocol (= sitemap blocks)
>> - a block gets its own component manager that contains all local components
>> and gets the block component managers of all wired blocks as parent.
>> - we use M2 as build and deployment tool (needs some special M2 plug-ins
>> for the deployment part)
>> - blocks are *not* spread over different directories during deployment
>> - a block can contain classes in [block]/BLOCK-INF/classes that are added
>> to the context classloader
>>
>> --> this means that everything, that real blocks promise, works except the
>> shielding of Java classes.
>>
>>- Cocoon 3.0 will use OSGi
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
