Try the following... In your exception throwing code, write the error into pnotes.
Create a provider which will read that error from pnotes and pass it to axkit. Create a virtual location, and set that up to use that provider, delivered with axkit. Make that location your 500 error document in apache. Mike. --- David J Craigon <[EMAIL PROTECTED]> wrote: > Hi there, > I've put together an AxKit application. I've got > some dynamic HTML > pages. These are produced by writing custom > Apache::AxKit::Providers > which produce XML, which is then processed by XSLT > stylesheets by AxKit. > Sometimes the Providers encounter problems, and > throw AxKit exceptions. > Elsewhere in the website I produce text/plain > content. Now at the > moment I do this through standard Apache mod_perl > handlers. These also > encounter problems sometimes. > > What I really want to do is to throw AxKit > exceptions in my ordinary > handlers. That way the user can be shown my fancy > error page, and I > don't have to write two error handling routines. > > Can anybody offer me some advice on how I could > achieve such an effect? > I've tried converting my handlers to AxKit providers > that produce plain > text, rather than XML, but that upsets the code that > parses the XML to > work out which stylesheet to use, since it isn't > XML. > > Any advice will be most welcome, > David > > > This message has been scanned but we cannot > guarantee that it and any > attachments are free from viruses or other damaging > content: you are > advised to perform your own checks. Email > communications with the > University of Nottingham may be monitored as > permitted by UK legislation. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
