Em Sun, 10 Jan 2010 15:09:30 -0200, Jim O'Callaghan
<jc1000...@yahoo.co.uk> escreveu:
Thanks for the replies. I can see how this would work between
pages/components but how would it work say from a service that was used
as some sort of entity manager? Would it be a question of passing it as
a
parameter to each method call on the service that requires data from it
or is there a way to access it from a service?
Use the ApplicationStateManager service to manipulate session state
objects in other services.
By the way, you can use some sort of cache to avoid hitting the database
all the time. You can do it easily if you're using Hibernate (second-level
cache).
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
Coordenador e professor da Especialização em Engenharia de Software com
Ênfase em Java da Faculdade Pitágoras
Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate
Sócio, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
