"Waldhoff, Rodney" <[EMAIL PROTECTED]> wrote:
>
>Re: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8458
>
>It's not entirely clear to me how the contract should work between
>setRequestBody and setParameter. Both are trying to set the body for the
>POST request, and doing so in incompatible ways. What should the behavior
>be? Throw an exception when one is called after the other has been already?
>One overrides another?
Throwing an exception when one is called after the other has
been already is fine.
>An alternative may be to add setName() methods to HttpMethod or at least
>HttpMethodBase, so that one could use a PUT method, and make it look like a
>POST. That way different behaviors live in different classes.
This is not quite :-) object-oriented. Imagine someone creates
a GetMethod and changes the method name to "DELETE". If you want
to do something special, subclass HttpMethodBase or implement
HttpMethod from scratch.
I suggest to implement behaviour that is common to at least two
methods in HttpMethodBase.
Best regards
Rainer Klute
Rainer Klute IT-Consulting GmbH i. Gr.
Dipl.-Inform.
Rainer Klute E-Mail: [EMAIL PROTECTED]
Körner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
