RE: [Newsletter] Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

2018-05-15 Thread 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

RE: [Newsletter] Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

2018-05-14 Thread Shultz, Dmitry 
http://tomee.apache.org/datasource-config.html

'Alternatively, a DataSource can be declared via properties in the 
/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:rmannibu...@gmail.com] 
Sent: Monday, May 14, 2018 3:04 AM
To: users@tomee.apache.org
Subject: Re: [Newsletter] Re: [Newsletter] Re: Migration step of jtaManaged 
flag in context resources

Le lun. 14 mai 2018 09:56, <fabian-a.rich...@rohde-schwarz.com> a écrit :

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


> -Original Message-
> From: Romain Manni-Bucau <rmannibu...@gmail.com>
> Sent: Monday, May 14, 2018 10:52 AM
> To: users@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
>
> Le lun. 14 mai 2018 07:57, <fabian-a.rich...@rohde-schwarz.com> a écrit :
>
> > 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 <strub...@yahoo.de.INVALID>
> > Sent: Friday, May 11, 2018 10:27 AM
> > To: users@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
> >
> > > Am 09.05.2018 um 17:21 schrieb Romain Manni-Bucau 
> > ><rmannibu...@gmail.com
> > >:
> > >
> > > Hi
> > >
> > > Just use resources.xml
> > >
> > > Le mer. 9 mai 2018 14:05, <fabian-a.rich...@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  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  to Resource ID 
> > >> 'Default JDBC Database' from 'XXX
> > >>
> > >> org.apache.openejb.config.AutoConfig setNonJtaDataSource 
> > >> Adjusting PersistenceUnit Auditing  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
> > >>
> > >>
> > >>
> >
>

Re: [Newsletter] Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

2018-05-14 Thread Romain Manni-Bucau 
Le lun. 14 mai 2018 09:56, <fabian-a.rich...@rohde-schwarz.com> a écrit :

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


> -Original Message-
> From: Romain Manni-Bucau <rmannibu...@gmail.com>
> Sent: Monday, May 14, 2018 10:52 AM
> To: users@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
>
> Le lun. 14 mai 2018 07:57, <fabian-a.rich...@rohde-schwarz.com> a écrit :
>
> > 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 <strub...@yahoo.de.INVALID>
> > Sent: Friday, May 11, 2018 10:27 AM
> > To: users@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
> >
> > > Am 09.05.2018 um 17:21 schrieb Romain Manni-Bucau
> > ><rmannibu...@gmail.com
> > >:
> > >
> > > Hi
> > >
> > > Just use resources.xml
> > >
> > > Le mer. 9 mai 2018 14:05, <fabian-a.rich...@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  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  to Resource ID 'Default
> > >> JDBC Database' from 'XXX
> > >>
> > >> org.apache.openejb.config.AutoConfig setNonJtaDataSource Adjusting
> > >> PersistenceUnit Auditing  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
> > >>
> > >>
> > >>
> >
>

RE: [Newsletter] Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

2018-05-14 Thread fabian-a . richter 
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 <rmannibu...@gmail.com> 
Sent: Monday, May 14, 2018 10:52 AM
To: users@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

Le lun. 14 mai 2018 07:57, <fabian-a.rich...@rohde-schwarz.com> a écrit :

> 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 <strub...@yahoo.de.INVALID>
> Sent: Friday, May 11, 2018 10:27 AM
> To: users@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
>
> > Am 09.05.2018 um 17:21 schrieb Romain Manni-Bucau 
> ><rmannibu...@gmail.com
> >:
> >
> > Hi
> >
> > Just use resources.xml
> >
> > Le mer. 9 mai 2018 14:05, <fabian-a.rich...@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  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  to Resource ID 'Default 
> >> JDBC Database' from 'XXX
> >>
> >> org.apache.openejb.config.AutoConfig setNonJtaDataSource Adjusting 
> >> PersistenceUnit Auditing  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
> >>
> >>
> >>
>


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [Newsletter] Re: Migration step of jtaManaged flag in context resources

2018-05-14 Thread Romain Manni-Bucau 
Not portable but same as context.xml ;)

