geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut-Håvard Aksnes (JIRA) <j...@apache.org>
Subject [jira] Commented: (GERONIMO-5451) JPA table generation fails on JTA datasources
Date Mon, 19 Jul 2010 13:06:13 GMT

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

Knut-Håvard Aksnes commented on GERONIMO-5451:
----------------------------------------------

My workaround seems to work on 2.1.6 but not on 2.1.5. 
I don't have both set up at the same time. I am really only interested in using JTA. The switching
trick works, but is ugly.The project I am working on are at a fairly early stage and Derby
is likely to be switched to some kind of enterprise database platform before deployment, but
Embedded Derby is nice "If it works" during development as it is low overhead and "Zero config".
The production database is likely to be running on SqlServer or Oracle depending on where
we decide to deploy.

> 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