cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-7455) IndexOutOfBoundsException when message part is missing
Date Wed, 26 Jul 2017 15:35:01 GMT

    [ https://issues.apache.org/jira/browse/CXF-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101822#comment-16101822
] 

ASF GitHub Bot commented on CXF-7455:
-------------------------------------

GitHub user semancik opened a pull request:

    https://github.com/apache/cxf/pull/297

    [CXF-7455] Tolerate missing message part

    

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

    $ git pull https://github.com/Evolveum/cxf CXF-7455

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

    https://github.com/apache/cxf/pull/297.patch

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

    This closes #297
    
----

----


> IndexOutOfBoundsException when message part is missing
> ------------------------------------------------------
>
>                 Key: CXF-7455
>                 URL: https://issues.apache.org/jira/browse/CXF-7455
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 3.1.12
>            Reporter: Radovan Semancik
>
> When SOAP response from the server does not include a part which is defined in the WSDL,
the the following exception is thrown:
> {code}
> Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> 	at java.util.ArrayList.rangeCheck(ArrayList.java:653)
> 	at java.util.ArrayList.get(ArrayList.java:429)
> 	at org.apache.cxf.message.MessageContentsList.get(MessageContentsList.java:80)
> 	at org.apache.cxf.jaxws.interceptors.HolderInInterceptor.handleMessage(HolderInInterceptor.java:69)
> ...
> {code}
> Yes, this is violation of the specs. Parts should not be missing. However, there are
bad servers out there (e.g. Windows 2008 WinRM). Throwing exception like this prohibits the
client to handle the situation. Which breaks projects such as winrm4j when talking to old
windows boxes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message