camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Wolf <cwolf.a...@gmail.com>
Subject Re: Camel Mustache & Handlebars components
Date Mon, 10 Jun 2013 17:40:28 GMT
Oh, I see, ok.  Actually, upon further thinking, instead of wrapping
the in-memory
object graph in "SimpleHash" - there's an interface called
"TemplateModelIterator",
where, I think I could implement it such that the iterator returned would be an
iterator whose next() could return a "TemplateModel" representing the
current record and have a special end-of-group record that signals next()
to return null, thus closing the file.    I haven't tried that, but hopefully it
will work.

I see what you're saying about having a single client-side and
server-side template
language.


Thanks,

Chris

On Mon, Jun 10, 2013 at 11:52 AM, gquintana <gerald.quintana@gmail.com> wrote:
> No these components won't help you, they work exactly like FreeMarker. On
> Mustache Java, I think you can customize the way your object graph is walked
> when rendering the template (see BaseObjectHandler). But the whole message
> must fit in memory.
>
> I produced theses components because I am using Handlebars on the client
> side (in JavaScript) and I didn't want to introduce another templating
> language.
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-Mustache-Handlebars-components-tp5734043p5734068.html
> Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message