Hi Ramprasath, here are my thoughts perhaps you can find them useful when I read this part of the requirement....
> 2. System will automate the report generation process , i.e kind of query > builder ..Which will connect to the data base and user can generate query > using user interface ( i.e selecting table/view and select display columns > and apply where clause conditions , apply group by and order by condition , > output type(pdf/html ) ) > and output will be generated based on above conditions > I thought..., Why would this guy use Hibernate?? a reporting application may require to develop/execute very complex sql queries... and when it comes to translate those queries to hibernate HQL/Criteria sometimes you could lose part of your hair... (according to my experience) if the queries required by reporting application are so complex (and on this applications it may come as complex as the user wants) that it would be easier to execute a native sql query through the hibernate session... well... at that time you 'll realize that it would 've been better to directly avoid hibernate. it's not so bad working without hibernate... (sure, you should code/design some supporting structure for accesing database and mapping result sets on a nice and clean fashion) most of all on this case where it seems that... somebody issues a query through the user inteface and you just have to spit up the result set on the screen... so my advice... for complex queries applications avoid hibernate (you 'll end up calling native sql... so why bothering with the framework at all?) remember it's just an opinion. :) cheers... Nicolás.- On Fri, Feb 10, 2012 at 9:56 AM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > 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-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > >
