Speaking of which, have you taken a look at that? Would it make sense to make that the basis of Conductor?
> -----Original Message----- > From: Matthew E. Porter [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 17, 2003 11:40 AM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] hibernate/webwork2 best practices > > > FYI: I believe this is how the Spring Framework got started. > > > Cheers, > matthew > > On Wednesday, September 17, 2003, at 10:31 AM, Jason Carreira wrote: > > > +1 to that... The code from the book looked good... You guys > > +interested > > in contributing it (or at least the infrastructure bits)? > > > >> -----Original Message----- > >> From: Matthew E. Porter [mailto:[EMAIL PROTECTED] > >> Sent: Wednesday, September 17, 2003 11:29 AM > >> To: [EMAIL PROTECTED] > >> Subject: Re: [OS-webwork] hibernate/webwork2 best practices > >> > >> > >> Patrick: > >> According to Wiley's website, the books is due in > November. When > >> will this code be available? The code I sent Jason has > some similar > >> interfaces but I would prefer to "standardize" on one as it would > >> seem weird that Conductor is not based upon the same code (and > >> practices) as > >> the first book talking about integrating these. > >> > >> > >> Cheers, > >> matthew > >> > >> > >> On Wednesday, September 17, 2003, at 10:22 AM, Pat Lightbody wrote: > >> > >>> 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 > >> > > > > > > ------------------------------------------------------- > > 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
