Hi

I assume Christian has not seen my comment [1] yet so why I put the same
question here if there's any good reason *today* (in contrast to 2007) to
enhance/weave the byte-code of camel-jpa's own JPA entities:

org.apache.camel.processor.interceptor.jpa.JpaTraceEventMessage
org.apache.camel.processor.idempotent.jpa.MessageProcessed

*specific* for OpenJPA?

And IMHO for the camel-jpa's own unit-tests we should give a try in dynamic
weaving [2] supported since openjpa 2.x. The other option could be also to
move to Hibernate-EntityManager and what not which perfectly can weave
dynamically at runtime.

Any thoughts?

Babak

[1] https://issues.apache.org/jira/browse/CAMEL-5044
[2] https://issues.apache.org/jira/browse/OPENJPA-952


--
View this message in context: 
http://camel.465427.n5.nabble.com/Thoughts-about-camel-example-tracer-which-is-currently-broken-tp5713377.html
Sent from the Camel Development mailing list archive at Nabble.com.

Reply via email to