The PropertyPlaceholderConfigurer is not made for this kind of substitution.
Did you need this stuff only for your test or also for your regular deployment? Which environment do you use (Standalone, Karaf, Tomcat, ...)? Best, Christian On Wed, Nov 7, 2012 at 4:29 PM, pberkman <[email protected]>wrote: > I have the following in my main Camel context: > > <bean id="bridgePropertyPlaceholder" > class="org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer"> > <property name="location" > value="file:nextgate/ms/ngmsroute.properties"/> > </bean> > > and, a bit later in the file I try and use the properties to control an > <import...> as follows: > > <import resource="${nextgate.ms.hl7v3.pdq.endpointfile}" /> > <import resource="${nextgate.ms.hl7v3.pix.endpointfile}" /> > <import resource="${nextgate.ms.hl7v3.xcpd.endpointfile}" /> > > I'm doing this to allow for various configurations - secure, non-secure, > and > SAML bassed endpoints. > > I'm getting an exception from Spring that the referenced placeholder has > NOT > been defined. > > It seems that the Spring loader goes through and tries to complete all of > the IMPORTs BEFORE loading the propert bridge bean. Is this correct, or am > I missing something else? > > if so, another question is: is there a way to have the Bridge Property > bean > prioritized BEFORE the imports get executed? > > thank you! > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Bridge-Property-Loading-Order-tp5722306.html > Sent from the Camel - Users mailing list archive at Nabble.com. > --
