Thanks Robin for your indication, it will save me hours ;-)
In that case, it is possible to use Xinclude, but in other case it could be usefull to get into util:include-*. So you mean the problem is independant of me, and that it a kind of bug ? On Fri, 1 Feb 2002, Robin Berjon wrote: > Hi Marc, > > On Friday 01 February 2002 17:02, Marc-Olivier Bernard wrote: > > I am using XSP Util taglibs (the very fresh one) on AxKit 1.5 > > (libxml2-2.4.12-1, XML::LibXML 1.31), and i often > > get the following trouble (the sample is *very silly*, it is just for > > trial !) : > > > > <util:include-uri href="http://sparta/AxKit/sample/nav.xml"/> > > > > It sometimes works (with exceptions in errog_log file) and sometimes leads > > to server internal error with such messages in error_log : > > > > [AxKit] [Error] Empty string at > > /usr/lib/perl5/site_perl/5.6.0/i386-linux/XML/LibXML.pm line 158. > > The error above is the problem: XML::LibXML gets an empty string instead of a > real document to parse (I struggled against this error for hours the other > day). > > I don't know what causes it to receive an empty string, perhaps at times the > document it fetches is absent or something? Also, you might want to look into > XInclude instead of util:include to, well, include documents as it'll > probably save you some overhead. > > Perhaps we could also try to inform the user better when such an error occurs > ? I'm not sure we can intercept the cases correctly though. > > -- Marc-Olivier BERNARD Mel [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
