You'll need to edit the server.config file to change the trace level for the package(s) you're interested in. There's some details on this in the user guide.
Originally Posted by marshallmccain
No, I believe that should be sufficient
I am using the context namespace configuration <context:load-time-weaver aspectj-weaving="on" />. Also, when not using lazy fetching, the transaction support is working as expected (I assume this also uses load-time-weaving since I configure it with <tx:annotation-driven mode="aspectj" />).
2.) To ensure that dependencies on com.springsource.org.eclipse.persistence are satisfied, I also use import-scope:=application. Is there any other subtle configuration that I need to make this work in an OSGi environment like dm Server?
dm Server plugs an OSGi-aware implementation of Spring's LoadTimeWeaver into your application context when you configure it to use load-time weaving which negates the need for the spring-agent.
3.) I tried modifying dm Server's startup to include a -javaagent:spring-agent.jar argument; however, my searches have indicated this is really not necessary. This change did not fix the error.
Let us know how you get on with the debug output and, if you're still having problems, we'll try to take a more detailed look.