camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CAMEL-11052) Soap11DataFormatAdapter throwing exception when using JAXB/JAX-WS generated code
Date Wed, 29 Mar 2017 20:12:41 GMT


ASF GitHub Bot commented on CAMEL-11052:

GitHub user onders86 opened a pull request:

    CAMEL-11052-wsimport compatibility


You can merge this pull request into a Git repository by running:

    $ git pull CAMEL-11052

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1582
commit 4650d7a0373f9bd2957df04e1f037a9f5fd0aba3
Author: onders86 <>
Date:   2017-03-29T20:10:23Z

    CAMEL-11052-wsimport compatibility


> Soap11DataFormatAdapter throwing exception when using JAXB/JAX-WS generated code
> --------------------------------------------------------------------------------
>                 Key: CAMEL-11052
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-soap
>    Affects Versions: 2.18.3
>            Reporter: Kieran Simpson
>            Assignee: onder sezgin
>            Priority: Minor
>              Labels: soap11
> When using WsImport, the structure of the generated Exception class for SOAP Faults have
only a two arg constructor generated ie:
> {code:java}public MyException(String message, <Type> faultInfo) {}{code}
> However in {{Soap11DataFormatAdapter::createExceptionFromFault}} the code is trying to
get a reference to the single argument constructor, before it tries to find/use the two argument
constructor, which would cause a {{NoSuchMethodException}} to be thrown as no such constructor
exits on the class.
> The solution is to move the {{messageConstructor}} variable inside the catch block. 
So we try to get/use the two arg constructor and if that fails then we try to get/use the
single argument constructor, which is the real logic of that try/catch block anyway.

This message was sent by Atlassian JIRA

View raw message