Does the book document the "Yet Another Petstore" as a web-tier only, or as a web-tier with an EJB (SLSB) backend?
Does the framework also support an ACID transaction across multiple requests, against more than one database connection, or across more than one VM. I'll be first in line to buy the book if it does! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pat Lightbody Sent: Wednesday, September 17, 2003 11:23 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] hibernate/webwork2 best practices Glad you like it! Spread the word :) I've used Hibernate + WebWork2 in a couple projects, and I always used the design that spawned from our (Mike/Joe/Ara/Mine) upcoming book that involves writing Yet Another PetStore. Basically, we used the IoC support offered by XWork and the following: * PersistenceManager interface * HibernatePersistenceManager class * PersistenceAware interface * HibernateConfiguration The HPM class was scoped at _request_ scope in components.xml and depended on another component, HibernateConfiguration, that is scoped at _application_ level so that we can keep a single SessionFactory around. Hope that helps. -Pat ----- Original Message ----- From: "Anoop Ranganath" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 16, 2003 8:31 PM Subject: [OS-webwork] hibernate/webwork2 best practices > I just started using WebWork2 yesterday, and I'm sold. A new > techonology hasn't kept me smiling for so long thinking "this is > right" since I first started playing with Ruby. > > I'm writing a vanilla database backed webapp for my client, and I'm > trying to decide where I should put the persistence code within the > WW2 framework. Right now I've implemented the Thread Local Session > seen here ( http://hibernate.bluemars.net/42.html ). I created a DAO > which uses the Thread Local Session to retrieve and persist the > business objects. I've made the DAOs components on the session and > any actions that need them are enabled for the DAOs. > > The thing is this seems clunky to me. I've only been using the > framework for two days, but something about this approach doesn't feel > like I'm fully leveraging WW's capabilities. I can't quite get my > nose on the smell, but it's definitely there. > > Any ideas? I'm sure this is a problem that's been solved many times > over. > > Anoop > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
