On Monday, Feb 3, 2003, at 06:52 Europe/London, S Woodside wrote:
Hi i'm getting into XSP now :) When I run the following xsp everything is fine, but if I change the content to just <util:include-file name="form.html"/> (without the <test></test> around it, I get bad juju errors. Is that of interest to anyone? It's weird to me, because putting in just <test/> gives no errors, and form.html contains valid XML. It's a very unhelpful error too (see below).I think the error messages with CVS should be slightly more intuitive.
But basically it's the expected behaviour. How XSP works is there are logically two sections:
<xsp:page>
GLOBALS SECTION
OUTPUT SECTION
</xsp:page>
The only way we can distinguish between the two is via what is called the "user root" element - i.e the root element for the output.
This is further complicated by taglibs of course, where you might want to consider your taglib to be your user root element, but the XSP engine basically detects the user root as the first non-taglib tag. Because even the xsp:* tags are implemented as a taglib.
There may be a way to fix it, but for now I've tried to make the error message clearer in 1.6.1 (unless that was 1.6.1 you were running, in which case I didn't fix it properly ;-)
Hopefully this isn't too confusing ;-)
Also I have another question. What's up with the PI for the xsp being either . or NULL in some mailing list posts?Originally I always used "." but found very quickly that it had two problems - it was hard to see when scanning a bunch of config directives, and also "." might indicate the current directory, which isn't desirable. So I started using NULL instead, and now I always use NULL. In reality it doesn't make a squat of a difference what you type there.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
