I guess it is related to how SEAM handles transactios. I'm using Seam POJOs.
The EntityQuery's getResultSet() method is marked @transactional. Call to
getResultSet() commits changes made to Client entity on the jsf form get committed to the
database.
Anyone knows why getResultSet() first committed changes to queried Entity. and how I can
avoid it in my case?
I guess it's a common issue, I can't find solution since this is my first attempt
on such scenarion.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106585#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...