Matija Mazi

I've created a quick patch and it seems `throws Exception` can be supported in rescu: #114. Please try it and report if this helps.

Move logback.xml to src/main/resources. Better still, move your main method to the xchange-examples module; logback is already configured there, and it will be more consistent. Also, please continue communication regarding...

> is there a programmatic feature to do same? None that I know of. In which branch in your repo can I find this code? Not in develop.

> src/main/resources doesn't change the outcome. Perhaps you must mark the src/main/resources as resources root in IntelliJ. Or perhaps try a `mvn package` before running the main method (I assume...

@jnorthrup Please give me a hand here: 1. Fork rescu 2. Create a test in RestInvocationHandlerTest that demonstrates the `@Valid` problem: * Add a new method in ExampleService with a...

So, to clarify: this is a bug in rescu, it should treat the parameter that is annotated only with `@Valid` (or any non-JAX-RS-parameter annotations) as the "unannotated" parameter (there can...

See how RestEasy, Jersey etc. handle this.

I think serialization in rescu should generally be refactored (eg. factor out the serialization methods from `Params`); serialization should be separate from the beans that hold data. This deserves a...

There is no explicit support for this in rescu currently. However, rescu uses `java.net.HttpURLConnection` under the hood to create connections; see if HttpURLConnection supports what you want, then we might...

A pull request to fix this will be welcome, and merged promptly :)