According to the advice from
http://openjpa.208410.n2.nabble.com/openjpa-javaagent-enhancement-with-tomcat-td5029993.html
this thread I switched to build-time enhancement, and it worked for me.
--
View this message in context:
http://old.nabble.com/Tomcat-and-openjpa-javaagent-tp28506406p28517
Well, I set openjpa-all-2.0.0.jar as javaagent, and all startup exceptions
are gone. Still there is no runtime optimization available, an exeption is
being throwed when accessing the database:
Caused by:
org.apache.openjpa.persistence.ArgumentException: This configuration
disallows runtime opti
geronumolibs need a jee container to function otherwise the classes will
never be instantiated. Use hibernate as a possible workaround
--
From: "n0weak"
Sent: Monday, May 10, 2010 11:57 AM
To:
Subject: RE: Tomcat and openjpa javaage
On 10/05/2010 10:57, n0weak wrote:
>
>> Try putting that jar into Tomcat's bin directory instead. It must be
> available to the system classloader, not Tomcat's common classloader.
>
> This had no effect. Tomcat in startup script sets the CLASSPATH variable to
> "$CATALINA_HOME"/bin/bootstrap.ja
> Try putting that jar into Tomcat's bin directory instead. It must be
available to the system classloader, not Tomcat's common classloader.
This had no effect. Tomcat in startup script sets the CLASSPATH variable to
"$CATALINA_HOME"/bin/bootstrap.jar, so i tried to modify it in catalina.sh
to "
> From: n0weak [mailto:n0w...@gmail.com]
> Subject: Tomcat and openjpa javaagent
>
> and also put commons-lang-2.3.jar into tomcat lib directory.
Try putting that jar into Tomcat's bin directory instead. It must be available
to the system classloader, not Tomcat's common classloader.
> But sti
