Tuesday, 15 March 2011

Mule 3.3.0 - global property not being resolved from properties file -



Mule 3.3.0 - global property not being resolved from properties file -

the global property not beingness resolved properties file, result of mmc deployment fails. ides why wrong?

<context:property-placeholder location="airports.properties" /> <global-property name="airportslist" value="${airportslist}" />

getting next exception --

com.mulesoft.mmc.agent.v3.dto.deploymentexception: unexpected exception parsing xml document url [file:/arprt/mule-esb-ee/mule-enterprise-standalone-3.3.0/apps/myapp-1.0.0-snapshot/myapp-config.xml]; nested exception java.lang.illegalargumentexception: not resolve placeholder 'airportslist' (org.mule.api.lifecycle.initialisationexception) (org.mule.api.config.configurationexception) @ com.mulesoft.mmc.agent.service.impl.applicationserviceimpl.deploy(applicationserviceimpl.java:245) @ sun.reflect.nativemethodaccessorimpl.invoke0(native method)

airports.properties contains above mentioned property:

airportslist={'sfo', 'yyz', 'dfw'}

you not need declare global-property if property defined in properties file , loaded context:property-placeholder.

just remove:

<global-property name="airportslist" value="${airportslist}" />

and utilize ${airportslist} anywhere need in config.

mule

No comments:

Post a Comment