mike wrote: > > It looks like you may have a mis-match between the tutorial and the > version of AppFuse you are using. The tutorial is written for AppFuse > 1.9.4 which uses Spring 2.0 AOP interceptors for transaction management. > The configuration snippet you quote is from AppFuse > 1.9.3 or earlier which still uses the older Spring 1.2.8 > interceptors.</div> > > To get it all working with the older style AOP you will need to change the > definition of your personManager bean: > > <bean id="personManager" parent="txProxytemplate"> > <property name="target"> > <bean > class="org.appfuse.service.impl.PersonManagerImpl"> > > <property name="personDao" ref="personDao"/> > </bean> > > </property> > </bean> > > It's a bit more work, hence the attraction of the new way of doing things > in Spring 2.0! > > Mike. >
That was it! Thank you Mike! maskkkk wrote: > > Hello Appfuse crew, > > Initially upon following the tutorial in which a Person object was created > and edited, I could edit the various person objects in the database. > However now that I have re-checked the project out I recieve the following > error when editing/creating and saving (only) Person objects: > > > > > Data Access Failure > > Write operations are not allowed in read-only mode (FlushMode.NEVER) - > turn your Session into FlushMode.AUTO or remove 'readOnly' marker from > transaction definition > > > > > What could be causing this? (I'm new to Hibernate, it looks like maybe a > Hibernate error, or possibily something to do with the MySQL database.) > Oh and By the way I can edit user profiles without any trouble. > > Thank you, > (for making Appfuse, and helping with my questions) > Andrew J. Leer > -- View this message in context: http://www.nabble.com/Data-Access-Failure-tf2711868s2369.html#a7586077 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
