castor

Omit multiple initialization of objectInTx in LockEngine.load

Details

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

Description

In LockEngine.load, if the object is extended, then the objectInTx will be initialized twice.

Activity

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

In this patch, I'll initialize the object after the concrete class is known.

Show
Wensheng Dou added a comment - In this patch, I'll initialize the object after the concrete class is known.
Hide
Permalink
Ralf Joachim added a comment -

Very good work. Patch commited as is.

Show
Ralf Joachim added a comment - Very good work. Patch commited as is.

People

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

Dates

  • Created:
    Updated:
    Resolved: