cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Re: svn commit: r453534 - /cocoon/trunk/tools/archetypes/cocoon-22-archetype-block/src/main/resources/archetype-resources/pom.xml
Date Sat, 07 Oct 2006 07:52:56 GMT
Leszek Gawron wrote:
> Carsten Ziegeler wrote:
>> Leszek Gawron wrote:
>>>> Hmm, that's bad - I don't see a solution for this now. But we discussed
>>>> at the GT an alternative handling of our blocks which would make the
>>>> cocoon:deploy plugin obsolete.
>>> which is ?
>> :)
>> Currently the deployer extracts the files from COB-INF and META-INF into
>> the file system (into the web application). We talked about skipping
>> this step and adding a mechanism to the core of Cocoon which allows to
>> access the information from within the jar without extracting it.
>> This should be doable by using the class loader and some detection
>> mechanism and avoids the deployer plugin. And more important it means
> Seems like cocoon solutions are always a step ahead my comprehension. Is 
> this really feasible?

Why not?

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