> From: Per Kreipke [mailto:[EMAIL PROTECTED]]
>
> > > If I do the following in an XSP, the CInclude transformer doesn't
> > > recognize
> > > the cinclude:include element because it has no namespace
> > > associated with it.
> > >
> > >
> >
> > This is incorrect.
>
> Of course. I thought it mi
> > If I do the following in an XSP, the CInclude transformer doesn't
> recognize
> > the cinclude:include element because it has no namespace associated
> with it.
> >
> >
>
> This is incorrect.
Of course. I thought it might take it from the a parent XSP element but it
doesn't.
> >name="sr
> From: Per Kreipke [mailto:[EMAIL PROTECTED]]
>
> If I do the following in an XSP, the CInclude transformer doesn't
recognize
> the cinclude:include element because it has no namespace associated
with it.
>
>
This is incorrect.
> strURL
>
>
>
> I had to change it to be:
>
> uri="http
2 11:35 AM
Subject: RE: Error Handling
And what about errors outside of ?
-Ursprüngliche Nachricht-
Von: Vadim Gritsenko [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 14. Mai 2002 16:26
An: [EMAIL PROTECTED]
Betreff: RE: Error Handling
> From: Michael Zehrer [mailto:[EMAIL PROTECT
And what about errors outside of ?
-Ursprüngliche Nachricht-
Von: Vadim Gritsenko [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 14. Mai 2002 16:26
An: [EMAIL PROTECTED]
Betreff: RE: Error Handling
> From: Michael Zehrer [mailto:[EMAIL PROTECTED]]
>
> Hi List,
>
> how
> From: Michael Zehrer [mailto:[EMAIL PROTECTED]]
>
> Hi List,
>
> how can one have a global static error-page in C2, I need this for a
> production system.
Put in every :
And develop error2static-html-page.xsl.
Vadim
>
> Cheers, Michael
>
--
Thanks!
-Original Message-
From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
Sent: 15 April 2002 15:31
To: cocoon-users
Subject: Re: Error handling with nested Velocity components
From: <[EMAIL PROTECTED]>
> Hi
>
> Does anyone know how to force a new page on the brows
From: <[EMAIL PROTECTED]>
> Hi
>
> Does anyone know how to force a new page on the browser when dealing with
> errors that come from a nested Velocity component? I'm finding that with
my
> current pipeline:
>
>
>
>
>
>
> causes the error to appear within the page, in the same way t
