Have you changed any transaction boundaries to take place in your
Controller? Transactions should begin in the service layer. I've seen
your problem happen when transactions are demarcated in the
FormController or an interceptor.
Matt
On Dec 14, 2007, at 1:22 PM, mavenj wrote:
I am using the appfuse spring mvc basic archetype. When I submit a
form to a
controller that extends BaseFormController, I find that hibernate
unexpectedly updates the command object before I call
xxxManager.save. In
fact, even when I don't call xxxManager.save the command object is
updated.
The update occurs right at the point in the FormController where I
making
use of a "Manager" (extends GenericManagerImpl, defined in
applicationContext.xml...) to "do" something necessary.
So, why does this happen? This behavior is undesirable in the case
where,
say, through some logic in the form, I don't want to update this
command
object, ultimately. Is there some spring or hibernate config I
need to do
to stop this behavior? Is hibernate or spring determining that
this object
has been changed and is there a "session" open on it and it needs
to be
updated/commited, and/or does it have to do with the dao or manager
impl
classes that extend GenericDaoHibernate or GenericManagerImpl?
--
View this message in context: http://www.nabble.com/Unexpected-
Command-Object-Update-in-FormController-tp14339780s2369p14339780.html
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
