Expanding on what James said and following up on a hint given by Howard
in an earlier thread, I have been using the approach of injecting the
ASO into services using the following approach: 1) create a proxy object
that implements the same interface as the ASO, 2) the proxy is a
threaded/pooled
Yes, it would be most helpful if you could describe your solution using
hivetranse for the following issues:
1) session per request - my experience was that if I called one
transaction demarcated service method, and then another one, two
hibernate sessions were created, thus defeating the use
Ted,
I ran into this same problem. As far as I can tell, Hivetranse will not
reuse a single hibernate Session across multiple transactions. Normally
it will close the session after a transaction. If you use the
DeferSessionClose option, it will keep the session around, but still
create a new
I opened http://issues.apache.org/jira/browse/HIVEMIND-174 regarding the
inconsistency of an exception worded like a warning.
Jesse Kuhnert wrote:
Ok, even though I suggested posting over here (was in the middle of a
production push before), I have one ~guess~ answer that doesn't involve
lookin
Jean-Francois
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Mark Reynolds
Sent: Thursday, April 13, 2006 4:42 AM
To: tapestry-user@jakarta.apache.org
Subject: Re: Open Session in View - Tapestry
I tried the hivetranse approach, but had 2 problems. 1) hivetran
The problem I experienced using hivetranse and the "open session in
view" was this:
1) execute one transactional method, transaction is committed when the
method returns and the hibernate session is kept open
2) execute another transactional method, hivetranse opens a second
hibernate session,
So how does transaction demarcation work in this common tapestry sequence:
1) in pageBeginRender(), call a service method to load the persisted
object and set it as a simple page property
2) tapestry form fields components then update the properties of the
persisted object and call some validat
I tried the hivetranse approach, but had 2 problems. 1) hivetranse seems
to limit a hibernate session to a single transaction, and 2) its
declarative approach ultimately limits the transaction demarcation to a
single method call, and I couldn't figure out a good way to structure my
application
t way, but it works.
Filip S. Adamsen wrote:
How about using IRequestCycle#forgetPage?
http://jakarta.apache.org/tapestry/tapestry/apidocs/org/apache/tapestry/IRequestCycle.html#forgetPage(java.lang.String)
-Filip
Mark Reynolds skrev:
I tried .clear(), but that didn't work.
I tried
nDelegate#clear and
then recording your error. That might work as well.
http://jakarta.apache.org/tapestry/tapestry/apidocs/org/apache/tapestry/valid/IValidationDelegate.html#clear()
If none of it works, well, then I blame it on lack of coffee - it's well
beyond midnight here. ; )
-Fili
I have a page with a form for editing an object. I am using optimistic
locking. I catch the optimistic lock exception in the listener method
and add a message to the validation delegate indicating that another
user changed the record. In this case, I want to have the form show the
current value
11 matches
Mail list logo
