deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dies Koper (JIRA)" <>
Subject [jira] [Updated] (DTACLOUD-337) return empty array instead of error when resource not found
Date Mon, 08 Oct 2012 13:00:03 GMT


Dies Koper updated DTACLOUD-337:

    Attachment: 0001-FGCP-return-empty-array-instead-of-error-when-no-dat.patch

renamed /VALIDATION_ERROR.*/ to /RESOURCE_NOT_FOUND/ in firewalls
> return empty array instead of error when resource not found
> -----------------------------------------------------------
>                 Key: DTACLOUD-337
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Improvement
>          Components: Server
>         Environment: latest workspace, fgcp driver
>            Reporter: Dies Koper
>            Assignee: Marios Andreou
>            Priority: Minor
>         Attachments: 0001-FGCP-return-empty-array-instead-of-error-when-no-dat.patch,
> Making fgcp driver comply with what mfojtik said in an e-mail to the ML on 26/07/2012:
> While I working on driver unit tests, I discovered that different drivers
> use different ways how to return data. For example in EC2, when you query
> for 'non-existing' resource (like instance), an Exception is being raised
> whereas in Mock driver, the method just return empty array or 'nil'.
> I think it would be great to have this unified across all driver, before
> we start advertising the new Library code.
> So I took the 'Mock' driver as an example, mean that:
> driver.instance(:id => 'unknown') => nil
> driver.instances(:id => 'unknown') => []
> I think this behavior is more easy to understand that capturing different
> kinds of exceptions.

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:

View raw message