On Tuesday, August 13, 2002, at 06:42 AM, Daisuke Maki wrote:
>
> I was fooling around with XSP Taglibs when I encountered this...
>
> From previous discussions I was aware that you needed to have a non-xsp
> root tag in the xsp:page in order to make things work:
>
> <xsp:page ....>
> <foo>
> <bar />
> </foo>
> </xsp:page>
>
> That's just fine, but what I'm confused about is this: if you create
> your taglib+namespace like so:
>
> <xsp:page ....>
> <my:foo>
> <my:bar />
> </my:foo>
> <xsp:page>
>
> In this case it seems that either AxKit::XSP::SAXHandler::start_document
> doesn't get called, or at least it doesn't create the
>
> sub handler {
> my( $r, $cgi, $document ) = @_;
> ....
When I've talked about a "non-XSP tag" in the past, what I really mean
is a non-taglib tag, but I didn't want to confuse people with the detail
that all the xsp: tags are just implemented as a core taglib.
As for making it work anyway, that's probably doable, it would just be a
little extra magic. Please feel free to try.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
