geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-5451) JPA table generation fails on JTA datasources
Date Sat, 17 Jul 2010 19:26:49 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889531#action_12889531
] 

David Jencks commented on GERONIMO-5451:
----------------------------------------

My experience is that jpa + derby _only_ works if you have _both_ a jta-datasource and a non-jta-datasource
and they are really transactional and non-transactional (i.e. the non-jta-datasource is set
up with no-transactions).  If not, there are a lot of operations besides DDL statements that
just don't work.  Do you have both configured?

> JPA table generation fails on JTA datasources
> ---------------------------------------------
>
>                 Key: GERONIMO-5451
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5451
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.1.5, 2.1.6
>         Environment: Vista using current Java 1.6 and embedded Derby
>            Reporter: Knut-HÃ¥vard Aksnes
>
> I am calling a number of JPA beans from a local Web service implemented via JAX-WS annotations
and  Stateless Session Bean.
> Table creation fails due to some operations during table creation being run outside a
transaction context.
>  
> Workaround:
> First set up the Database Pool and persistence.xml to use a Local(Non JTA) setup. Table
creation will succeed, but the rest of my code will fail.
> Then uninstalling my EAR and removing the DBPool, but keeping the Local Derby database.
> Then creating new JTA enabled DB pool for the same underlaying database, fixing the persistence.xml,
rebuild the EAR, and reinstall.
> As this has to be done everytime OpenJPA needs to update tables this is a major hassle
during development.
> If the workaround hadn't required so much work this would have been a minor bug.

-- 
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