• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Won't Fix
  • DSO:L1
  • hhuynh
  • Reporter: steve
  • April 26, 2006
  • 0
  • Watchers: 1
  • June 11, 2007
  • June 08, 2007

Description

We now auto-lock the world, which has the side effect of auto-locking boot-jar classes. Is this what we want? should we seperate the concepts?

Comments

Tim Eck 2006-09-19

I’m not aware of a highly negative impact, but of course it can be problematic (from a performance point of view) to overly autolock.

If anyone cares to make a call about whether we should split out the locking section to have sections applicable in different contexts (ie. boot jar class, non boot-jar class, or both)….then I don’t think it would be too much work to do. In my opinion, this is just going to add perceived complexity, require more docs and testing and such, which until we know we have a problem seems slightly foolish

Fiona OShea 2007-05-30

verify that this has been resolved and has a test/test case

Hung Huynh 2007-06-06

there hasn’t any action/comment for this issue to close

Fiona OShea 2007-06-08

There is a new bug with more information and this should be addressed in Ortega