Hello,

a while ago we discussed the (still undocumented; see
https://issues.apache.org/jira/browse/OPENJPA-650 !)
openjpa.RuntimeUnenhancedClasses configuration in this list.

A question: On Java6, according to
http://openjpa.apache.org/builds/latest/docs/manual/ref_guide_pc_enhance
.html#ref_guide_pc_enhance_unenhanced_types, "OpenJPA will attempt to
dynamically register a ClassTransformer that will redefine your
persistent classes on the fly to track access to persistent data"
without specifying a javaagent. However, with
openjpa.RuntimeUnenhancedClasses=unsupported it still says
"org.apache.openjpa.persistence.ArgumentException: This configuration
disallows runtime optimization, but the following listed types were not
enhanced at build time or at class load time with a javaagent: ..." -
isn't this inconsistent / wrong?

It would be useful to have a possibility / configuration option which
PREVENTS users from running OpenJPA with that stupid (useless) "runtime
enhancement", and makes them specify the javaagent under Java5 (that's
what openjpa.RuntimeUnenhancedClasses=unsupported does, works well), but
which when you're running under Java6 does not abort and uses that
dynamic ClassTransformer. For now I'm doing if
(System.getProperty("java.version").startsWith("1.5")) {
p.setProperty("openjpa.RuntimeUnenhancedClasses", "unsupported"); } and
that works ;-), but IMHO it would make sense to extend the
RuntimeUnenhancedClasses related check inside OpenJPA with something
like this? JIRA?

Thanks & Regards,
Michael


____________________________________________________________

• This email and any files transmitted with it are CONFIDENTIAL and intended
solely for the use of the individual or entity to which they are addressed.
• Any unauthorized copying, disclosure, or distribution of the material within
this email is strictly forbidden.
• Any views or opinions presented within this e-mail are solely those of the
author and do not necessarily represent those of Odyssey Financial
Technologies SA unless otherwise specifically stated.
• An electronic message is not binding on its sender. Any message referring to
a binding engagement must be confirmed in writing and duly signed.
• If you have received this email in error, please notify the sender immediately
and delete the original.