camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-1552) Provide declarative transaction handling for the JPA component
Date Wed, 29 Apr 2009 06:26:39 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-1552.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.6.1

trunk: 769673
1.x: 769677.

Frank let me know how it goes for you. Mind that setting JPA in a managed environment to use
a JTA TM might take a bit time to get working.

I also changed the JpaProducer to use {{merge}} instead of {{persist}} so it can do updates.

> Provide declarative transaction handling for the JPA component
> --------------------------------------------------------------
>
>                 Key: CAMEL-1552
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1552
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-jpa
>    Affects Versions: 2.0-M1
>            Reporter: Frank Schwarz
>            Assignee: Claus Ibsen
>             Fix For: 1.6.1, 2.0.0
>
>
> The JPA component uses currently a hard coded reference to org.springframework.orm.jpa.JpaTransactionManager.
A more flexible (i.e. declarative) handling would be desirable.
> See also: http://www.nabble.com/Re%3A-JPA-component-in-a-JEE5-environment-p23154746s22882.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message