Isn't this a bit of an object-oriented failure for HttpPost to inherit from
the abstract class of AbstractHttpMessage when setParams(HttpParams params)
does absolutely nothing?
Roland Weber wrote:
>
> Hello Ever,
>
>> Here is the code on client side:
>> // prepare parameters
>> HttpParams params = new BasicHttpParams();
>> params.setParameter("paraName", "test");
>
> HttpParams provides parameters to the HttpClient framework.
> If you want send something to the server, put it in an
> entity. The one you're looking for is this:
> http://hc.apache.org/httpcomponents-client/httpclient/apidocs/org/apache/http/client/methods/UrlEncodedFormEntity.html
>
>> When I use httpclient3.x for this kind of functions, it works fine.
>
> If you call PostMethod.getParams().setParameter(...) in 3.1,
> it fails just as miserably ;-)
>
> But we need to improve our documentation, quickly...
>
> cheers,
> Roland
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/httpclient4-app-cause-serverside-servlet-request.getparameter%28%29-return-null--tp15796391p18014758.html
Sent from the HttpClient-User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
