> + @Path("/vips")
> + @SelectJson("vip")
> + VIP createVIP(@WrapWith("vip") VIP.CreateVIP vip);
> +
> + /**
> + * Update a VIP.
> + *
> + * @param id the id of the VIP to update.
> + * @param vip the VIP's attributes to update.
> + * @return a reference of the updated VIP.
> + */
> + @Named("vip:update")
> + @PUT
> + @Path("/vips/{id}")
> + @SelectJson("vip")
> + @Fallback(NullOnNotFoundOr404.class)
POST operations don't use 404 fallbacks. Should I have to remove 404 fallbacks
on PUT operations? Or is it going to be the subject of a future PR? I mean, a
new PR to remove 404 fallbacks on all service operations (RouterApi,
NetworkApi, etc.)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/146/files#r17897680
