Hi everyone,
I am trying to figure out the cleanest solution to managing a zone which
will be updated with numerous complex page fragments depending on the state
of the user.
There is one page with a zone which gets periodically updated depending on
the state of the user, the content is large enough to be organized into
pages itself. But since the server side event handler can only return a
Block or a component, I can't organize my page fragments into pages. And the
class/template code is too large to be placed inside a Block i.e. it will
not be very readable.
Placing the code inside components creates a problem of injecting the
component into the container. Since I have a possible 8 - 10 components, all
these will have to be injected and placed inside a Block to prevent from
being rendered, as shown below. As this does not look very clean to me is
there a better way to handle this?
Thanks in advance.
Anu
---------------------------
<t:zone t:id="zone" >
</t:zone>
<t:actionlink t:id="state" zone="zone" >state</t:actionlink>
<t:block>
<t:myComponent1/>
<t:myComponent2/>
<t:myComponent3/>
<t:myComponent4/>
....
</t:block>
----------------------------
@InjectComponent private MyComponent1 myComponent1;
@InjectComponent private MyComponent2 myComponent2;
@InjectComponent private MyComponent3 myComponent3;
@InjectComponent private MyComponent4 myComponent4;
.....
public Object onActionFromState() {
// business logic to figure out component
if (...)
return myComponent1;
else if (...)
return myComponent2;
.....
}
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/How-to-manage-complex-content-for-zones-tp5012792p5012792.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
