You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2009/03/19 04:53:50 UTC
[jira] Resolved: (CXF-2115) refactor JBIConduitOutputStream
exception handle
[ https://issues.apache.org/jira/browse/CXF-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved CXF-2115.
-------------------------------
Resolution: Fixed
commit fix
http://svn.apache.org/viewvc?rev=755498&view=rev for trunk
http://svn.apache.org/viewvc?rev=755519&view=rev for 2.1.x branch
http://svn.apache.org/viewvc?rev=755822&view=rev for 2.0.x branch
> refactor JBIConduitOutputStream exception handle
> ------------------------------------------------
>
> Key: CXF-2115
> URL: https://issues.apache.org/jira/browse/CXF-2115
> Project: CXF
> Issue Type: Bug
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 2.0.11, 2.1.5, 2.2.1
>
>
> currently it's
> {code}
> } catch (IOException e) {
> throw e;
> } catch (Exception e) {
> e.printStackTrace();
> new IOException(e.toString());
> }
> {code}
> should be
> {code}
> } catch (IOException e) {
> throw e;
> } catch (Exception e) {
> throw new RuntimeException(e.toString());
> }
> {code}
> so that we can get correct exception back from JBI client side and remove noisy exception stacktrace
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.