Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (nike.apache.org: domain of
 thorsten.scherler.ext@juntadeandalucia.es designates 217.12.18.114 as
 permitted sender)
Subject: Re: Listener in cocoon 2.2
From: Thorsten Scherler <thorsten.scherler.ext@juntadeandalucia.es>
To: dev@cocoon.apache.org
In-Reply-To: <45c308810909291227w6e905efalb2e45bf2403acdee@mail.gmail.com>
References: <1254217080.3532.31.camel@asf>
	 <45c308810909291227w6e905efalb2e45bf2403acdee@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 30 Sep 2009 09:20:36 +0200
Message-Id: <1254295236.3532.38.camel@asf>
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable

On Tue, 2009-09-29 at 20:27 +0100, Dominic Mitchell wrote:
> On Tue, Sep 29, 2009 at 10:38 AM, Thorsten Scherler
> <thorsten.scherler.ext@juntadeandalucia.es> wrote:
>         Hi all,
>        =20
>         what is the best way to implement a Listener in cocoon 2.2?
>        =20
>         I our use case we have a "listener" uri that got dispatched by
>         an
>         external application to notify that some resources have
>         changed and
>         invalid our cache for that resource.
>        =20
>         The thing is that the uri do not have to/will not return
>         anything in the
>         body only in the request header.
>        =20
>         The current solution which was presented to us uses a custom
>         generator
>         which will not output anything. That just does not feel right.
>        =20
>         I did a small test with
>         <map:match pattern=3D"notify">
>          <map:act type=3D"notify"/>
>          <map:generate src=3D"notify.xml"/>
>          <map:serialize/>
>         </map:match>
>        =20
>         but that is just to make it work the normal cocoon way. The
>         notify.xml
>         is a dummy and I am not really thrilled about that neither.
>        =20
>         Using flow seems to be as well too much since we just want a
>         simple
>         listener that returns only http header.
>=20
>=20
> Last time I needed something like this I used the "empty:" source.

That is a custom input module, right?

>   Combined with a reader, that should do the track.
>=20
>=20
>   <map:match pattern=3D"notify">
>     <map:read src=3D"empty:" />
>   </map:match>
>=20
>=20
> This is untested =E2=80=94 I can't remember if there are any quirks.
>=20


Yeah will reduce the match nicely. Thanks Dom.=20

salu2

>=20
> -Dom=20
--=20
Thorsten Scherler <thorsten.at.apache.org>
Open Source Java <consulting, training and solutions>

Sociedad Andaluza para el Desarrollo de la Sociedad=20
de la Informaci=C3=B3n, S.A.U. (SADESI)