cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fagerstrom <dani...@nada.kth.se>
Subject Re: Taglib Block, and Re: Planning Cocoon's future
Date Wed, 24 Nov 2004 09:25:51 GMT
Vadim Gritsenko wrote:

> Reinhard Poetz wrote:
>
>> Daniel Fagerstrom wrote: 
>
<snip what="Info about taglib"/>

> About faces block; usage of taglib block there provided for an easy 
> "migration path" of JSP JSF taglibs into Cocoon Faces taglibs, and 
> final result is such that I can use very similar JSP JSF pages and 
> Cocoon Faces pages - the only difference is addition of namespace 
> declarations and removal of JSP taglib instructions. Both use same 
> expression language, so your 3rd party JSF editor can resolve and 
> validate expressions (and may be even code completion).
>
>>> IMHO, if the taglib is good enough, the best approach for JXTG 2.0 
>>> would be to refactor the JXTG tags to taglib tags, factor out the 
>>> object model and make the expression language plugable.
>>
>
> The problem I'm seeing with this is that JXTG should be implemented as 
> *generator*, with template pre-parsing, pre-processing, template 
> caching, and other features, whereas Taglib is *transformer* and can 
> not provide these options.
>
> Currently I'm seeing taglib as a step-up stone from JSP into the world 
> of Cocoon - once JSP EL and JSTL support is added to it, that is.
>
> PS Folks who currenly stuck with JSP are welcome to volunteer
>
> Vadim

Ok, thanks for the info. From what you say it seem better to let the 
taglib focus on its close connection to JSP taglib. After having studied 
the code in more detail I don't think it would be worthwhile to refactor 
it to handle the pre-compilation step needed for JXTG.

/Daniel



Mime
View raw message