I kept digging and found the answer to my problem. The kicker was my move to Eclipse Ganymede and loss of my previous running configurations that included the -javaagent for instrumenting my classes before the unit tests ran. It probably mattered because Account has a lazy 1:1 reference to itself, and my test indirectly updated that lazy reference.
This might have been combined with moving to Java 1.6 as well, since the chapter on enhancement suggests that OpenJPA tries to cope with having no enhancer in Java 1.6 by using runtime class retransformation. I've already uninstalled Java 1.5 off my system, or I'd try my test on 1.5 with no javaagent to see if the behaviour is specific to 1.6. It's plausible that there -could- be a problem with class retransformation. Nick 2008/7/27 Nicklas Johnson <[EMAIL PROTECTED]> > Though it isn't clear what might have changed with my code or dependencies, > I've started observing strange "caching"-like behavior, even if I disable > the query and data caches. I've changed a few things recently... going to > JDK 1.6, updating to a newer version of Wicket (and along with that its > dependencies), etc. I don't think the problem is related to my updating to > OpenJPA 1.1.0, since I tried downgrading back to 1.0.1 and still saw the > same behaviour. > [snip] > -- "Courage isn't just a matter of not being frightened, you know. It's being afraid and doing what you have to do anyway." -- Doctor Who - Planet of the Daleks This message has been brought to you by Nick Johnson 2.3b1 and the number 6. http://healerNick.com/ http://morons.org/ http://spatula.net/
