You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jens Granseuer (JIRA)" <ji...@apache.org> on 2012/06/11 13:37:42 UTC
[jira] [Created] (CAMEL-5356) CXF endpoint doesn't play nice with
doTry/doCatch
Jens Granseuer created CAMEL-5356:
-------------------------------------
Summary: CXF endpoint doesn't play nice with doTry/doCatch
Key: CAMEL-5356
URL: https://issues.apache.org/jira/browse/CAMEL-5356
Project: Camel
Issue Type: Bug
Components: camel-cxf
Affects Versions: 2.8.3
Reporter: Jens Granseuer
When using a CXF client endpoint to call a web service via SOAP/HTTP there are two possible error scenarios:
1) The call fails immediately with an exception (e.g. because the service is down/the address is wrong)
2) The call "succeeds" but returns a SOAP fault. This could also signal an error condition to the application.
Currently, using doTry/doCatch doesn't work properly in either scenario because, apprently, the CXF endpoint nulls the message when receiving an exception or fault.
--
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] (CAMEL-5356) CXF endpoint doesn't play nice with
doTry/doCatch
Posted by "Jens Granseuer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jens Granseuer updated CAMEL-5356:
----------------------------------
Attachment: camelTryCatch.zip
Here is a test case with both scenarios. Note that the test also shows another (related?) issue: For the first test to succeed the convertBodyTo is required (despite stream caching being turned on). For the last test case, the convertBodyTo must not be present, however.
> CXF endpoint doesn't play nice with doTry/doCatch
> -------------------------------------------------
>
> Key: CAMEL-5356
> URL: https://issues.apache.org/jira/browse/CAMEL-5356
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.8.3
> Reporter: Jens Granseuer
> Attachments: camelTryCatch.zip
>
>
> When using a CXF client endpoint to call a web service via SOAP/HTTP there are two possible error scenarios:
> 1) The call fails immediately with an exception (e.g. because the service is down/the address is wrong)
> 2) The call "succeeds" but returns a SOAP fault. This could also signal an error condition to the application.
> Currently, using doTry/doCatch doesn't work properly in either scenario because, apprently, the CXF endpoint nulls the message when receiving an exception or fault.
--
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] [Commented] (CAMEL-5356) CXF endpoint doesn't play nice with
doTry/doCatch
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293649#comment-13293649 ]
Claus Ibsen commented on CAMEL-5356:
------------------------------------
There is a handleFault you can enable to turn SOAP faults into exceptions, which Camels error handler can react upon.
> CXF endpoint doesn't play nice with doTry/doCatch
> -------------------------------------------------
>
> Key: CAMEL-5356
> URL: https://issues.apache.org/jira/browse/CAMEL-5356
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.8.3
> Reporter: Jens Granseuer
> Attachments: camelTryCatch.zip
>
>
> When using a CXF client endpoint to call a web service via SOAP/HTTP there are two possible error scenarios:
> 1) The call fails immediately with an exception (e.g. because the service is down/the address is wrong)
> 2) The call "succeeds" but returns a SOAP fault. This could also signal an error condition to the application.
> Currently, using doTry/doCatch doesn't work properly in either scenario because, apprently, the CXF endpoint nulls the message when receiving an exception or fault.
--
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] (CAMEL-5356) CXF endpoint doesn't play nice with
doTry/doCatch
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-5356:
-------------------------------
Fix Version/s: Future
Issue Type: Bug (was: Wish)
Lets see if we can get this fixed in a future patch releases of the Camel branches.
In terms of #2 then the idea would be that when you use handleFault=true then Camel turns SOAP Faults into exceptions, which try .. catch ought to react upon.
> CXF endpoint doesn't play nice with doTry/doCatch
> -------------------------------------------------
>
> Key: CAMEL-5356
> URL: https://issues.apache.org/jira/browse/CAMEL-5356
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.8.3
> Reporter: Jens Granseuer
> Fix For: Future
>
> Attachments: camelTryCatch.zip
>
>
> When using a CXF client endpoint to call a web service via SOAP/HTTP there are two possible error scenarios:
> 1) The call fails immediately with an exception (e.g. because the service is down/the address is wrong)
> 2) The call "succeeds" but returns a SOAP fault. This could also signal an error condition to the application.
> Currently, using doTry/doCatch doesn't work properly in either scenario because, apprently, the CXF endpoint nulls the message when receiving an exception or fault.
--
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] [Commented] (CAMEL-5356) CXF endpoint doesn't play nice with
doTry/doCatch
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398421#comment-13398421 ]
Claus Ibsen commented on CAMEL-5356:
------------------------------------
Thanks for the tests cases. The #1 situation should of course be propagated back to the caller, if sending failed due some exception.
> CXF endpoint doesn't play nice with doTry/doCatch
> -------------------------------------------------
>
> Key: CAMEL-5356
> URL: https://issues.apache.org/jira/browse/CAMEL-5356
> Project: Camel
> Issue Type: Wish
> Components: camel-cxf
> Affects Versions: 2.8.3
> Reporter: Jens Granseuer
> Attachments: camelTryCatch.zip
>
>
> When using a CXF client endpoint to call a web service via SOAP/HTTP there are two possible error scenarios:
> 1) The call fails immediately with an exception (e.g. because the service is down/the address is wrong)
> 2) The call "succeeds" but returns a SOAP fault. This could also signal an error condition to the application.
> Currently, using doTry/doCatch doesn't work properly in either scenario because, apprently, the CXF endpoint nulls the message when receiving an exception or fault.
--
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] (CAMEL-5356) CXF endpoint doesn't play nice with
doTry/doCatch
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-5356:
-------------------------------
Issue Type: Wish (was: Bug)
> CXF endpoint doesn't play nice with doTry/doCatch
> -------------------------------------------------
>
> Key: CAMEL-5356
> URL: https://issues.apache.org/jira/browse/CAMEL-5356
> Project: Camel
> Issue Type: Wish
> Components: camel-cxf
> Affects Versions: 2.8.3
> Reporter: Jens Granseuer
> Attachments: camelTryCatch.zip
>
>
> When using a CXF client endpoint to call a web service via SOAP/HTTP there are two possible error scenarios:
> 1) The call fails immediately with an exception (e.g. because the service is down/the address is wrong)
> 2) The call "succeeds" but returns a SOAP fault. This could also signal an error condition to the application.
> Currently, using doTry/doCatch doesn't work properly in either scenario because, apprently, the CXF endpoint nulls the message when receiving an exception or fault.
--
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] (CAMEL-5356) CXF endpoint doesn't play nice with
doTry/doCatch
Posted by "David J. M. Karlsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David J. M. Karlsen updated CAMEL-5356:
---------------------------------------
Comment: was deleted
(was: Any news on this?
My onException handling is never called.
If it makes any difference this is an inOnly webservice.
I've set handleException true and handleFault=true.)
> CXF endpoint doesn't play nice with doTry/doCatch
> -------------------------------------------------
>
> Key: CAMEL-5356
> URL: https://issues.apache.org/jira/browse/CAMEL-5356
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.8.3
> Reporter: Jens Granseuer
> Fix For: Future
>
> Attachments: camelTryCatch.zip
>
>
> When using a CXF client endpoint to call a web service via SOAP/HTTP there are two possible error scenarios:
> 1) The call fails immediately with an exception (e.g. because the service is down/the address is wrong)
> 2) The call "succeeds" but returns a SOAP fault. This could also signal an error condition to the application.
> Currently, using doTry/doCatch doesn't work properly in either scenario because, apprently, the CXF endpoint nulls the message when receiving an exception or fault.
--
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] [Commented] (CAMEL-5356) CXF endpoint doesn't play nice with
doTry/doCatch
Posted by "David J. M. Karlsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496218#comment-13496218 ]
David J. M. Karlsen commented on CAMEL-5356:
--------------------------------------------
Any news on this?
My onException handling is never called.
If it makes any difference this is an inOnly webservice.
I've set handleException true and handleFault=true.
> CXF endpoint doesn't play nice with doTry/doCatch
> -------------------------------------------------
>
> Key: CAMEL-5356
> URL: https://issues.apache.org/jira/browse/CAMEL-5356
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.8.3
> Reporter: Jens Granseuer
> Fix For: Future
>
> Attachments: camelTryCatch.zip
>
>
> When using a CXF client endpoint to call a web service via SOAP/HTTP there are two possible error scenarios:
> 1) The call fails immediately with an exception (e.g. because the service is down/the address is wrong)
> 2) The call "succeeds" but returns a SOAP fault. This could also signal an error condition to the application.
> Currently, using doTry/doCatch doesn't work properly in either scenario because, apprently, the CXF endpoint nulls the message when receiving an exception or fault.
--
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] [Commented] (CAMEL-5356) CXF endpoint doesn't play nice with
doTry/doCatch
Posted by "Jens Granseuer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293676#comment-13293676 ]
Jens Granseuer commented on CAMEL-5356:
---------------------------------------
At least in POJO mode it seems like a SOAP fault is handled like an exception anyway. Either way, using handleFault=true doesn't change the outcome of the test cases.
> CXF endpoint doesn't play nice with doTry/doCatch
> -------------------------------------------------
>
> Key: CAMEL-5356
> URL: https://issues.apache.org/jira/browse/CAMEL-5356
> Project: Camel
> Issue Type: Wish
> Components: camel-cxf
> Affects Versions: 2.8.3
> Reporter: Jens Granseuer
> Attachments: camelTryCatch.zip
>
>
> When using a CXF client endpoint to call a web service via SOAP/HTTP there are two possible error scenarios:
> 1) The call fails immediately with an exception (e.g. because the service is down/the address is wrong)
> 2) The call "succeeds" but returns a SOAP fault. This could also signal an error condition to the application.
> Currently, using doTry/doCatch doesn't work properly in either scenario because, apprently, the CXF endpoint nulls the message when receiving an exception or fault.
--
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