Yes, I found that exactly. If I patch CXF to not complain about the
ArrayList size(), then CXF passes what should be the 19th parameter (a
Holder) as the 16th parameter, violating typing at runtime. It seems like
certain parts are simply missing. Every call does have a mix of headers,
in-params,
19 parameters?!?!? Jeesh… I think I'd be strongly considering running
wsdl2java with the -bareMethods parameters to flip to bare mode.Seriously,
consider it.
We'd likely need a test case for this. When you are getting that many
parameters, there is definitely some possibilities of get
Hi,
IIRC, the MessagePartInfo index is start from 0, so I don't think we should
change code in MessageContentsList.java to
super.get(key.getIndex()-1)
IMO, a narrow-down test case would be necessary and more helpful here.
Btw, when you use wsdl2java to generate the code, you can enable valida
Our CXF client consistently gets an IndexOutOfBoundsException
(java.lang.IndexOutOfBoundsException:
Index: 19, Size: 19) when handling a SOAP response which otherwise looks
valid. We're using CXF 2.7.5 with the wsdl2java Maven plugin to generate
client wrapper code.
The stack trace goes from
Hold
