[jira] [Closed] (GERONIMO-5451) JPA table generation fails on JTA datasources

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

Mark Struberg closed GERONIMO-5451.
-----------------------------------
    Resolution: Won't Fix

Closing old outdated issues.

Note that the Apache Geronimo Application Server itself was declared EOL in 2017 and we do not maintain the server parts anymore.

We still do actively maintain many of the Java EE / Jakarta EE which saw the light during creation of the Apache Geronimo Aplication Server.
If you feel that this ticket still affects one of those components then please feel free to reopen the ticket.
thanks, your Apache Geronimo team!

> 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
>            Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)