Hi, Yeah, I didn't fix the problem, I just made it a warning. We probably need to do some ClassLoader experimentation to figure out why the PersistenceCapable check is failing.
-Patrick On 8/22/07, Prashant Bhat <[EMAIL PROTECTED]> wrote: > Hi, > > Thanks, It's working now with openjpa.RuntimeUnenhancedClasses set to warn. > and the best thing is even the performance is same as before. But > surprisingly, although entities are enhanced, the following message still > comes. > > openjpa.Enhance - This configuration disallows runtime optimization, but the > following listed types were not enhanced at build time or at class load time > with a javaagent: [...] > > And if I set openjpa.RuntimeUnenhancedClasses set to unsupported, then an > exception is thrown. > > Actually, I'm running the application in a multi-classloader > environment(with JPF and plugin arch), so different related entities(and > super-classes also) are in different classloader but all of them are > available in Thread.contextClassLoader. > Could this be causing the error? > > Thanks, > Prashant. > > On 8/23/07, Patrick Linskey <[EMAIL PROTECTED]> wrote: > > > > ClassLoadEnhancement and RuntimeRedefinition are options for the > > javaagent specification: > > > > java -javaagent:openjpa.jar=RuntimeRedefinition=true > > ,ClassLoadEnhancement=false > > ... > > > > openjpa.RuntimeUnenhancedClasses is a configuration option with three > > possible options: supported, unsupported, and warn. > > > > When RuntimeUnenhancedClasses is set to unsupported or warn, the > > developer must either run the enhancer or use the javaagent with > > ClassLoadEnhancement=true (the default). This is the same as the > > OpenJPA behavior two months ago. > > > > When RuntimeUnenhancedClasses is set to supported, OpenJPA can be used > > without running the enhnacer or specifying a javaagent. > > > > -Patrick > > > -- Patrick Linskey 202 669 5907
