> For example, in Maverick, apparently, your controller may
> recieve a discard() callback when "when the views are
> finished and the model is discarded". I'm not sure of the
> details since I've never used maverick.
It works as you described. When maveric renders a view it executes
following cod
t: Friday, November 08, 2002 11:21 AM
Subject: Re: [OS-webwork] Callback after view is rendered
> Hi,
>
> > A few people have suggested using a filter to handle the hibernate
> > session. It probably wouldn't be a bad idea to see such a filter in
> > the source for h
To avoid slurping up the whole database when we retrieve a single object,
associations must support lazy initialization. This is usually referred to
as "faults" though I've never figured out exactly where that term comes
from. So an object returned by Hibernate might really just be a dynamic
CGLIB
ot; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 09, 2002 11:19 AM
Subject: Re: [OS-webwork] Callback after view is rendered
> Yep, I like that option :)
>
> Errors occurring in the JSP would also have to point to RollbackTx.
>
> - Original Mess
riday, November 08, 2002 4:19 PM
Subject: Re: [OS-webwork] Callback after view is rendered
> Yep, I like that option :)
>
> Errors occurring in the JSP would also have to point to RollbackTx.
>
> - Original Message -
> From: "Patrick Lightbody" <[EMAIL PROT
Gavin,
I recommend that you try the filter approach. You could solve your
transaction boundary problem for all your Hibernate users doing webapps
at once. Someone could be doing something as primitive as a
servlet+jsp w/ scriptlets and you would still have them covered. I'm
not sure, but Si
Yep, I like that option :)
Errors occurring in the JSP would also have to point to RollbackTx.
- Original Message -
From: "Patrick Lightbody" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 09, 2002 11:12 AM
Subject: Re: [OS-webwork] Callback
gt; ensure that transactions get committed / rolled back.
>
> - Original Message -
> From: "James Cook" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, November 09, 2002 5:11 AM
> Subject: RE: [OS-webwork] Callback after view is rende
ginal Message -
From: "James Cook" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 09, 2002 5:11 AM
Subject: RE: [OS-webwork] Callback after view is rendered
> I agree with the filter approach, however an unsophisticated technique
that
> can be app
> Hm, shouldn't transactions last only as short as possible? We are using a
> system where the transaction is opened and closed in a wrapper for the
> execute() method, but I always thought this is a design flaw ... ?
I would have thought that in most applications, the time spent processing a
user
callbacks.
...
<% someCallback() %>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:opensymphony-webwork-admin@;lists.sourceforge.net]On Behalf Of
> Gavin King
> Sent: Friday, November 08, 2002 7:07 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webw
Hi,
> A few people have suggested using a filter to handle the hibernate
> session. It probably wouldn't be a bad idea to see such a filter in
> the source for hibernate users. Any contributors?
Hm, shouldn't transactions last only as short as possible? We are using a
system where the transaction
>
> Hav you tried using a servlet filter for this?
>
> /Rickard
I havn't tried anything at all. I am mainly asking for a recommended "best"
approach that I can add to our doco. If thats the best approach, I will
write that :)
Thanks Rickard.
---
A few people have suggested using a filter to handle the hibernate
session. It probably wouldn't be a bad idea to see such a filter in the
source for hibernate users. Any contributors?
Callbacks are another feature that would be trivial to handle given the
"views aren't terminal" idea that, um, pr
Gavin King wrote:
Is there some feature of WebWork that allows an application to perform
some
cleanup code after rendering a view? Many of our users need some way to
close/commit the Hibernate session/transaction *after* the view is
rendered.
The reason for this is that Hibernate might return l
Is there some feature of WebWork that allows an application to perform some
cleanup code after rendering a view? Many of our users need some way to
close/commit the Hibernate session/transaction *after* the view is rendered.
The reason for this is that Hibernate might return lazy-initializing proxi
16 matches
Mail list logo
