Reinhard Poetz wrote:
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?
By asking "is this really feasible" I hoped someone would say exactly how :)
--
Leszek Gawron, IT Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
