Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <452762C3.5050102@apache.org>
Date: Sat, 07 Oct 2006 10:18:11 +0200
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: svn commit: r453534 -
 /cocoon/trunk/tools/archetypes/cocoon-22-archetype-block/src/main/resources/archetype-resources/pom.xml
References: <20061006090632.912FE1A981A@eris.apache.org>
 <4526353A.1090300@mobilebox.pl> <4526376C.4090201@mobilebox.pl>
 <4526467E.6060309@apache.org> <45265497.402@mobilebox.pl>
 <452660E1.9060303@apache.org> <452695D6.7060908@apache.org>
 <45275CD8.6090008@apache.org>
In-Reply-To: <45275CD8.6090008@apache.org>
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 7bit

Reinhard Poetz wrote:
>>> 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?
> 
Giacomo and I talked a little bit about this at the GT and to be honest,
we are not sure if it's 100% feasible, but it should! (I really love
such answers).

We are able to find all jar files containing a COB-INF directory through
the class loader and we should be able to get a stream to this jar.
Then we can just go through the archive, find the files, and register
them somewere.

Carsten
-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/