It looks like the strategy you've defined isn't being picked up on the annotation scan. If it were a problem related to loading your handler/strategy class, you see an exception from createEntityManager(). The most common cause is a missing OSGi bundle import. I've also seen cases where this issue is caused by having multiple copies of OpenJPA binaries in the environment, each being loaded by different classloaders. That can result in the @Strategy class being scanned by the runtime != @Strategy class used by the application. Beyond that, you might look into using the OSGi console, if possible, to determine whether your bundle is able to resolve the import.
-Jeremy On Fri, May 24, 2013 at 1:36 PM, rwheeler <rwhee...@novatusinc.com> wrote: > Sorry yes I am in OSGI enviroment. I do have > org.apache.openjpa.persistence.jdbc being imported. This is what I have > from my trace log for that particular field 39598 camel TRACE [Camel > (557-camel-32) thread #19 - timer://myTimer] openjpa.MetaData - "id" > has > mapping strategy > "org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy". > > > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/FieldStrategy-not-found-tp7584021p7584023.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
