I'm currently in the process of porting an application from T4->T5 and have
run into a problem.
Specifically the application has 100+ pluggable modules. Each module has
it's own jar containing its specific classes and related Tapestry config
class/template. A custom class loader loads the modules
I'm sure I'm doing something silly here but how can I ensure components keep
their "panel" context when events occur later?
More broadly speaking has anyone managed to implement a dashboard style
application (i.e.layouts/panels) and what is the correct pattern to use?
act with it how to ensure the
original context is somehow presented back to the component so it can
interpret the event correctly.
Any suggestions gratefully received, this really is vexing me.
Regards,
Scyta1e
Thiago H. de Paula Figueiredo wrote:
>
> On Mon, 21 Jun 2010 16:06:38 -0300, Pi
