Yes, it does add clarity and it makes sense, kinda. That way would work
for smaller maps, but doesn't scale. But that may not be relevant to you.
That is not possible now in camel, but I'll create a new and think of a
solution, hopefully for 2.9.0.
Hadrian
On 09/12/2011 11:16 PM, ganges_k wrote:
Here is an example which explains the need for HashMap. As part of camel-snmp
component, we want to pass the trap information (oid<key> = value<value)
which are dynamic to the recipient. We want to send this information in the
URI which the target endpoint (third-party system) can understand.
I hope this information gives more clarity in terms of usage. Please let me
know is there a way to solve this.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-URI-parameters-to-support-HashMap-k-v-tp4794389p4796913.html
Sent from the Camel Development mailing list archive at Nabble.com.
