Objet : Re: [OS-webwork] hibernate/webwork2 best practices
We're working on finishing up the code as I type... very soon!
- Original Message -
From: "Francisco Hernandez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 19, 2003 12:18 AM
Subject
We're working on finishing up the code as I type... very soon!
- Original Message -
From: "Francisco Hernandez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 19, 2003 12:18 AM
Subject: Re: [OS-webwork] hibernate/webwork2 best practices
any update on when this code will be shared with us? (can you tell im
anxious? :)
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
wr
gt;
Sent: Wednesday, September 17, 2003 8:31 AM
Subject: RE: [OS-webwork] hibernate/webwork2 best practices
+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:
al 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 Wi
: [EMAIL
PROTECTED]
[EMAIL PROTECTED]cc:
ceforge.net Subject: Re:
[OS-webwork] hibernate
> -Original Message-
> From: Matthew E. Porter [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 17, 2003 2:10 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webwork] hibernate/webwork2 best practices
>
>
> I have looked at Spring and even had a chance to
-- From: "Jason Carreira"
<[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2003 8:31 AM
Subject: RE: [OS-webwork] hibernate/webwork2 best practices
+1 to that... The code from the book looked good... You guys
interested
in contributing it (or at least th
1 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
Wednesday, September 17, 2003 8:31 AM
Subject: RE: [OS-webwork] hibernate/webwork2 best practices
+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
Multiple requests does not necessarily mean a long-lived transaction. I
was thinking of a general case when one may want to use a redirect thus
creating a second request.
Basically, I was asking Pat if the book's framework used Hibernate in a
way that supports transactions especially in a componen
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]
&g
ook 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:
s Cook [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 17, 2003 12:56 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [OS-webwork] hibernate/webwork2 best practices
>
>
> Does the book document the "Yet Another Petstore" as a
> web-tier only, or as a web-tier with
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 wor
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?
ry at this point :)
-Pat
- Original Message -
From: "Jason Carreira" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2003 8:31 AM
Subject: RE: [OS-webwork] hibernate/webwork2 best practices
+1 to that... The code from the book looke
gt; 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 "standardiz
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 fi
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:
* Persi
Subject: Re: [OS-webwork] hibernate/webwork2 best practices
>
>
> > Conductor is just starting to get started... I've gotten a
> little busy
> > trying to get WW2 out... I keep trying to get Matt Porter and Mike
> > Cannon-Brookes to start doing the Condu
Anoop Ranganath wrote:
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 sho
Conductor is just starting to get started... I've gotten a little busy
trying to get WW2 out... I keep trying to get Matt Porter and Mike
Cannon-Brookes to start doing the Conductor work for me, but they
haven't fallen for it yet :-)
Jason, did you ever look at the code I sent over?
Cheers,
matt
tember 17, 2003 8:42 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [OS-webwork] hibernate/webwork2 best practices
>
>
> I was replying to his statement that he:
>
> > currently in my daos i create a session object for every
> > dao operation like dao.save dao.load, e
I was replying to his statement that he:
> currently in my daos i create a session object for every
> dao operation like dao.save dao.load, etc
I was assuming that he was also doing a flush after each of these
operations.
-Original Message-
From: Jason Carreira
> This is not how Freerol
This seems like a good approach to me, what seems wrong to you?
It would be nice to have the ability to have inverted component
dependencies (i.e. have your Session-level DAOs depend on a
request-level Session wrapper, so you don't need a ThreadLocal), but I'm
not sure how that could work. Maybe y
and Mike
Cannon-Brookes to start doing the Conductor work for me, but they
haven't fallen for it yet :-)
> -Original Message-
> From: James Cook [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 17, 2003 6:43 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [OS-webwork
uh oh i dont want extreme scalability problems with my app either, i
better look into a better way of dealing with sessions
and to elaborate on the part about starting sessions in xwork
interceptors or servlet filters, if I were to start a session in an
interceptor or filter and stuff it into a
> currently in my daos i create a session object for every
> dao operation like dao.save dao.load, etc
I think this is exactly what caused the freeroller application (using
Hibernate also) to suffer some extreme scalability failures.
As far as best practices go, Jason has started Conductor that
this is exactly how im doing things with hibernate aswell, a few things
I can think of is putting the hibernate session creation code in a
servlet filter or xwork interceptor but thats going to cause some
problems anyways if the session were to be put in a un-usable state
somewhere in your code
30 matches
Mail list logo
