- Immutable*.Builders instead of maps: more specifically?
- Parsing refactoring / not dry: it definitely needs to be refactored. I might 
prefer to refactor it after I get the last couple of unsupported service calls 
done. 
- Parsing numbers: For this service it is problematic because of how GSON 
parses numbers now (or because of how inflexible the service is when 
accepting/returning numbers).
- Clever parsing logic: The reason there is so much manual mapping is to make 
sure the domain objects make sense and are simple - regardless of what the JSON 
actually looks like. User experience will degrade if domain objects are more 
similar to the JSON (at least so it seems in this case). There are some 
alternatives that can be done to reduce the parsing logic (perhaps a facade of 
some sort)? But it mostly moves the problem elsewhere.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/39#issuecomment-27269197

Reply via email to