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 Mon, 14 Aug 2017 09:00:03 GMT

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

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

Github user semancik commented on the issue:

    https://github.com/apache/cxf/pull/297
  
    I was looking around how to construct a test for this. But I'm really puzzled. There seems
to be very little documentation about writing tests. And I could not find any test that would
be similar to what I'm trying to do.
    
    I have SOAP message that is causing the exception. It is a SOAP response from the server.
How do I create a simple test that just attempts to process the message, runs the interceptors
and checks the processed message?


> 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