[
https://issues.apache.org/jira/browse/JCLOUDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762082#comment-13762082
]
Maty Grosz commented on JCLOUDS-273:
------------------------------------
This is exactly my point: if OpenStack says in their formal documentation that
metadata is an optional attribute, then 'metadata' shouldn't have been included
in the response as they do for any other optional attribute - they don't appear
in the response if they are set to NULL.
I also expose OpenStack APIs in my application, and I don't include the
metadata in my response if it is empty. And this is the source for the problem.
So either OpenStack should make their say more clearly about the metadata, or
JClouds expect NULL value for this attribute or I will need to set this
attribute to an empty map (which probably will be the case eventually).
> JClouds OpenStack Nova v2.0 Server domian doesn't follow OpenStack formal
> documentation
> ---------------------------------------------------------------------------------------
>
> Key: JCLOUDS-273
> URL: https://issues.apache.org/jira/browse/JCLOUDS-273
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Reporter: Maty Grosz
>
> Using class org.jclouds.openstack.nova.v2_0.domain.Server – look at the
> constructor “protected Server(… parameters)”:
> OpenStack formal documentation says that the metadata attribute is optional.
> The constructor above calls to(checkNotNull(metadata, "metadata")) – and
> fails.
> No need to check that in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
