Hmmm... In that case, if we are going to *keep* both forever, and now that we have a custom Json adapter for the *entire* image object, wouldn't it be better to remove the *complexMetadata* class, and promote the "block device mapping" metadata as a root level element in the Image class? The custom json adapter can take care of that and we forget about duplicate info and users having to know which accessor to use. We would then have:
```java Map<String, String> metadata; Map<String, String> blockDeviceMappingMetadata; ``` Which is also backwards compatible and looks more clean, as we can set proper types for each one? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/626#issuecomment-67711319
