Discussion:
Using Property Placeholders in
Martin Mulder
2012-08-31 08:01:16 UTC
Permalink
I have a transformer with a @Lookup annotation.
<br />
When I declare a property in a property file loaded via context:property-placeholder it isn't set in the registry (and my Lookup will throw an exception)
<br /><br />
<code>
<br />
Expression Evaluator &quot;registry&quot; with expression &quot;cendris_username&quot; returned null but a value was require
<br />
d&#46; (org&#46;mule&#46;api&#46;expression&#46;ExpressionRuntimeException)
<br />
</code>
<br /><br />
This works well when setting the property via
<br />
Maybe this is a bug in mule, but this happens, even in mule-3.3

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
Fake David Dossot
2012-08-31 14:48:17 UTC
Permalink
It's not a bug. If you use the Spring property placeholder resolver you have to look *it* up in the registry then ask it for the value of "cendris_username". Global properties are different, they are directly bound in the registry.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Loading...