xml-xsp-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sergeant <m...@sergeant.org>
Subject Re: taglib application order (was: Re-purposing XSP)
Date Sat, 10 Mar 2001 18:32:11 GMT
On Sat, 10 Mar 2001, Tagunov Anthony wrote:

> Hello, evrybody!!
> 
> On Thu, 8 Mar 2001 15:50:44 -0000, Allan Erskine wrote:
> >XSP page generation
> <snip/>
> >Taglibs are introduced by namespacing in any element, eg. <p
> >xmlns:esql="http://apache.org/sql">,.....<p> (end of tag lib scope)
> >including the root element.
> 
> Please excuse me (somewhat a lurker) for boldness, but still:
> since there's some talk here on a kind of "refactoring xsp" (Allan)
> (or refactoring the way it is used Matt), maybe it would be a good
> time to consider the questions that (IMHO ;) have long been in the 
> way of XSP developers:
> 
> -1- the order in which the taglibs are applied
> -2- taglib A being dependent on taglib B:
>   -2.1- taglib A producing tags processed by taglib B
>   -2.2- taglib A requiring some other code generated by taglib B
> 
> Please tell if i miss something: has -1- (aka -2.1-) been solved? 

It has in AxKit, it requires further abstraction for Cocoon
(e.g. SiLLy). It's basically a weakness of Cocoon's serial taglib
application model (whereas in AxKit taglibs are applied in parallel).

-- 
<Matt/>

    /||    ** Founder and CTO  **  **   http://axkit.com/     **
   //||    **  AxKit.com Ltd   **  ** XML Application Serving **
  // ||    ** http://axkit.org **  ** XSLT, XPathScript, XSP  **
 // \\| // ** mod_perl news and resources: http://take23.org  **
     \\//
     //\\
    //  \\


Mime
View raw message