yes, have to admit I don't recall out of my mind but if not we need to fix it.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-12-01 23:01 GMT+01:00 Violeta Georgieva <[email protected]>: > You gave me an idea: > Can I declare <Resource id="..." properties-provider="MyPropertiesProvider" > /> in resources.xml and still supply configuration with the properties > provider? > > > Romain Manni-Bucau wrote > > Ok, did you try using placeholders in resources.xml (${my.driver} and > > my.driver=... in conf/system.properties)? This sounds the easiest. > > > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <http://rmannibucau.wordpress.com> | Github > > <https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > > <http://www.tomitribe.com> > > > > 2015-12-01 22:36 GMT+01:00 Violeta Georgieva < > > > violetagg@ > > > >: > > > >> Mhm that's what I'm trying to achieve in order to supply the > >> configuration > >> automatically for TomEE Buildpack. > >> https://github.com/cloudfoundry-community/tomee-buildpack/issues/5 > >> > >> > >> Romain Manni-Bucau wrote > >> > To be honest I wouldnt use this but resources.xml cause this bind a > >> global > >> > resource to an application which is never very sane - but can be > needed > >> in > >> > some clouds. properties-provider should allows you to extract the > >> config > >> > if > >> > it is the goal. > >> > > >> > > >> > Romain Manni-Bucau > >> > @rmannibucau <https://twitter.com/rmannibucau> | Blog > >> > <http://rmannibucau.wordpress.com> | Github > >> > <https://github.com/rmannibucau> | > >> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > >> > <http://www.tomitribe.com> > >> > > >> > 2015-12-01 22:18 GMT+01:00 Violeta Georgieva < > >> > >> > violetagg@ > >> > >> > >: > >> > > >> >> One additional question: Is there a better way to achieve this? - > >> >> Resource > >> >> specifies via system properties and a driver provided by the web app > >> >> binaries. > >> >> > >> >> > >> >> Violeta Georgieva wrote > >> >> > Hi, > >> >> > > >> >> > So what is your proposal? > >> >> > Romain Manni-Bucau wrote > >> >> >> - I skipped on master (7.x) lazy resource merge in tomcat jndi > tree > >> to > >> >> >> avoid the first exception to be seen and tomcat to try to process > >> them > >> >> at > >> >> >> startup. This then makes the remove() working as expected - the > >> remove > >> >> is > >> >> >> intended to avoid to consider this virtual property as a real one > >> in > >> >> the > >> >> >> "object factory". > >> >> > In 1.7.3 this resource merge in tomcat jndi is not skipped and the > >> >> > property is removed. > >> >> > How I can overcome this? > >> >> > > >> >> > Thanks, > >> >> > Violeta > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> > http://tomee-openejb.979440.n4.nabble.com/Resource-and-UseAppClassLoader-question-tp4677073p4677078.html > >> >> Sent from the TomEE Users mailing list archive at Nabble.com. > >> >> > >> > >> > >> > >> > >> > >> -- > >> View this message in context: > >> > http://tomee-openejb.979440.n4.nabble.com/Resource-and-UseAppClassLoader-question-tp4677073p4677080.html > >> Sent from the TomEE Users mailing list archive at Nabble.com. > >> > > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Resource-and-UseAppClassLoader-question-tp4677073p4677083.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
