It's in the same package as any other manager, which is a subpackage of
a "service"-package. Because it's working for all other managers in the
package, I guess it's working "normally".

Kind regards,
Tobias

> -----Original Message-----
> From: Matt Raible [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, February 12, 2008 3:56 PM
> To: [email protected]
> Subject: Re: [appfuse-user] OpenSessionInViewFilter and 
> Hibernate cascades
> 
> Is your Manager interface in a "service" package? If so, it should
> work. If it doesn't, adding @Transactional sounds like an easy
> workaround.
> 
> Matt
> 
> On 2/12/08, Tobias Vogel <[EMAIL PROTECTED]> wrote:
> > Hi list,
> >
> > I'm fiddling around with the lazyLoadingFilter 
> (OpenSessionInViewFilter)
> > in AppFuse 2.x a little. The base AppFuse files already contain the
> > right aop-config, to mark any manager as transactional, so 
> basically no
> > problem.
> >
> > If I enable the lazyLoadingFilter for my webapp and call the
> > save()-method of a certain manager, I get the following exception:
> > org.springframework.dao.InvalidDataAccessApiUsageException: Write
> > operations are not allowed in read-only mode 
> (FlushMode.NEVER/MANUAL):
> > Turn your Session into FlushMode.COMMIT/AUTO or remove 
> 'readOnly' marker
> > from transaction definition.
> >
> > All other managers still work flawlessly, the only 
> difference between
> > them is, that this particular one saves a model object with cascades
> > defined. If I add a "@Transactional" annotation the manager 
> class, the
> > problem goes away, too. I just don't see the logic behind 
> this, as all
> > managers should get marked as transactional due to the 
> "managerTx" from
> > AppFuse anyway.
> >
> > Does anyone have a good explanation for this behaviour and 
> probably some
> > additional comments/workarounds/solutions?
> >
> > Kind regards,
> > Tobias
> >
> > 
> ---------------------------------------------------------------------
> > 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]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to