On Fri, 10 Feb 2012 03:03:20 -0200, Ramprasath
<jothiprasath2...@gmail.com> wrote:
Dear Friends ,
Hi!
5. Now the requirement is Client wants to turn this to dynamic ..i.e
In the very first screen user should provide the connection details
through
screen ...( Server , user name , password ,database )..
This requirements seems like something you'd read in thedailywtf.com . . .
In tapestry ..hibernate session object is been build on start up as
singleton ...
What you're saying isn't correct for Tapestry as a whole. Tapestry doesn't
prevent you to create a new SessionFactory every time you connect to a
database, which seems to be the solution for your problem.
Tapestry-Hibernate, which you don't need to use to use Tapestry with
Hibernate, is just an easy way to get the most common scenario working:
single database with static configurations.
Your solution: don't use Tapestry-Hibernate, create a SessionFactory using
the configurations you've got from the user, then use it to get a Session,
then do the queries based on it.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, 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
