> +Current implementations have the following two issues : > + > +1. Heavy use of map-binders and parsers to transform JSON. Map-binders use > annotation-selected classes to map method data (such as the data in the > create-user call above) to the JSON required by the service. The > [parsers](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2_0/functions/ParseNetworkDetails.java) > apply the reverse transformation: from JSON to domain objects. > +2. Lack of consistent, concise, and user-friendly way to use domain objects > in create/update/list methods. > + > +In addition to fixing these issues, jclouds wants to provide developers with > some compiler checks and other syntactic sugar (fluent builders), while also > supporting different updating, creating, or listing validation strategies. > + > +We want to > + > +1. Ensure object immutability. > +2. Utilize the fluent builder pattern. > +3. Ensure that "create" objects can only be used for create; update for > update; and listed resources cannot be directly sent back to the service. > +4. Reuse code and keep domain classes > [DRY](http://en.wikipedia.org/wiki/Don't_repeat_yourself). > +5. Allow using different validation strategies (for example, create vs > update). > + > +We have been able to identify a pattern that addresses these issues. Here is > some [sample > code](https://github.com/jclouds/jclouds-labs-openstack/blob/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2/domain/Router.java).
Include the relevant snippet of the sample code here? Or is it too long? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/124/files#r17126300
