Reputation: 517
I'm using Mule Studio 1.3.2, which corresponds to Mule 3.3 I believe.
I'm using a property-placeholder element. I wanted to use the technique described here of having an optional override file. However, the ignore-resource-not-found attribute is being flagged as an error in Mule Studio: Attribute ignore-resource-not-found is not defined as a valid property of property-placeholder
<context:property-placeholder location="classpath:config.properties" ignore-resource-not-found="true" />
Is this broken or am I doing something silly?
Upvotes: 1
Views: 867
Reputation: 211
Under Window -> Preferences -> Mule Studio -> Turn off error reporting in XML editor
This may let through valid errors too, but in my case, I turned it on after verifying everything was working fine. Just kept annoying me, those "red markers".
Do not forget to turn it off, when you modify the flow though.
Upvotes: 0
Reputation: 4551
Mule 3.3
uses Spring context 3.1 schema
which supports ignore-resource-not-found
attribute
<xsd:complexType name="propertyPlaceholder">
<xsd:attribute name="location" type="xsd:string">...</xsd:attribute>
<xsd:attribute name="properties-ref" type="xsd:string">...</xsd:attribute>
<xsd:attribute name="file-encoding" type="xsd:string">...</xsd:attribute>
<xsd:attribute name="order" type="xsd:integer">...</xsd:attribute>
<xsd:attribute name="ignore-resource-not-found" type="xsd:boolean" default="false">
<xsd:annotation>
<xsd:documentation><![CDATA[Specifies if failure to find the property resource location should be ignored. Default is "false", meaning that if there is no file in the location specified an exception will be raised at runtime.]]>
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="ignore-unresolvable" type="xsd:boolean" default="false">... </xsd:attribute>
<xsd:attribute name="local-override" type="xsd:boolean" default="false">...</xsd:attribute>
</xsd:complexType>
so, you're doing the right thing
Upvotes: 2