You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Michael Homeijer <M....@devote.nl> on 2002/09/23 10:07:43 UTC
RE: WebDAV sitemap
Hi,
I found and received info on slide, but I was thinking of a sitemap that has
matchers and additional actions, transformers etc. that make supporting
webdav from an application much easier. This way you can easily expose an
application as a webdav resource. A sample sitemap would contain the
following matchers:
<map:match pattern="/">
<map:act type="requestmethod">
<map:generate src="cocoon:{request-method}"/>
<map:serialize/>
</map:act>
</map:match>
<map:match pattern="PROPFIND">
</map:match>
<map:match pattern="PROPPATCH">
</map:match>
<map:match pattern="MKCOL">
</map:match>
etc.
Does this make sense?
Michael.
-----Original Message-----
From: Michael Homeijer
To: 'cocoon-users@xml.apache.org'
Sent: 20-9-2002 2:10
Subject: WebDAV sitemap
Has anybody developed a sitemap in which webDAV requests can be handled?
I am looking for a good start to add a webdav interface to part of my
application.
TIA,
Michael
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: WebDAV sitemap
Posted by Martin Holz <ho...@fiz-chemie.de>.
On Monday 23 September 2002 10:07, Michael Homeijer wrote:
> Hi,
>
> I found and received info on slide, but I was thinking of a sitemap that
> has matchers and additional actions, transformers etc. that make supporting
> webdav from an application much easier. This way you can easily expose an
> application as a webdav resource. A sample sitemap would contain the
> following matchers:
>
> <map:match pattern="/">
> <map:act type="requestmethod">
> <map:generate src="cocoon:{request-method}"/>
> <map:serialize/>
> </map:act>
> </map:match>
>
> <map:match pattern="PROPFIND">
> </map:match>
>
> <map:match pattern="PROPPATCH">
> </map:match>
>
> <map:match pattern="MKCOL">
> </map:match>
>
> etc.
>
> Does this make sense?
Yes, adding Webdav methods to the cocoon makes sense. However
it would duplicate the work done for the slide webdav servlet.
Slide webdav contains lot of code, so porting it to cocoon is a
major project.
Do you want to extend the matcher or introduce a new one? You could do either
<map:match type="wildcard" method="PROPFIND" pattern="**./ >
....
</map:match>
or
<map:match type="wildcard" pattern="**./ >
<map:select type="webdav">
<map:when test="PROPFIND">
...
</map:when>
<map:when test="PUT">
...
</map:when>
</map:select>
</map:match>
I would prefer the second solution, since you don't have to change
existing matchers.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org