tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: Migration step of jtaManaged flag in context resources
Date Wed, 09 May 2018 15:21:53 GMT
Hi

Just use resources.xml

Le mer. 9 mai 2018 14:05, <fabian-a.richter@rohde-schwarz.com> a écrit :

> Hi all,
>
>
>
> I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
> currently stuck with the following problem:
>
>
>
> We have DataSources defined in webapp’s META-INF/context.xml as Tomcat
> <Resource> and there _*was*_ a flag called jtaManaged which apparently
> doesn’t exist in Tomcat 8.5 anymore. Problem is our persistence units are
> still JTA managed, so what I see in the log is:
>
>
>
> org.apache.openejb.config.AutoConfig deploy Found matching datasource: XXX
> but this one is not a JTA datasource
>
>
>
> An hence TomEE does the following:
>
> org.apache.openejb.config.AutoConfig setJtaDataSource Adjusting
> PersistenceUnit Auditing <jta-data-source> to Resource ID 'Default JDBC
> Database' from 'XXX
>
> org.apache.openejb.config.AutoConfig setNonJtaDataSource Adjusting
> PersistenceUnit Auditing <non-jta-data-source> to Resource ID 'Default
> Unmanaged JDBC Database' from 'null'
>
>
>
> How can I define a DataSource inside context.xml which is still JTA
> managed? Or what is the correct way to migrate such a scenario? Wrapping it
> in JTADataSourceWrapperFacory?
>
>
>
> Thanks in advance and best
>
> Fabian
>
>
>

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