That was a challenge i had... Unfortunately, it will be parsed at statement
execution time as a string replacement, not at map build time with the
passed in properties. It's an inconsistency... :-/
In Statements:
#{} == Prepared Statement Parameter
${} == String replacement at execution
Might I suggest if you're going to change the tokens perhaps using
:{} (that's colon) for prepared statement parameters would be in
order. It matches how prepared statement parameters are identified
in most host environments.
I suspect the #{} usage may be a nod to Cold
I think I like the idea of the new token. There have been list threads
before where accessing properties at map build would have been very
convenient. This would be especially great for DB Trash (to reference a
thread from the past):
JSF uses #{} for binding. This is meant to be consistent with that (even
though I'm not a fan of JSF, it's at least one reference for consistency).
Similarly ANT and many other projects use ${} for direct token/value
replacement, usually with properties.
Now we need something in between...
