I guess you want to hide user, password, connection, schema etc.
You could use variable replacement with ${} and pack the file in the jar and
then just set the properties to replace like Romain mentioned. I think it
should work,
Cheers,
Roberto
> On 22 Nov 2018, at 05:42, Romain Manni-Bucau <[email protected]> wrote:
>
> Hello,
>
> You can always load system properties in setenv.sh before the server starts.
>
> If it is properties settable after tomee.xml is read you can set them in it
> and it supports <Import path=.... />
>
> Finally you can always plug a tomcat listener before tomee one and set the
> system properties the way you want peogrammatically.
>
> Le mer. 21 nov. 2018 23:51, exabrial12 <[email protected]> a écrit :
>
>> We want to store the configuration for our datasources separate from the
>> distribution of the one-jar. If you haven't seen Jonathan [Gallimore's]
>> excellent blog post on configuration TomEE, see here:
>> https://www.tomitribe.com/blog/tomee-configuration-techniques/
>>
>> Looking at the TomEE plugin's options though, it allows you to include a
>> system.properties at build time, but I can't seem to find a way to set it
>> at
>> runtime.
>>
>> Any ideas or alternatives?
>>
>>
>>
>> --
>> Sent from:
>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>>
