You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (Created) (JIRA)" <ji...@apache.org> on 2011/12/14 19:25:30 UTC
[jira] [Created] (DOSGI-102) DOSGI RI can not map SOAP exception to
custom exceptions on the client side
DOSGI RI can not map SOAP exception to custom exceptions on the client side
---------------------------------------------------------------------------
Key: DOSGI-102
URL: https://issues.apache.org/jira/browse/DOSGI-102
Project: CXF Distributed OSGi
Issue Type: Bug
Components: DSW
Affects Versions: 1.3
Reporter: Sergey Beryozkin
Assignee: Sergey Beryozkin
Fix For: 1.3
I think I have found the problem, considering the following code:
http://svn.apache.org/repos/asf/cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/handlers/ServiceInvocationHandler.java
Around line 56-57, where it checks whether the arrived exception is
assignable from the method invoked:
if (type.isAssignableFrom(theCause.getClass())) {
throw theCause;
}
Should be:
if (type.isAssignableFrom(theCause.getCause().getClass())) {
throw theCause.getCause();
}
I tried it out, this way the client gets the declared exception. I dont know
what you exactly meant by providing a patch (I never contributed to OS
projects), but you may check / consider this 2 small corrections.
Cheers,
András
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DOSGI-102) DOSGI RI can not map invocation
exceptions to custom exceptions on the client side
Posted by "Sergey Beryozkin (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DOSGI-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin resolved DOSGI-102.
------------------------------------
Resolution: Fixed
> DOSGI RI can not map invocation exceptions to custom exceptions on the client side
> ----------------------------------------------------------------------------------
>
> Key: DOSGI-102
> URL: https://issues.apache.org/jira/browse/DOSGI-102
> Project: CXF Distributed OSGi
> Issue Type: Bug
> Components: DSW
> Affects Versions: 1.3
> Reporter: Sergey Beryozkin
> Assignee: Sergey Beryozkin
> Fix For: 1.3
>
>
> I think I have found the problem, considering the following code:
> http://svn.apache.org/repos/asf/cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/handlers/ServiceInvocationHandler.java
> Around line 56-57, where it checks whether the arrived exception is
> assignable from the method invoked:
> if (type.isAssignableFrom(theCause.getClass())) {
> throw theCause;
> }
> Should be:
> if (type.isAssignableFrom(theCause.getCause().getClass())) {
> throw theCause.getCause();
> }
> I tried it out, this way the client gets the declared exception. I dont know
> what you exactly meant by providing a patch (I never contributed to OS
> projects), but you may check / consider this 2 small corrections.
> Cheers,
> András
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DOSGI-102) DOSGI RI can not map invocation
exceptions to custom exceptions on the client side
Posted by "Sergey Beryozkin (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DOSGI-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin updated DOSGI-102:
-----------------------------------
Summary: DOSGI RI can not map invocation exceptions to custom exceptions on the client side (was: DOSGI RI can not map SOAP exception to custom exceptions on the client side)
Applies to ws & rest
> DOSGI RI can not map invocation exceptions to custom exceptions on the client side
> ----------------------------------------------------------------------------------
>
> Key: DOSGI-102
> URL: https://issues.apache.org/jira/browse/DOSGI-102
> Project: CXF Distributed OSGi
> Issue Type: Bug
> Components: DSW
> Affects Versions: 1.3
> Reporter: Sergey Beryozkin
> Assignee: Sergey Beryozkin
> Fix For: 1.3
>
>
> I think I have found the problem, considering the following code:
> http://svn.apache.org/repos/asf/cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/handlers/ServiceInvocationHandler.java
> Around line 56-57, where it checks whether the arrived exception is
> assignable from the method invoked:
> if (type.isAssignableFrom(theCause.getClass())) {
> throw theCause;
> }
> Should be:
> if (type.isAssignableFrom(theCause.getCause().getClass())) {
> throw theCause.getCause();
> }
> I tried it out, this way the client gets the declared exception. I dont know
> what you exactly meant by providing a patch (I never contributed to OS
> projects), but you may check / consider this 2 small corrections.
> Cheers,
> András
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira