Migration step of jtaManaged flag in context resources

[Mark Struberg]

Hi Fabian!


To give a bit more context:

Having actual db connections configured inside a WAR or EAR is usually something you'd rather like to avoid.
Having passwords checked in into your source repo, needing to recompile if you want to tweak the connection or credentials, etc
All that is simply not a really good idea.

This problem is imo best solved by separating off all configuration and kind of 'infrastructure' setup from your own appliaction source and provide it via the container.

TLDR; I recommend configuring DataSources and stuff in the container and not in your WAR: Just use /conf/tomee.xml [1].
And you can ofc also encrypt your passwords [2] so they are not stored in plain text.

LieGrue,
strub


[1] https://tomee.apache.org/configuring-datasources.html
[2] https://tomee.apache.org/datasource-password-encryption.html

Hi
Just use resources.xml

Hi all,
I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
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
org.apache.openejb.config.AutoConfig deploy Found matching datasource: XXX
but this one is not a JTA datasource
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

[Romain Manni-Bucau]

Post by Mark Struberg
Hi Fabian!
Having actual db connections configured inside a WAR or EAR is usually
something you'd rather like to avoid.
Having passwords checked in into your source repo, needing to recompile if
you want to tweak the connection or credentials, etc
All that is simply not a really good idea.
This problem is imo best solved by separating off all configuration and
kind of 'infrastructure' setup from your own appliaction source and provide
it via the container.
TLDR; I recommend configuring DataSources and stuff in the container and
not in your WAR: Just use /conf/tomee.xml [1].
And you can ofc also encrypt your passwords [2] so they are not stored in plain text.

Mark, dont forget you can use placeholders with default for all values in
the war but it hardcodes mandatory things like jtaManaged + exposes the
config as needed by the app and not the tomee way which can be undesired or
not consistent with the app way ;)

Post by Mark Struberg
LieGrue,
strub
[1] https://tomee.apache.org/configuring-datasources.html
[2] https://tomee.apache.org/datasource-password-encryption.html

Hi
Just use resources.xml

Hi all,
I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
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
XXX

but this one is not a JTA datasource
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

[Mark Struberg]

Do you remember (would have to look it up in the code) if the conf/tomee.xml overrides resource parameters defined in resources.xml from the WAR?

Kind of:
1.) pickup all values from resources.xml
2.) add/override values from resources defined in conf/tomee.xml

Does it work that way?

LieGrue,
strub

Post by Romain Manni-Bucau

Post by Mark Struberg
Hi Fabian!
Having actual db connections configured inside a WAR or EAR is usually
something you'd rather like to avoid.
Having passwords checked in into your source repo, needing to recompile if
you want to tweak the connection or credentials, etc
All that is simply not a really good idea.
This problem is imo best solved by separating off all configuration and
kind of 'infrastructure' setup from your own appliaction source and provide
it via the container.
TLDR; I recommend configuring DataSources and stuff in the container and
not in your WAR: Just use /conf/tomee.xml [1].
And you can ofc also encrypt your passwords [2] so they are not stored in plain text.

Mark, dont forget you can use placeholders with default for all values in
the war but it hardcodes mandatory things like jtaManaged + exposes the
config as needed by the app and not the tomee way which can be undesired or
not consistent with the app way ;)

Post by Mark Struberg
LieGrue,
strub
[1] https://tomee.apache.org/configuring-datasources.html
[2] https://tomee.apache.org/datasource-password-encryption.html

Hi
Just use resources.xml

Hi all,
I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
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
XXX

but this one is not a JTA datasource
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

[Romain Manni-Bucau]

Post by Mark Struberg
Do you remember (would have to look it up in the code) if the
conf/tomee.xml overrides resource parameters defined in resources.xml from
the WAR?
1.) pickup all values from resources.xml
2.) add/override values from resources defined in conf/tomee.xml
Does it work that way?

Resources.xml id are prefixed by the app name and lifecycle is managed by
the app but otherwise it is the exact same and there is no override just a
last one wins rules since override rules are handled at another layer
already (properties).

Post by Mark Struberg
LieGrue,
strub

Post by Romain Manni-Bucau

Post by Mark Struberg
Hi Fabian!
Having actual db connections configured inside a WAR or EAR is usually
something you'd rather like to avoid.
Having passwords checked in into your source repo, needing to recompile

if

Post by Romain Manni-Bucau

Post by Mark Struberg
you want to tweak the connection or credentials, etc
All that is simply not a really good idea.
This problem is imo best solved by separating off all configuration and
kind of 'infrastructure' setup from your own appliaction source and

provide

Post by Romain Manni-Bucau

Post by Mark Struberg
it via the container.
TLDR; I recommend configuring DataSources and stuff in the container and
not in your WAR: Just use /conf/tomee.xml [1].
And you can ofc also encrypt your passwords [2] so they are not stored

in

Post by Romain Manni-Bucau

Post by Mark Struberg
plain text.

Mark, dont forget you can use placeholders with default for all values in
the war but it hardcodes mandatory things like jtaManaged + exposes the
config as needed by the app and not the tomee way which can be undesired

or

Post by Romain Manni-Bucau
not consistent with the app way ;)

Post by Mark Struberg
LieGrue,
strub
[1] https://tomee.apache.org/configuring-datasources.html
[2] https://tomee.apache.org/datasource-password-encryption.html

Am 09.05.2018 um 17:21 schrieb Romain Manni-Bucau <
Hi
Just use resources.xml

Hi all,
I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
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
XXX

but this one is not a JTA datasource
org.apache.openejb.config.AutoConfig setJtaDataSource Adjusting
PersistenceUnit Auditing <jta-data-source> to Resource ID 'Default

JDBC

Post by Romain Manni-Bucau

Post by Mark Struberg

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

[f***@rohde-schwarz.com]

Hi Mark and Romain,

thanks for your replies!

Is the resources.xml approach a portable solution? E.g. if we want to support Wildfly in the future, which approach is the most portable? Tomee.conf doesn’t sound too portable :)

Thanks and best
Fabian

-----Original Message-----
From: Mark Struberg <***@yahoo.de.INVALID>
Sent: Friday, May 11, 2018 10:27 AM
To: ***@tomee.apache.org
Subject: *EXT* [Newsletter] Re: Migration step of jtaManaged flag in context resources

Hi Fabian!


To give a bit more context:

Having actual db connections configured inside a WAR or EAR is usually something you'd rather like to avoid.
Having passwords checked in into your source repo, needing to recompile if you want to tweak the connection or credentials, etc All that is simply not a really good idea.

This problem is imo best solved by separating off all configuration and kind of 'infrastructure' setup from your own appliaction source and provide it via the container.

TLDR; I recommend configuring DataSources and stuff in the container and not in your WAR: Just use /conf/tomee.xml [1].
And you can ofc also encrypt your passwords [2] so they are not stored in plain text.

LieGrue,
strub


[1] https://tomee.apache.org/configuring-datasources.html
[2] https://tomee.apache.org/datasource-password-encryption.html

Hi
Just use resources.xml

Hi all,
I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
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
org.apache.openejb.config.AutoConfig deploy Found matching
datasource: XXX but this one is not a JTA datasource
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

[Romain Manni-Bucau]

Not portable but same as context.xml ;)

@DataSourceDefinition is not too :( - properties are not

Post by f***@rohde-schwarz.com
Hi Mark and Romain,
thanks for your replies!
Is the resources.xml approach a portable solution? E.g. if we want to
support Wildfly in the future, which approach is the most portable?
Tomee.conf doesn’t sound too portable :)
Thanks and best
Fabian
-----Original Message-----
Sent: Friday, May 11, 2018 10:27 AM
Subject: *EXT* [Newsletter] Re: Migration step of jtaManaged flag in context resources
Hi Fabian!
Having actual db connections configured inside a WAR or EAR is usually
something you'd rather like to avoid.
Having passwords checked in into your source repo, needing to recompile if
you want to tweak the connection or credentials, etc All that is simply not
a really good idea.
This problem is imo best solved by separating off all configuration and
kind of 'infrastructure' setup from your own appliaction source and provide
it via the container.
TLDR; I recommend configuring DataSources and stuff in the container and
not in your WAR: Just use /conf/tomee.xml [1].
And you can ofc also encrypt your passwords [2] so they are not stored in plain text.
LieGrue,
strub
[1] https://tomee.apache.org/configuring-datasources.html
[2] https://tomee.apache.org/datasource-password-encryption.html

Hi
Just use resources.xml

Hi all,
I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
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
org.apache.openejb.config.AutoConfig deploy Found matching
datasource: XXX but this one is not a JTA datasource
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

[Mark Struberg]

Yup.

In my book the conf/tomee.xml is the most portable one.
Becaue here you clearly defer all infrastructure configuration to the container.
Of course for WildFly, Payara, etc the way how to configure the infrastructure is different. But the WAR will be perfectly portable in this case.

LieGrue,
strub

Post by Romain Manni-Bucau
Not portable but same as context.xml ;)
@DataSourceDefinition is not too :( - properties are not

Post by f***@rohde-schwarz.com
Hi Mark and Romain,
thanks for your replies!
Is the resources.xml approach a portable solution? E.g. if we want to
support Wildfly in the future, which approach is the most portable?
Tomee.conf doesn’t sound too portable :)
Thanks and best
Fabian
-----Original Message-----
Sent: Friday, May 11, 2018 10:27 AM
Subject: *EXT* [Newsletter] Re: Migration step of jtaManaged flag in context resources
Hi Fabian!
Having actual db connections configured inside a WAR or EAR is usually
something you'd rather like to avoid.
Having passwords checked in into your source repo, needing to recompile if
you want to tweak the connection or credentials, etc All that is simply not
a really good idea.
This problem is imo best solved by separating off all configuration and
kind of 'infrastructure' setup from your own appliaction source and provide
it via the container.
TLDR; I recommend configuring DataSources and stuff in the container and
not in your WAR: Just use /conf/tomee.xml [1].
And you can ofc also encrypt your passwords [2] so they are not stored in plain text.
LieGrue,
strub
[1] https://tomee.apache.org/configuring-datasources.html
[2] https://tomee.apache.org/datasource-password-encryption.html

Hi
Just use resources.xml

Hi all,
I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
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
org.apache.openejb.config.AutoConfig deploy Found matching
datasource: XXX but this one is not a JTA datasource
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

[f***@rohde-schwarz.com]

So bottom line: There is no portable DataSource definition technique as they are part of the container and hence container specific?

-----Original Message-----
From: Romain Manni-Bucau <***@gmail.com>
Sent: Monday, May 14, 2018 10:52 AM
To: ***@tomee.apache.org
Subject: *EXT* [Newsletter] Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

Not portable but same as context.xml ;)

@DataSourceDefinition is not too :( - properties are not

Post by f***@rohde-schwarz.com
Hi Mark and Romain,
thanks for your replies!
Is the resources.xml approach a portable solution? E.g. if we want to
support Wildfly in the future, which approach is the most portable?
Tomee.conf doesn’t sound too portable :)
Thanks and best
Fabian
-----Original Message-----
Sent: Friday, May 11, 2018 10:27 AM
Subject: *EXT* [Newsletter] Re: Migration step of jtaManaged flag in
context resources
Hi Fabian!
Having actual db connections configured inside a WAR or EAR is usually
something you'd rather like to avoid.
Having passwords checked in into your source repo, needing to
recompile if you want to tweak the connection or credentials, etc All
that is simply not a really good idea.
This problem is imo best solved by separating off all configuration
and kind of 'infrastructure' setup from your own appliaction source
and provide it via the container.
TLDR; I recommend configuring DataSources and stuff in the container
and not in your WAR: Just use /conf/tomee.xml [1].
And you can ofc also encrypt your passwords [2] so they are not stored
in plain text.
LieGrue,
strub
[1] https://tomee.apache.org/configuring-datasources.html
[2] https://tomee.apache.org/datasource-password-encryption.html

Am 09.05.2018 um 17:21 schrieb Romain Manni-Bucau
Hi
Just use resources.xml

Hi all,
I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
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
org.apache.openejb.config.AutoConfig deploy Found matching
datasource: XXX but this one is not a JTA datasource
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

[Romain Manni-Bucau]

Post by f***@rohde-schwarz.com
So bottom line: There is no portable DataSource definition technique as
they are part of the container and hence container specific?

