Nicklas Karlsson [https://community.jboss.org/people/nickarls] created the discussion "Re: Readonly transactions in session beans" To view the discussion, visit: https://community.jboss.org/message/787595#787595 -------------------------------------------------------------- Are you talking about something like an EJB with a NOT_SUPPORTED transaction attribute? Or a non-transactional datasource? -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/787595#787595] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Nicklas Karlsson [https://community.jboss.org/people/nickarls] created the discussion "Re: Readonly transactions in session beans" To view the discussion, visit: https://community.jboss.org/message/788701#788701 -------------------------------------------------------------- If you're using Hibernate, I think it has the concept of Session.setDefaultReadOnly(true); -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/788701#788701] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Lukasz Szymik [https://community.jboss.org/people/lszymik] created the discussion "Re: Readonly transactions in session beans" To view the discussion, visit: https://community.jboss.org/message/788709#788709 -------------------------------------------------------------- I read article about transaction pitfalls. It is very interesting. So far I know that JPA2 does not support it directly and Hibernate Session could be used directly. I have real life scenarion where it is lot of I18N messages stored in database and there is stateless session bean which is providing method: getMessage(int id). The getMessage method is annotated with TransactionAttribute(REQUIRED) so read is executed inside transaction. The messages are rarely changed so I started to look for optimalizations. Springs developers told me to use transaction - read only. However now I am little bit confused. Maybe removing transaction from getMessage method will be better solution. Thanks for valueble information. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/788709#788709] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Stephen Coy [https://community.jboss.org/people/sfcoy] created the discussion "Re: Readonly transactions in session beans" To view the discussion, visit: https://community.jboss.org/message/788674#788674 -------------------------------------------------------------- JBoss does not explicitly support this notion. The fact is is that Spring Framework read-only transactions are poorly understood by developers that use it and it rarely does what you expect. See http://www.ibm.com/developerworks/java/library/j-ts1/index.html Transaction strategies: Understanding transaction pitfalls for more information. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/788674#788674] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]