>research into this memory leak Any info we can give on this problem to help? I've just come across the problem too.
On 30/05/2002 8:56 am, "Matt Sergeant" <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thursday 30 May 2002 2:24 am, Steven N��ez wrote: >> Is there a scheduled release date for 1.6? > > I've got two things I consider "pending": > > - - research into this memory leak (but I consider this low priority as I > don't > have a place to look yet and scouring the whole of AxKit is not fun). > - - make XSP work with tainting. I think this should be pretty easy. > > Since it's a four day weekend coming up, you should probably hope for > something after or during that. > >> On 30/5/02 8:20, "Kip Hampton" <[EMAIL PROTECTED]> wrote: >>> 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 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > > - -- > <:->get a SMart net</:-> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > > iD8DBQE89dsbVBc71ct6OywRAkf/AKCowaQnGfOF7qRENOPiBDz13S1P/ACeMliD > Hs048RonyRcZ1GbU4haXnsE= > =YvHA > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > 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]
