Ron

@JosephEarl - it looks like you caught a virus that's sending emails on your behalf. I've deleted your 'comments' from the different posts but please look into it.

Yup, that's possible behavior when using YAML 1.1. `YES` can be considered as `true` (also `ON` and some other things). We should disable this kind of parsing though, and I...

That's actually not true, @piebur. JSON Schema doesn't work that way. The `type` has no impact on the `enum` or vice versa. You can define the type to be integer,...

@hellmersjl3ds - while the swagger dependency is easily fixable, the rest are a bit beyond me. This sample was contributed to us, but unfortunately, we're not really grails users/developers so...

@ceekayel has kindly contributed a set of changes to the sample which indeed help it compile now. Unfortunately, there are still issues with the sample, so it's not working just...

Right now we only support debugging by content, though adding validation should be fairly easy. For your use case though, it will work only if the spec is a single...

It's funny you quote the spec, because it actually means that it makes no sense to use the `default` value as a default value in the UI because the client/server...

I believe we may be ready for that now. Please let me know if you need any assistance.

@federecio - 1.5.1-M2 is the latest. The develop_2.0's dropwizard sample works, if you want.

That sounds more like a backend issue. The `Accept` header is only a hint to the producer as to what the client wants to receive. The producer, on the other...