We should support multiple parameters on the JAX-RS interface used for RESTEasy bindings. If multiple parameters are specified, it's up to the user to introduce a message composer to map the multi-parameter input data to the single parameter that the SY service interface is expecting. Some general notes:

• We should look at using Proxy in java.lang.reflect instead of class file generation for the JAX-RS implementation class. It will be much easier to maintain in the long run, IMHO.

• If there are multiple parameters on the JAX-RS interface, we need to decide how this is represented in the RESTEasyBindingData. One option is to have a Map represent the content in RESTEasyBindingData where the key is the method parameter names. In cases of a single arg, there will only be a single entry in the map. This makes it pretty easy to code the default, one-arg implementation in MessageComposer.