No, it's my fault, because I was from mobile and I was reading too fast. I'm sorry.
Yes, probably the best solution is multiple properties file. Il giorno ven 31 gen 2020 alle ore 17:10 Remco Schoen <r.sch...@topdesk.com> ha scritto: > Thanks, I think we are misunderstanding each other. But we will look into > an alternative for the properties, which probably will be multiple files. > > > Op 31 jan. 2020, om 16:59 heeft Andrea Cosentino <anco...@gmail.com> > het volgende geschreven: > > > > Let me answer again: if you need to distinguish between properties for > > testing and production through the propertyPrefix, no, you can't do it > > anymore. > > > > Il giorno ven 31 gen 2020 alle ore 16:57 Remco Schoen < > r.sch...@topdesk.com> > > ha scritto: > > > >> Let me rephrase the question: > >> > >> So it is no longer possible to distinguish between properties for > testing > >> and production in one properties file? > >> > >> > >>> Op 31 jan. 2020, om 16:54 heeft Andrea Cosentino <anco...@gmail.com> > >> het volgende geschreven: > >>> > >>> No, we removed the options because they were more harmful than useful > >>> > >>> Actually the propertyPrefix is set to default and cannot be changed. > >>> > >>> Il giorno ven 31 gen 2020 alle ore 16:52 Remco Schoen < > >> r.sch...@topdesk.com> > >>> ha scritto: > >>> > >>>> I repeat my question: > >>>> > >>>> Is there a way of doing such a setup in Camel 3? I rather wouldn’t > like > >> to > >>>> have multiple properties files. > >>>> > >>>> > >>>>> Op 31 jan. 2020, om 16:50 heeft Andrea Cosentino <anco...@gmail.com> > >>>> het volgende geschreven: > >>>>> > >>>>> The propertyPrefix along with the other advanced options have been > >>>> removed. > >>>>> > >>>>> > >>>> > >> > https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_properties_component > >>>>> > >>>>> Il giorno ven 31 gen 2020 alle ore 16:48 Remco Schoen < > >>>> r.sch...@topdesk.com> > >>>>> ha scritto: > >>>>> > >>>>>> Hi, > >>>>>> > >>>>>> I was testing to see if I can use Camel 3.0.1 for my work and I > found, > >>>>>> that I no longer can use the propertyPrefix in the > >> propertyPlaceholder. > >>>> I > >>>>>> was using the prefix to make a distinction between production, test > >> and > >>>>>> acceptance using an environment variable like this: > >>>>>> > >>>>>> <propertyPlaceholder id="tifProperties" > >> propertyPrefix="${env:STAGE}.”> > >>>>>> > >>>>>> And with a properties file like this: > >>>>>> > >>>>>> component=jetty:http://0.0.0.0:8090 > >>>>>> acc.component=jetty:http://0.0.0.0:80 > >>>>>> # CAUTION: production setting > >>>>>> prod.component=jetty:http://0.0.0.0:80 > >>>>>> > >>>>>> Is there a way of doing such a setup in Camel 3? I rather wouldn’t > >> like > >>>> to > >>>>>> have multiple properties files. > >>>>>> > >>>>>> Kind regards, > >>>>>> > >>>>>> Remco Schoen > >>>>>> > >>>> > >>>> > >> > >> > >
