Announcement Announcement Module
No announcement yet.
Finer grained object versioning Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Finer grained object versioning

    I'm using the Spring OJB implementation with the PersistenceBrokerTemplate.

    Object A contains a Collection of Object B instances. When I change any of the instances of Object B contained within the Collection owned by Object A, and then store(myA), the version of A is incremented.

    This will cause problems for my implementation. If two users modify myA, but change different information (that is to say that the two objects can be saved sequentially without causing a collision), the way the versioning works will indicate that a collision has ocurred by throwing an Exception (likely a ConcurrencyFailureException).

    So, what I'd like to look into is a way to save/store Objects at the most fine grained level. Is there some way to store() such that only in the event of a collision will an Exception be thrown?