[
https://issues.apache.org/jira/browse/CXF-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102921#comment-16102921
]
ASF GitHub Bot commented on CXF-7455:
-------------------------------------
Github user semancik commented on the issue:
https://github.com/apache/cxf/pull/297
Looks like this has been already worked around in the winrm4j project. I
was not aware of that. So I might actually cancel the pull request later on.
Please, bear with me, I need some time to explore. However, I would say that it
is rather sad that it is easier to work around the problem than to deal with
all this checkstyle pain, unit tests and so on.
> 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)