Yes, portable solution is an app datasource which breaks the injection
pattern :(

Post by f***@rohde-schwarz.com
-----Original Message-----
Sent: Monday, May 14, 2018 10:52 AM
Subject: *EXT* [Newsletter] Re: [Newsletter] Re: Migration step of
jtaManaged flag in context resources
Not portable but same as context.xml ;)
@DataSourceDefinition is not too :( - properties are not

Post by f***@rohde-schwarz.com
Hi Mark and Romain,
thanks for your replies!
Is the resources.xml approach a portable solution? E.g. if we want to
support Wildfly in the future, which approach is the most portable?
Tomee.conf doesn’t sound too portable :)
Thanks and best
Fabian
-----Original Message-----
Sent: Friday, May 11, 2018 10:27 AM
Subject: *EXT* [Newsletter] Re: Migration step of jtaManaged flag in
context resources
Hi Fabian!
Having actual db connections configured inside a WAR or EAR is usually
something you'd rather like to avoid.
Having passwords checked in into your source repo, needing to
recompile if you want to tweak the connection or credentials, etc All
that is simply not a really good idea.
This problem is imo best solved by separating off all configuration
and kind of 'infrastructure' setup from your own appliaction source
and provide it via the container.
TLDR; I recommend configuring DataSources and stuff in the container
and not in your WAR: Just use /conf/tomee.xml [1].
And you can ofc also encrypt your passwords [2] so they are not stored
in plain text.
LieGrue,
strub
[1] https://tomee.apache.org/configuring-datasources.html
[2] https://tomee.apache.org/datasource-password-encryption.html

Am 09.05.2018 um 17:21 schrieb Romain Manni-Bucau
Hi
Just use resources.xml

Hi all,
I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
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
org.apache.openejb.config.AutoConfig deploy Found matching
datasource: XXX but this one is not a JTA datasource
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

[Shultz, Dmitry]

http://tomee.apache.org/datasource-config.html

'Alternatively, a DataSource can be declared via properties in the <tomee-home>/conf/system.properties file or via Java VirtualMachine -D properties. '

This is what I'm planning to use (Java VirtualMachine -D properties) in a K8 cluster, should satisfy the portability and also plays good with the K8's config maps.



-----Original Message-----
From: Romain Manni-Bucau [mailto:***@gmail.com]
Sent: Monday, May 14, 2018 3:04 AM
To: ***@tomee.apache.org
Subject: Re: [Newsletter] Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

Post by f***@rohde-schwarz.com
So bottom line: There is no portable DataSource definition technique
as they are part of the container and hence container specific?

Yes, portable solution is an app datasource which breaks the injection pattern :(

Post by f***@rohde-schwarz.com
-----Original Message-----
Sent: Monday, May 14, 2018 10:52 AM
Subject: *EXT* [Newsletter] Re: [Newsletter] Re: Migration step of
jtaManaged flag in context resources
Not portable but same as context.xml ;)
@DataSourceDefinition is not too :( - properties are not

Post by f***@rohde-schwarz.com
Hi Mark and Romain,
thanks for your replies!
Is the resources.xml approach a portable solution? E.g. if we want
to support Wildfly in the future, which approach is the most portable?
Tomee.conf doesn’t sound too portable :)
Thanks and best
Fabian
-----Original Message-----
Sent: Friday, May 11, 2018 10:27 AM
Subject: *EXT* [Newsletter] Re: Migration step of jtaManaged flag in
context resources
Hi Fabian!
Having actual db connections configured inside a WAR or EAR is
usually something you'd rather like to avoid.
Having passwords checked in into your source repo, needing to
recompile if you want to tweak the connection or credentials, etc
All that is simply not a really good idea.
This problem is imo best solved by separating off all configuration
and kind of 'infrastructure' setup from your own appliaction source
and provide it via the container.
TLDR; I recommend configuring DataSources and stuff in the container
and not in your WAR: Just use /conf/tomee.xml [1].
And you can ofc also encrypt your passwords [2] so they are not
stored in plain text.
LieGrue,
strub
[1] https://tomee.apache.org/configuring-datasources.html
[2] https://tomee.apache.org/datasource-password-encryption.html

Am 09.05.2018 um 17:21 schrieb Romain Manni-Bucau
Hi
Just use resources.xml

Hi all,
I haven been trying to migrate from TomEE 1.7.5 to 7.0.4 but I am
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
org.apache.openejb.config.AutoConfig deploy Found matching
datasource: XXX but this one is not a JTA datasource
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

[gilbertoca]

Hi Fabian,

This discussion[1] can help you a little more about standard way to use
data-source in Java EE containers.

Regards,

Gilberto

[1] https://stackoverflow.com/q/2279913/269514



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html