camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <christian.muel...@gmail.com>
Subject Re: Thoughts about camel-example-tracer which is currently broken
Date Wed, 23 May 2012 20:22:08 GMT
Fixed!

Thanks again,
Christian

On Wed, May 23, 2012 at 9:29 PM, Christian Müller <
christian.mueller@gmail.com> wrote:

> Hello Babak,
>
> thanks for pointing this out. I had to "manage" some private things in the
> last weeks (similar to the one you had to "manage" when we meet in
> Zurich)...
>
> We do not want force our users to use OpenJPA if they are familiar with
> other JPA providers. It's simply an issue introduced by myself. I will have
> a look on it.
>
> Thanks,
> Christian
>
>
> On Wed, May 23, 2012 at 1:32 PM, Babak Vahdat <babak.vahdat@swissonline.ch
> > wrote:
>
>> 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.
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message