Hi Juan!
My experience is that using an error page directive can take care of _some_
of the problems, not all. For now, I have simply put such a directive in
each page, and quite often Orion shows my error page when an error occurs.
However, if the error occurs on an included page, the contents on the
containing page are often combined with my error page, which gives me a mix
of two pages contents which all together is NOT valid XML.
In these cases I bypass the XSLT processor by removing the page's link to
it, and look at the source of the html to see the exception.
I have not had time to solve this yet, but I was thinking of using a dummy
error page containing a redirection header which would force the client to
call a REAL error page which will be delivered with no page mixing. This
would work, I think, but I would have to store the error information
somewhere in between the two page invokations, which is maybe not that
pretty after all. I will go ahead and make a post about this directly to the
list.
PS: I mailed this to the list aswell, as I think this is an important
subject which should also be brought up on the list.
Yours
Randahl
-----Original Message-----
From: Juan Lorandi (Chile) [mailto:[EMAIL PROTECTED]]
Sent: 6. marts 2001 19:53
To: '[EMAIL PROTECTED]'
Subject: Error page
Hi Randahl!
I remeber you've had some problems with orion errors being invalid xml and
you followed my suggestion of creating your own error page; I was wondering
if you could share it with me(or some pointers) because I have the same
problem now.
TIA
Juan