@DataSourceDefinition is not too :( - properties are not

Le lun. 14 mai 2018 07:57, <fabian-a.rich...@rohde-schwarz.com> a écrit :

> 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 <strub...@yahoo.de.INVALID>
> Sent: Friday, May 11, 2018 10:27 AM
> To: users@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
>
> > Am 09.05.2018 um 17:21 schrieb Romain Manni-Bucau <rmannibu...@gmail.com
> >:
> >
> > Hi
> >
> > Just use resources.xml
> >
> > Le mer. 9 mai 2018 14:05, <fabian-a.rich...@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  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  to Resource ID 'Default
> >> JDBC Database' from 'XXX
> >>
> >> org.apache.openejb.config.AutoConfig setNonJtaDataSource Adjusting
> >> PersistenceUnit Auditing  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
> >>
> >>
> >>
>

RE: [Newsletter] Re: Migration step of jtaManaged flag in context resources

2018-05-14 Thread fabian-a . richter 
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 <strub...@yahoo.de.INVALID> 
Sent: Friday, May 11, 2018 10:27 AM
To: users@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

> Am 09.05.2018 um 17:21 schrieb Romain Manni-Bucau <rmannibu...@gmail.com>:
> 
> Hi
> 
> Just use resources.xml
> 
> Le mer. 9 mai 2018 14:05, <fabian-a.rich...@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  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  to Resource ID 'Default 
>> JDBC Database' from 'XXX
>> 
>> org.apache.openejb.config.AutoConfig setNonJtaDataSource Adjusting 
>> PersistenceUnit Auditing  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
>> 
>> 
>> 


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Migration step of jtaManaged flag in context resources

2018-05-11 Thread Romain Manni-Bucau 
Le ven. 11 mai 2018 10:07, Mark Struberg  a
écrit :

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

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



> LieGrue,
> strub
>
>
> > Am 11.05.2018 um 10:37 schrieb Romain Manni-Bucau  >:
> >
> > Le ven. 11 mai 2018 09:27, Mark Struberg  a
> > écrit :
> >
> >> 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.
> >>
> >
> >
> > 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 ;)
> >
> >
> >> 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 <
> rmannibu...@gmail.com
> >>> :
> >>>
> >>> Hi
> >>>
> >>> Just use resources.xml
> >>>
> >>> Le mer. 9 mai 2018 14:05,  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
>   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  to Resource ID 'Default
> JDBC
>  Database' from 'XXX
> 
>  org.apache.openejb.config.AutoConfig setNonJtaDataSource Adjusting
>  PersistenceUnit Auditing  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
>
>

Re: Migration step of jtaManaged flag in context resources

2018-05-11 Thread 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


> Am 11.05.2018 um 10:37 schrieb Romain Manni-Bucau :
> 
> Le ven. 11 mai 2018 09:27, Mark Struberg  a
> écrit :
> 
>> 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.
>> 
> 
> 
> 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 ;)
> 
> 
>> 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
>>> 
>>> Le mer. 9 mai 2018 14:05,  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
  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  to Resource ID 'Default JDBC
 Database' from 'XXX
 
 org.apache.openejb.config.AutoConfig setNonJtaDataSource Adjusting
 PersistenceUnit Auditing  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

Re: Migration step of jtaManaged flag in context resources

2018-05-11 Thread Romain Manni-Bucau 
Le ven. 11 mai 2018 09:27, Mark Struberg  a
écrit :

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


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


> 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
> >
> > Le mer. 9 mai 2018 14:05,  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
> >>  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  to Resource ID 'Default JDBC
> >> Database' from 'XXX
> >>
> >> org.apache.openejb.config.AutoConfig setNonJtaDataSource Adjusting
> >> PersistenceUnit Auditing  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
> >>
> >>
> >>
>
>

Re: Migration step of jtaManaged flag in context resources

2018-05-11 Thread 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

> Am 09.05.2018 um 17:21 schrieb Romain Manni-Bucau :
> 
> Hi
> 
> Just use resources.xml
> 
> Le mer. 9 mai 2018 14:05,  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
>>  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  to Resource ID 'Default JDBC
>> Database' from 'XXX
>> 
>> org.apache.openejb.config.AutoConfig setNonJtaDataSource Adjusting
>> PersistenceUnit Auditing  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
>> 
>> 
>>

Re: Migration step of jtaManaged flag in context resources

2018-05-09 Thread Romain Manni-Bucau 
Hi

Just use resources.xml

Le mer. 9 mai 2018 14:05,  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
>  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  to Resource ID 'Default JDBC
> Database' from 'XXX
>
> org.apache.openejb.config.AutoConfig setNonJtaDataSource Adjusting
> PersistenceUnit Auditing  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
>
>
>