cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Hartle <>
Subject Re: [RT] Integrating Cocoon with WebDAV
Date Fri, 02 Nov 2001 13:24:09 GMT
Gianugo Rabellino wrote:

> Michael Hartle wrote:
>> I hope I understood you correctly; IOW, Cocoon perfectly produces and 
>> delivers content, but can hardly receive and decompose it. If we 
>> assume that we edited final dynamic and intermixed contents as a 
>> whole (e.g. a personalized corporate frontpage) via WebDAV, then I 
>> agree that reversing the production process is almost impossible to 
>> do. As I posted in my earlier response to Stefano, we have to target 
>> complete atomic contents instead, those informations that are being 
>> taken, transformed and intermixed. The URI space for standard web 
>> pages and WebDAV operation does not necessarily have to be the same, 
>> nor would it make sense.
> Exactly. It would be perfectly feasible, given a generic WebDAV 
> support to deploy a Cocoon application configured in such a way that 
> content can be clearly identified and edited. But if this is true I 
> see no point in using Cocoon over mod_dav, Slide or even the Tomcat 4 
> servlet. I think that this effort should be undertaken only if there 
> is a clear advantage over existing technologies: being Cocoon a 
> framework even the WebDAV stuff should be really generic and 
> extendable, which means that it should be possible to use it 
> independently from any actual layout. If this is not the case it 
> wouldn't make sense to spend resources in this task (of courseIMHO). 

My target is not in using WebDAV to deploy Cocoon applications, but to 
expose a virtual drive with virtual folders containing virtual contents 
with the power of Cocoon over WebDAV; loadable content would be 
generated on the fly as needed, and when content is being saved, it is 
being handled (unpackaged and saved somewhere, for instance) depending 
on your specific demands.

The pipeline concept of Cocoon has Generators as a start and Serializers 
as an end; in a way, a Generator could be considered a Deserializer. I 
had a short look into SOAP some time ago and when I heard of SOAP 
logicsheets running with Cocoon 2, I was of the opinion that Ovidiu had 
taken exactly that way. If we are able to deserialize the content being 
saved, a kind of reversing the serialization process that will not work 
in all cases (no perfect way from JPEG to SVG, I know...), but can be 
done in some.

The situation is that I have to spend work on integrating WebDAV with 
Cocoon as I definitely need such a setup, so the resources (at least 
mine ;) ) will be spent on this subject, and I am hoping on good ideas 
and hints how to do this right, so that this investment gives maximum value.

Best regards,

Michael Hartle,
Hartle & Klug GbR

To unsubscribe, e-mail:
For additional commands, email:

View raw message