>> >> When we see "bean:" prefixing a key, then we treat myJpaRepo as bean >> id. If it can not be resolved, we will flag an error. If "bean:" is >> not there, the value is a string "myJpaRepo". Since ':' is not a >> valid Java variable name, we don't have to worry about "bean:" >> clashing with key name. > > Yeah the bean: convention is also nice at it clearly highlights that > it's a bean reference, and no problems if end users want a string > literal starting with #. > > When I first thought of this I used the convetion that if the > parameter name ended with Ref then it was a bean reference. So it > should be: > file://inbox/?idempotent=true&idempotentRepositoryRef=myJpaRepo > > That is why currently we have the xxxRef options added manually on > some of the components. >
I like where this is going. My personal preference would be to use a "key:ref=value" syntax. That way you avoid the escaping issues with # in the value and you avoid the property name clash issues with the Property name. Plus is reads nicely. example: file://inbox/?idempotent=true&idempotentRepository:ref=myJpaRepo -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
