On Tue, 2004-12-07 at 00:45 +0100, Jonas Ekstedt wrote:
> On Mon, 2004-12-06 at 22:32 +0100, Sylvain Wallez wrote:
> > Glen Ezkovich wrote:
> >
> > >
> > > On Dec 6, 2004, at 9:00 AM, Sylvain Wallez wrote:
> > >
> > >>
> > >>> Reinhard Poetz wrote:
> > >>
> > >>
> > >> Yeah, cocoon-dev has gone crazy during the week-end :-)
> > >>
> > >>> more than one EL per template is clear FS to me. I'd be in favor of
> > >>> specifying EL at the TemplateGenerator declaration time, and would
> > >>> not go more granular than this.
> > >>
> > >>
> > >>
> > >> I don't agree: it happens quite often to have mixed view data
> > >> combining java objects and XML.
> > >
> > >
> > > Hmmm... why does this happen? It seems that the java could be injected
> > > by by one component and the XML by another.
> >
> >
> > Not always, e.g. when you have an XML document and objects describing
> > its metadata which are both managed by a flowscript.
>
> Fully agree. Restricting expressions to only one type would be quite bad
> I think. In addition to xpath and jelly it would also be cool with
> formatting expressions (ie ${format:<jelly-expression>#type}). As an
> example of all three types (xpath, jelly and format) consider a site
> with some articles and a calendar on it:
>
> <body>
> <p>Your last login: ${format:user.lastLogin#short}</p>
>
> <h3>This months calendar</h3>
> <calendar:month currentDate="${jelly:today}"/>
>
> <h3>Articles</h3>
> <dom:out select="${xpath:/domVariable/articles/article}
> </body>
>
> Cheers Jonas
Oops! jelly -> jexl
// jonas
