Return-Path: 
 <cocoon-dev-return-29308-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 43098 invoked by uid 500); 10 Jul 2002 16:20:28 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 43086 invoked from network); 10 Jul 2002 16:20:27 -0000
From: "Per Kreipke" <per@onclave.com>
To: <cocoon-dev@xml.apache.org>,
	<nicolaken@apache.org>
Subject: RE: [PROPOSAL] Extending Sitemap Error Handling
Date: Wed, 10 Jul 2002 12:22:21 -0400
Message-ID: <FCEPLAOECPOAGINFDFCHAEOHFJAA.per@onclave.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <3D2C4ED3.8070601@apache.org>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Nicola wrote:

> > Will whatever the new syntax is allow something like this?
> >
> > <!-- Symbolic only, actual syntax may vary -->
> > <map:handle-errors exception="org.foo.com.RedirectException">
> >   <!-- RedirectException puts destURL in the sitemap parameters -->
> >   <map:redirect-to href="{destURL}" />
> > </map:handle-errors>
> >
> > That's be nice, then I could actually redirect from generators (and even
> > transformers, etc).
>
> Exactly what I want to prohibit.
>
> Error handling should *not* redirect or create loops.
> If it's part of the flow, use an Action to tell it to the next
> components, not exceptions, which are... exceptional ;-)

What about the site developer who doesn't know Java but understands XML and
XSL? Or even a bit of XSP with the great taglibs we've got but doesn't know
enough to code an Action in Java.

[Assume for a second the database actions aren't good enough because we
don't allow direct DB access from the Cocoon layer]

> Redirecting is generally not needed, and Cocoon was made so to not make
> erdirects part of the necessary flow.

This is the basic part of C2 I don't understand. Given a form that posts to
a different URL, how do you get back to the form page (or a summary page)?

Like this?

<match "form">
  <generate>
  <transform>
  <serialize>
</match>

<match "POST">
  <act "doMyPost">
    <redirect-to "form-or-summary">
  </act>
  <generate "form again with errors">
  <!-- Does this mean form is in sitemap in two places? -->
  ...
</match>

I find that difficult conceptually and haven't even gotten it working.

Per


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org