Paul Lieberman wrote:
>
> I'm getting
> ErrorStylesheet: No module mapping found for type ''
> when trying to veiw the test documents from the instructions. The xml
> file clearly shows the type= attribute and I get the same error with
> both the xsl and the xpathscript stylesheets. I added all the stuff from
> the instructions to my httpd.conf file as well.
This is actually a long-standing bug that Matt knocked down in CVS just
this morning.
The missing mapping error is the result of an over-eager config reader
that assumes that the AxErrorStylesheet config directive is defined.
The AxErrorStylesheet directive offers a way to define a language
processor and stylesheet file to transform the XML backtrace produced
from any errors that AxKit encountered while processing-- the
transformed result is sent to the browser instead of the usual,
depressing 500 Internal Server Error.
The sum of this is that AxKit is encountering an error *besides* the "no
mapping" one that appears last in the logs-- the "no mapping" error is
thrown while trying to process the real error for delivery to the
browser.
Anyway... you have two choices:
Wait for AxKit 1.6
or
Snag the stylesheet I use to process errors [1] and add the following to
your config:
AxErrorStylesheet application/x-xpathscript /path/to/error.xps
AxStackTrace On
HTH,
-kip
[1] http://hampton.ws/download/files/error.xps
--
print join ' ', map { ucfirst($_->getFirstChild->getData)}
XML::LibXML->new()->parse_string(join '', pack "c*", (60, 122, 62, 60,
97, 62, 106, 117, 115, 116, 60, 47, 97, 62, 60, 98, 62, 97, 110, 111,
116, 104, 101, 114, 60, 47, 98, 62, 60, 99, 62, 112, 101, 114, 108, 60,
47, 99, 62, 60, 100, 62, 88, 77, 76, 60, 47, 100, 62, 60, 101, 62, 104,
97, 99, 107, 101, 114, 60, 47, 101, 62, 60, 47, 122,
62))->findnodes('//*[name() != "z"]')->get_nodelist;
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
