you can use :
then to get the property at runtime try to use coherence mbeans api
if it is not avaliable in mbeans api you can use also a system property -Dmycustomproperty=10s
thanks for the answer.
Actually I need a default value which can be overriden at runtime as described in the documentation
This is very handy to move conifguration items outside the cache-config.
Do you know why the xml woul dnot validate when system-property is used in the write-delay?
<?xml version="1.0" encoding="UTF-8"?>
Coherence accepts it (when we force no xml validation (removing the xmlns)).
But I would like to use the xml validation to avoid miss-configurations.
Because Coherence's xsd file define that "write-delay" doesn't accept system-property attribute. There is nothing you can do for that unless you have your own customized coherence-cache-config.xsd or have Oracle change it on future release.
yes that's for sure (the xml validation is failing because the xsd doesn't allow that attribute).
But the documentation is saying the opposite.
So is this just a bug in the version (3.7.1) I'm using
or just the wrong xsd I'm pointing at.
or something else?
Maybe someone from Coherence staff can help?
Could you try without the "-"
<write-delay system-property="myproperty.override.writedelay" >10s</write-delay>
And then use: -Dmyproperty.override.writedelay=5
Hi Leo_TA, changing "-" to "." in the property name won't chnage the validation failure.