I think this is a reasonable way to approach this and not break backwards compatibility or force the user to always deal with `Map<String, Object>` when the more common case is `Map<String, String>`
@nacx @inbarsto Since you were kind enough to reply to the [Dealing with different JSON value types in a Map](http://mail-archives.apache.org/mod_mbox/incubator-jclouds-dev/201409.mbox/%3ca97b84b3-3890-4675-819a-3118249fb...@rackspace.com%3E), I'd be interested in your opinion on this approach to fix it. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/626#issuecomment-67355954
