cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Panu Hämäläinen (JIRA) <j...@apache.org>
Subject [jira] [Updated] (DOSGI-254) ServiceInvocationHandler does not handle checked super-interface exceptions correctly
Date Fri, 20 Jan 2017 11:54:26 GMT

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

Panu Hämäläinen updated DOSGI-254:
----------------------------------
    Description: 
If a remote service interface is composed of an interface hierarchy, the ServiceInvocationHandler
(in org.apache.cxf.dosgi.dsw.handlers package)  only handles correctly the checked exceptions
of the interface the service directly implements (the lowest level interface of the hierarchy).
The checked exceptions of the super-interface methods are thrown as generic ServiceExceptions
(which are RuntimeExceptions). 

For example below, the IOException thrown by the throwBaseException method gets converted
to ServiceException while the URISyntaxException thrown by the throwSubException method remains
correctly as URISyntaxException. The service is exported as a TestSubInterface service.

{code}
    public interface TestBaseInterface {
        void throwBaseException() throws IOException;
    }
    
    public interface TestSubInterface extends TestBaseInterface {
        void throwSubException() throws URISyntaxException;
    }

    public class TestClass implements TestSubInterface {
        @Override
        public void throwBaseException() throws IOException {
            throw new IOException("expected baseinterface exception");
        }

        @Override
        public void throwSubException() throws URISyntaxException {
            throw new URISyntaxException("some input", "expected subinterface exception");
        }
    }
{code}

I have been using DOSGi 1.7.0 but I also checked version 2.0.0 and ServiceInvocationHandler
(now in org.apache.cxf.dosgi.common.proxy package) seems the same as in previous releases.

  was:
If a remote service interface is composed of an interface hierarchy, the ServiceInvocationHandler
(in org.apache.cxf.dosgi.dsw.handlers package)  only handles correctly the checked exceptions
of the interface the service directly implements (the lowest level interface of the hierarchy).
The checked exceptions of the super-interface methods are thrown as generic ServiceExceptions
(which are RuntimeExceptions). 

For example below, the IOException thrown by the throwBaseException method gets converted
to ServiceException while the URISyntaxException thrown by the throwSubException method remains
correctly as URISyntaxException .

{code}
    public interface TestBaseInterface {
        void throwBaseException() throws IOException;
    }
    
    public interface TestSubInterface extends TestBaseInterface {
        void throwSubException() throws URISyntaxException;
    }

    public class TestClass implements TestSubInterface {
        @Override
        public void throwBaseException() throws IOException {
            throw new IOException("expected baseinterface exception");
        }

        @Override
        public void throwSubException() throws URISyntaxException {
            throw new URISyntaxException("some input", "expected subinterface exception");
        }
    }
{code}

I have been using DOSGi 1.7.0 but I also checked version 2.0.0 and ServiceInvocationHandler
(now in org.apache.cxf.dosgi.common.proxy package) seems the same as in previous releases.


> ServiceInvocationHandler does not handle checked super-interface exceptions correctly
> -------------------------------------------------------------------------------------
>
>                 Key: DOSGI-254
>                 URL: https://issues.apache.org/jira/browse/DOSGI-254
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>          Components: DSW
>    Affects Versions: 2.0.0
>            Reporter: Panu Hämäläinen
>
> If a remote service interface is composed of an interface hierarchy, the ServiceInvocationHandler
(in org.apache.cxf.dosgi.dsw.handlers package)  only handles correctly the checked exceptions
of the interface the service directly implements (the lowest level interface of the hierarchy).
The checked exceptions of the super-interface methods are thrown as generic ServiceExceptions
(which are RuntimeExceptions). 
> For example below, the IOException thrown by the throwBaseException method gets converted
to ServiceException while the URISyntaxException thrown by the throwSubException method remains
correctly as URISyntaxException. The service is exported as a TestSubInterface service.
> {code}
>     public interface TestBaseInterface {
>         void throwBaseException() throws IOException;
>     }
>     
>     public interface TestSubInterface extends TestBaseInterface {
>         void throwSubException() throws URISyntaxException;
>     }
>     public class TestClass implements TestSubInterface {
>         @Override
>         public void throwBaseException() throws IOException {
>             throw new IOException("expected baseinterface exception");
>         }
>         @Override
>         public void throwSubException() throws URISyntaxException {
>             throw new URISyntaxException("some input", "expected subinterface exception");
>         }
>     }
> {code}
> I have been using DOSGi 1.7.0 but I also checked version 2.0.0 and ServiceInvocationHandler
(now in org.apache.cxf.dosgi.common.proxy package) seems the same as in previous releases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message