cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (JIRA)" <>
Subject [jira] [Commented] (CXF-4860) Request.Inpustream Lost
Date Wed, 27 Feb 2013 11:47:13 GMT


Aki Yoshida commented on CXF-4860:

I am not sure why you want to get the input stream directly from the servlet request object
and not from the message.

I think it would be better if you can explain it more and post your question to users@cxf
list first.

regards, aki
> Request.Inpustream Lost
> -----------------------
>                 Key: CXF-4860
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.6.6
>         Environment: On JEUS Web Application Server
>            Reporter: Keunil Yoon
>            Assignee: Sergey Beryozkin
>             Fix For: 2.8.0, 2.7.4, 2.6.7
> Hi.
> I am using CXF on WAS (JEUS 6).
> I called jax-rs service with "application/x-www-form-urlencoded" content type.
> I'm ok with Tomcat or WebLogic.
> But some WAS lost request.getInpustream.(It already read).
> When CXF 2.3.x was good. but after 2.4.X,
> AbstractHTTPDestination.class changed and copyKnownRequestParameters code is added.
> I think copyKnownRequestParameters method call request.getParameter, so WAS read request.inpustream.
So some Interceptor can't handle inpustream.
> WAS can not be changed. Can you suggest any solution?
> Is copyKnownRequestParameters method necessary method.
> Thanks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message