> + * @return the list of all router references configured for the tenant.
> + */
> + @Named("router:list")
> + @GET
> + @ResponseParser(ParseRouters.class)
> + @Transform(ParseRouters.ToPagedIterable.class)
> + @Fallback(Fallbacks.EmptyPagedIterableOnNotFoundOr404.class)
> + @QueryParams(keys = {"fields", "fields", "fields"}, values = {"id",
> "tenant_id", "name"})
> + PagedIterable<? extends ReferenceWithName> list();
> +
> + @Named("router:list")
> + @GET
> + @ResponseParser(ParseRouters.class)
> + @Fallback(KeystoneFallbacks.EmptyPaginatedCollectionOnNotFoundOr404.class)
> + @QueryParams(keys = {"fields", "fields", "fields"}, values = {"id",
> "tenant_id", "name"})
> + PaginatedCollection<? extends ReferenceWithName> list(PaginationOptions
> options);
Any reason for collection vs. iterable return type above?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/47/files#r7546857
