cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (CXF-2328) Corba Exceptions not being mapped correctly
Date Wed, 01 Jul 2009 15:59:47 GMT

     [ https://issues.apache.org/jira/browse/CXF-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp reassigned CXF-2328:
--------------------------------

    Assignee: Daniel Kulp

> Corba Exceptions not being mapped correctly
> -------------------------------------------
>
>                 Key: CXF-2328
>                 URL: https://issues.apache.org/jira/browse/CXF-2328
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.2.2
>            Reporter: Eamonn Dwyer
>            Assignee: Daniel Kulp
>             Fix For: 2.2.3
>
>         Attachments: CorbaExceptionProblem.diff
>
>
> Corba exceptions used to be mapped correctly in version 2.2.0.0 of cxf. In the latest
code the underlying corba exception is not being reported back to the client.
> It seems this change to ClientImpl.java has affected the corba binding
> http://pastebin.com/m10019bf5
> Previously the client was relying on 
> chain.doIntercept(message);
> being called. 
> This would call
> CorbaStreamInInterceptor.handleMessage which in turn would invoke
> ep.getInFaultObserver().onMessage(message);
> which would invoke CorbaStreamFaultInInterceptor.handleMessage
> CorbaStreamFaultInInterceptor is the class that does the mapping, it needs to be called

-- 
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