Hi Andrew,
Your decision to opt for build-time enhancement is the right choice. The
wrinkles around the mechanics of bytecode enhancement process is the
responsibility of OpenJPA team. And we perhaps havn't done a good job of it
from a usability point of view. Moreover, we have introduced several
alternatives that can bypass bytecode enhancement at build time. However,
these mechanics often carry forward edge errors that manifest as runtime
errors and are difficult to track.
Here are few suggestions. Please add our perspectives
a) emphasize the import of bytecode enhancement at build time in our
document. The XML
b) make the mechanics more accessible -- they exist but are hard to
find
c) block or at least inhibit other modes such that the developer can
do the right thing and not get tangled in a weave at runtime.
-----
Pinaki Poddar
Chair, Apache OpenJPA Project
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Problems-with-load-time-enhancement-and-Spring-s-TomcatInstrumentableClassLoader-tp6554347p6577479.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
