> +import org.jclouds.rest.annotations.PayloadParam;
> +import org.jclouds.rest.annotations.RequestFilters;
> +
> +/**
> + * Provides access to Resource features.
> + *
> + */
> +@RequestFilters(AuthenticateRequest.class)
> +@Consumes(MediaType.APPLICATION_JSON)
> +@Produces(MediaType.APPLICATION_JSON)
> +public interface TemplateApi {
> +
> + @Named("validation:validate_template")
> + @POST
> + @Path("/validate")
> + @Fallback(NullOnNotFoundOr404.class)
I think you are right and I have removed the 404 fallback for the POST call. I
can't really justify it, even with the service the way it is right now. The
problem is that the service behaves in a somewhat weird way when certain
invalid URLs are supplied (socket timeouts in some cases), so this should make
more sense overall for now.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/193/files#r32673496
