Reusing request messages can cause incorrect option value

[taylow]

One of the methods of proving access to the MethodOptions was to add a method to the request model.

This is fine if there is a 1-to-1 service method to request model relationship, but once a service uses the same request message for two or more service methods, one will most likely overwrite the previous.

There is a risk of receiving an incorrect value, so for now please ensure you do not reuse your request messages of you are going to use the request methods, or stick to the constants/service methods until a better solution is implemented.