cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-2464) ClassCastException in JAXRSOutInterceptor.serializeMessage
Date Fri, 09 Oct 2009 20:13:31 GMT

    [ https://issues.apache.org/jira/browse/CXF-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764176#action_12764176
] 

Sergey Beryozkin commented on CXF-2464:
---------------------------------------

it's unfortunate...please use new MetadataMap<String, Object> as a workaround, it implements
Map<String, List<Object>> so will work in JAXWS only case

> ClassCastException in JAXRSOutInterceptor.serializeMessage
> ----------------------------------------------------------
>
>                 Key: CXF-2464
>                 URL: https://issues.apache.org/jira/browse/CXF-2464
>             Project: CXF
>          Issue Type: Bug
>          Components: REST
>    Affects Versions: 2.2.2
>            Reporter: Tommy Odom
>
> The following line in JAXRSOutInterceptor.serializeMessage causes a ClassCastException
if the headers are not of type MultivaluedMap.
>         MultivaluedMap<String, Object> responseHeaders = 
>             (MultivaluedMap)message.get(Message.PROTOCOL_HEADERS);
> We have an existing CXF out interceptor that we configure on the CXF bus which works
with both SOAP and REST calls so when we add the protocol headers we use a standard HashMap.
 This worked fine in CXF 2.2 but when we tried upgrading to CXF 2.2.2 our REST services started
failing.  A few lines above that the code retrieves the headers and refers to them as a standard
Map interface.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message