On 26/10/09 08:25, Søren Krum wrote:
The access to hibernate managed java objects is done via the standard hibernate way: Getting a factory, getting a session, fetching/manipulating your object. We use a central class, a (scope=singleton) HibernateUtil, to get the connection to the different hibernate session factories. This Util class additionally offers some easy ways to fetch and delete objects without carying for all the session/transaction stuff. Handy if you need your hibernate objects in a flow script.
More or less same here, though I used a filter Servlet to take care of sessions and bound them to the localthread of each servlet invocation, in order to avoid the oops-the-session-expired-while-the-pipeline-was-being-processed issue.
I manipulatoed DAOs via Flowscript for added flexibility, which means every Java domain class has its own DAO class for manipulation... hmm... not really, some domain classes I managed to subclass.
What I miss is a more direct way from domain classes to the (AJAX) client and back, without all the packing and unpacking of things (though I used JSON for communications)... I suppose Restlet/Kauri may come in handy, but I did not feel like plunging into it.
Regards, -------------------- Luca Morandini www.lucamorandini.it -------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
