Why not use action or event links to do this?
If you need the links available from every page, then write yourself a
component that you drop onto any page (eg: a layout component). Then
you can do your heavy processing inside of the event handlers, even
return the new page to render.
Robert
On Nov 5, 2009, at 11/51:22 PM , josete wrote:
king on a page link makes the application do lot of business logic,
and then, sends the user to the end page.
The business logic is done inside in a non-viewable ( has no .tml )
page, inside its onActivate method .. who then return the resulting
page.
The flow is like this :
list.tml -> doTheLogic.java:onActivate -> result.tml / error.tml
I don't feel comfortable doing it like this .. but if any of you
think there's a better solution, please let me know.
As you can see, i am using a page as a 'business service' class ..
because i found no way to cook it ..
BTW: inside the doTheLogic.java i have a hibernate session injected,
and two T5 pages injected ( to be returned )
Thanks all.
---- some code ---
list.tml
<t:pagelink page="doSomeLogic" context="${thePlan.id}"><img src="$
{buybutton}"/></t:pagelink>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
