Prevent seam to increment EJB @Version field when we only read information

[guillaumebourgois]

Hi

I often have OptimisticLockException when we read web pages while an other application update the informations displayed through seam application (either on seam side or on the other application side).

The main reason seems to be the incrementation of our EJB @Version fields, each time we display/refresh a seam view.

When we never change the informations through thoses web pages, is there a way to prevent those @Version field incrementations ? (I do have some other pages with forms that requires proper increment of @Version to prevent data loss)

Best regards,

Guillaume Bourgois

Added some details : I speak about EJB @Version field and I need proper increment of those fields for the view with forms

[mkouba]

Hi Guillaume,

please provide some more information about the Seam application logic you suspect of version incrementations. By the way are you sure you only read information? E.g. when using Seam-managed persistence context and conversations, extended persistence context is automatically used by default and due to dirty checking even calling a setter on entity may fire an unwanted update...