o save the modifications, you can call saveOrUpdate() or merge.
Regards,
Kedar
-Original Message-
From: Toni Lyytikäinen [mailto:[EMAIL PROTECTED]
Sent: Friday, February 29, 2008 6:19 PM
To: Struts Users Mailing List
Subject: Re: persistence and doubts on usage of hibernate in struts 2
H
Hard to say where the problem lies without having a look at the DAO code.
Are you using OpenSessionInViewFilter or similar mechanism for lazy loading
in the view? If yes, try setting the param singleSession to false like this:
OSIVFilter
org.springframework.orm.hibernate3.support.OpenSessionI
OK I found what I am looking for, but I am missing something.
Basically I need to be able to post back to an action. How do I check if
the request is post back or not.
Mansour wrote:
hello every one:
I am having a look at hibernate and I think it's neat. however, is
there away to temporary
hibernate is great for autopopulating classes from DB tables identified from
hibernate.properties
watch their treatment of collection classes especially with lazy=true where
classes are not initialized until the last possible moment..
(One of those features that needs to be tuned)
M-
---
There is no persistence layer as part of Struts. For that, you must rely on
an external package.
That said, Struts integrates very well with Hibernate (or with Hibernate +
Spring).
2007/1/31, jlp86 <[EMAIL PROTECTED]>:
Hello all - I'm new to Java Web development/Struts, and was wondering if
Hi Jan
Yes, this is what I'm doing. This solution (including html:hidden for these
fields) does
raise the potential for problems, for example, when I now add a new variable to
my
databases / form-bean I have to manually check through all of the JSP files
that use
this form-bean and ensure
Why not put the ID as a hidden field on the form too, so you SAVE action can
read it from the request and update the record with the ID ? It's not hard at
all.
J
On Mon, 12 Sep 2005 13:48:45 +1000
"Murray Collingwood" <[EMAIL PROTECTED]> wrote:
> Hi folks
>
> Getting back to some operational
There has been an interesting shift lately with people more apt to put
things in session. I think a lot of it stems from what newer frameworks
are doing and people taking some cues from them. There are certainly
some obvious advantages, and the old disadvantages aren't nearly as big
a deal as
Two responses and both suggesting I push all my beans into the session scope.
This really does beg the question, what purpose is the request scope for a
bean? My
only answer was display-only material. Is this really how it was designed?
Sorry to be asking so many design questions but I reall
On 9/11/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> From: "Murray Collingwood" <[EMAIL PROTECTED]>
>
> > I guess pushing the form bean into the session would do this, but session
> > variables for a
> > request level function is probably not recommended.
>
> It is by me. :) Put the form in sess
From: "Murray Collingwood" <[EMAIL PROTECTED]>
I guess pushing the form bean into the session would do this, but session
variables for a
request level function is probably not recommended.
It is by me. :) Put the form in session scope, and most of your problems
will disappear. You pick up
11 matches
Mail list logo
