You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Eamonn Dwyer (JIRA)" <ji...@apache.org> on 2009/07/01 17:28:09 UTC
[jira] Created: (CXF-2328) Corba Exceptions not being mapped
correctly
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
Fix For: 2.2.3
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.
[jira] Resolved: (CXF-2328) Corba Exceptions not being mapped
correctly
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2328.
------------------------------
Resolution: Fixed
Fix Version/s: 2.1.6
> 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.1.6, 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.
[jira] Assigned: (CXF-2328) Corba Exceptions not being mapped
correctly
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CXF-2328) Corba Exceptions not being mapped
correctly
Posted by "Eamonn Dwyer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eamonn Dwyer updated CXF-2328:
------------------------------
Attachment: CorbaExceptionProblem.diff
Test case that works with
http://svn.apache.org/repos/asf/cxf/tags/cxf-2.2
but not with
http://svn.apache.org/repos/asf/cxf/branches/2.2.x-fixes
> 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
> 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.