You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Aki Yoshida (JIRA)" <ji...@apache.org> on 2012/10/29 10:23:12 UTC

[jira] [Created] (CAMEL-5755) CXF endpoint's parameter exceptionMessageCauseEnabled not working for Camel CXF endpoints

Aki Yoshida created CAMEL-5755:
----------------------------------

             Summary: CXF endpoint's parameter exceptionMessageCauseEnabled not working for Camel CXF endpoints
                 Key: CAMEL-5755
                 URL: https://issues.apache.org/jira/browse/CAMEL-5755
             Project: Camel
          Issue Type: Improvement
          Components: camel-cxf
    Affects Versions: 2.10.2
            Reporter: Aki Yoshida


CXF provides an option using runtime property exceptionMessageCauseEnabled to include the exception cause at the service invocation in the fault text [1]. But this option is not working for Camel endpoints.

For this setting to work, the message's fault mode must be set by the service invoker. In Camel endpoints, this mode is not set when a fault is thrown. Consequently, the above option is not taken into account.

To support this option for Camel CXF endpoints, this fault mode setting code can be placed in CxfConsumer.

I am attaching a suggested change for trunk and a test case.

I logged this as a minor bug, assuming this option was supposed to work but please feel free to change the issue type to improvement if you find it more suitable.

1. 
http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging-Showingthecauseexceptionmessage


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CAMEL-5755) CXF endpoint's parameter exceptionMessageCauseEnabled not working for Camel CXF endpoints

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CAMEL-5755.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.11.0
                   2.10.3
                   2.9.5

Applied patch into trunk, camel-2.10.x and camel-2.9.x branches with thanks to Aki.
                
> CXF endpoint's parameter exceptionMessageCauseEnabled not working for Camel CXF endpoints
> -----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5755
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5755
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cxf
>    Affects Versions: 2.10.2
>            Reporter: Aki Yoshida
>            Assignee: Willem Jiang
>             Fix For: 2.9.5, 2.10.3, 2.11.0
>
>         Attachments: trunk-20121026.patch
>
>
> CXF provides an option using runtime property exceptionMessageCauseEnabled to include the exception cause at the service invocation in the fault text [1]. But this option is not working for Camel endpoints.
> For this setting to work, the message's fault mode must be set by the service invoker. In Camel endpoints, this mode is not set when a fault is thrown. Consequently, the above option is not taken into account.
> To support this option for Camel CXF endpoints, this fault mode setting code can be placed in CxfConsumer.
> I am attaching a suggested change for trunk and a test case.
> I logged this as a minor bug, assuming this option was supposed to work but please feel free to change the issue type to improvement if you find it more suitable.
> 1. 
> http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging-Showingthecauseexceptionmessage

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CAMEL-5755) CXF endpoint's parameter exceptionMessageCauseEnabled not working for Camel CXF endpoints

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang reassigned CAMEL-5755:
-----------------------------------

    Assignee: Willem Jiang
    
> CXF endpoint's parameter exceptionMessageCauseEnabled not working for Camel CXF endpoints
> -----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5755
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5755
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cxf
>    Affects Versions: 2.10.2
>            Reporter: Aki Yoshida
>            Assignee: Willem Jiang
>         Attachments: trunk-20121026.patch
>
>
> CXF provides an option using runtime property exceptionMessageCauseEnabled to include the exception cause at the service invocation in the fault text [1]. But this option is not working for Camel endpoints.
> For this setting to work, the message's fault mode must be set by the service invoker. In Camel endpoints, this mode is not set when a fault is thrown. Consequently, the above option is not taken into account.
> To support this option for Camel CXF endpoints, this fault mode setting code can be placed in CxfConsumer.
> I am attaching a suggested change for trunk and a test case.
> I logged this as a minor bug, assuming this option was supposed to work but please feel free to change the issue type to improvement if you find it more suitable.
> 1. 
> http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging-Showingthecauseexceptionmessage

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-5755) CXF endpoint's parameter exceptionMessageCauseEnabled not working for Camel CXF endpoints

Posted by "Aki Yoshida (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aki Yoshida updated CAMEL-5755:
-------------------------------

    Attachment: trunk-20121026.patch

trunk diff on camel-cxf
                
> CXF endpoint's parameter exceptionMessageCauseEnabled not working for Camel CXF endpoints
> -----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5755
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5755
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cxf
>    Affects Versions: 2.10.2
>            Reporter: Aki Yoshida
>         Attachments: trunk-20121026.patch
>
>
> CXF provides an option using runtime property exceptionMessageCauseEnabled to include the exception cause at the service invocation in the fault text [1]. But this option is not working for Camel endpoints.
> For this setting to work, the message's fault mode must be set by the service invoker. In Camel endpoints, this mode is not set when a fault is thrown. Consequently, the above option is not taken into account.
> To support this option for Camel CXF endpoints, this fault mode setting code can be placed in CxfConsumer.
> I am attaching a suggested change for trunk and a test case.
> I logged this as a minor bug, assuming this option was supposed to work but please feel free to change the issue type to improvement if you find it more suitable.
> 1. 
> http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging-Showingthecauseexceptionmessage

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira