Glen Mazza wrote:
>
>
> Ronald Pieterse wrote:
>>
>> UnsupportedOperationException from the <jaxws:outInterceptors> I am
>> using.
>> If I take the outInterceptors and outFaultInterceptors stuff out it works
>> fine.
>> Is there something I should have done or changed?
>>
>
> Are you using WS-Security? I would check to see that Maven doesn't
> download two BouncyCastle jar dependencies--I noticed that problem
> recently: https://issues.apache.org/jira/browse/CXF-1726.
>
> If that's not it, I would still scrutinize the libs that are downloaded by
> Maven in 2.0.8 (or between 2.0.5 and 2.0.8)--you might see another
> duplication--for some reason, two different versions of the same
> dependency downloaded, causing CXF to activate the older JAR without the
> operation that its looking for.
>
> HTH,
> Glen
>
>
I am importing WS-Security and you are right about Bouncy: it was there
twice. However, this was the only jar that was duplicated and if I fix my
classpath it still throws the same exception :-(
So the problem remains: when I remove the following part from my bean
declaration it works, but then I'm missing my custom header:
...
<jaxws:outInterceptors>
<ref bean="soapHeaderSetter15" />
</jaxws:outInterceptors>
<jaxws:outFaultInterceptors>
<ref bean="soapHeaderSetter15" />
</jaxws:outFaultInterceptors>
...
--
View this message in context:
http://www.nabble.com/upgrade-from-2.0.5-to-2.0.8-%3A%3A-%3Cjaxws%3AoutInterceptors%3E-throws-exception-tp18769193p18808199.html
Sent from the cxf-user mailing list archive at Nabble.com.
