DynamicTemplate issue

[Martin Kersten <ma...@gmail.com>]

Hi there,

   I still try to get DynamicTemplate working. Since I debugged into it it
seams that the parser of the dynamic template just returns dom elements and
never tries to analyze any element and map it towards components.

Am I correct on this?

Is someone able to use a dynamic template component to render child
components?


Cheers,

Martin (Kersten)

Re: DynamicTemplate issue

[Martin Kersten <ma...@gmail.com>]

Its not about the binding. Its about discovering any components at all.
During the dynamic parser session it seams that no child component related
behaviour is triggered at all. I can use any tag name it doesnt matter. I
need to check whether I am in production mode also since there seams to be
no validation going on.

I need to check if a dynamic component can nest any other component. Maybe
something is broken over here.


2013/10/26 Lance Java <la...@googlemail.com>

> Have you seen the code I provided on the "jack of all trades page" thread?
> I've pretty much solved the problem there. Tapestry uses bindings to read
> and write values during rendering. Eg the prop: binding.
>

Re: DynamicTemplate issue

[Lance Java <la...@googlemail.com>]

Have you seen the code I provided on the "jack of all trades page" thread?
I've pretty much solved the problem there. Tapestry uses bindings to read
and write values during rendering. Eg the prop: binding.