e -
> From: "Omar Carvajal"
> To: "Tapestry users"
> Sent: Tuesday, 5 October, 2010 07:19:27 GMT +02:00 Athens, Beirut,
> Bucharest, Istanbul
> Subject: Re: Dynamically loading a component
>
> This is horrible news since I have no way of knowing the co
s"
Sent: Tuesday, 5 October, 2010 07:19:27 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Dynamically loading a component
This is horrible news since I have no way of knowing the components that needs
to be called at design time (other wise I would use a ).
There is no magic
possible
combinations.
for more details take a look at the BeanEditor implementation.
g,
kris
Von:Omar Carvajal
An: Tapestry users
Datum: 05.10.2010 06:19
Betreff:Re: Dynamically loading a component
This is horrible news since I have no way of knowing the components that
This is horrible news since I have no way of knowing the components that needs
to be called at design time (other wise I would use a ).
There is no magic that can be done to achieve this at all? Even if I have to
use the internal services.
Thanks for your quick response.
Omar
On Oct 4, 2010,
On Mon, 04 Oct 2010 19:35:38 -0300, Omar Carvajal
wrote:
Hey all,
Hi!
I am trying to dynamically load a component which must be determined at
run time, I figured I must use a t:delegate to render the component.
On the Java side of things I cannot figure out how to instantiate the
actual c
Hey all,
I am trying to dynamically load a component which must be determined at
run time, I figured I must use a t:delegate to render the component.
On the Java side of things I cannot figure out how to instantiate the
actual component. I saw the @Component annotation with the "type" parameter
b
