an
Tapestry users users@tapestry.apache.org
An
Tapestry users users@tapestry.apache.org
Kopie
Thema
Re: Substitution for Switch/Case/Block to embed components really dynamic
?
No. That's the drawback of the caching of pages and their component
structure done by Tapestry.
Uli
I think Its the right direction, but there is always the main problem:
How to get and add a component which is not defined/bound in any page
template?
Is that possible at all?
Am 04.09.2009 um 01:43 schrieb Thiago H. de Paula Figueiredo:
BeanEditor and BeanEditForm use blocks from different
No. That's the drawback of the caching of pages and their component structure
done by Tapestry.
Uli
On 04.09.2009 13:56 schrieb Stefan:
I think Its the right direction, but there is always the main problem:
How to get and add a component which is not defined/bound in any page
template?
Is
Hi again,
i'm currently working on a solution to embed custom components really
dynamic.
In short:
I have a page with a custom component with a specific parameter.
The component does nothing else than embedding (one) another custom
component,
based upon the passed parameter value. (and
BeanEditor and BeanEditForm use blocks from different pages to edit
properties. Its something similar to what you want to do. Ultimately, they
get a block from a given page using this code (adapted from
BeanBlockOverrideSourceImpl.toBlock()):
Page page = pageCache.get(pageName);
return
