castor

change of OID meaning

Details

  • Type: Sub-task Sub-task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.3.3rc1
  • Component/s: JDO
  • Labels:
    None
  • Number of attachments :
    1

Description

In current implementation, both the extended object and superclass object will have one oid for one instance, so more than one oid and lock will be created when loading an extended object. This cause the usage of 'synchronized (basemolder)'.
In this issues, I'll make it unique for one instance. Then one instance just has one oid, and just one lock (no matter extended or not).

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Wensheng Dou added a comment -

This patch makes oid unique for one instance. Then one instance just has one oid, and just one lock (no matter extended or not).

Show
Wensheng Dou added a comment - This patch makes oid unique for one instance. Then one instance just has one oid, and just one lock (no matter extended or not).
Hide
Permalink
Ralf Joachim added a comment -

Committed patch as is with cpactf test04 enabled again

Show
Ralf Joachim added a comment - Committed patch as is with cpactf test04 enabled again

People

  • Assignee:
    Wensheng Dou
    Reporter:
    Wensheng Dou
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: