> +public abstract class Template {
> +
> + /**
> + * @return the description of this Stack Template.
> + */
> + @Nullable public abstract String getDescription();
> +
> + /**
> + * @return the parameters of this Stack, such as compute_flavor or
> compute_image.
> + */
> + @Nullable public abstract Map<String, Object> getParameters();
> +
> + /**
> + * @return the resources of this Stack, such as server_instance.
> + */
> + @Nullable public abstract Map<String, Object> getResources();
Very good point, but let me expand on that a bit. Classes such as Template here
that are returned by deserializing service JSON have no reason to have nullable
collections, and it makes sense to just use empty collections. This also should
be easy to do.
Classes which we use for serialization to the service should still support
nullable collection, as nullables automatically do not get serialized in
jclouds. We could change this (i.e. do not serialize empty collections), but I
am not sure that makes sense.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/193/files#r32575492
