Questions Tagged With webservice

AXIS web service client calls LinkageError with Policy

Alex Suter — Thu, 12 Mar 2020 01:45:20 -0400

Since Axon.ivy 8.0 you may have problems with AXIS web service client calls, which you will notice in the log as follows:

LinkageError: loader constraint violation: loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @4797c3e2 wants to load class org.apache.neethi.Policy. A different class with the same name was previously loaded by org.eclipse.osgi.internal.loader.EquinoxClassLoader @59b5251d. (org.apache.neethi.Policy is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @59b5251d, parent loader 'platform')

This problem occurs in combination with web service policies. To fix this issue, you need to migrate to the CXF Web Service Client technology - the AXIS stack is deprecated.

We have invested heavily in the new CXF technology in the Web Service Call Stack . If you have any problems with CXF, please contact us. We will take our time and make the CXF stack even better 💪!

CXF Web Service Client improvements in 8.0.3

Alex Suter — Thu, 05 Mar 2020 02:33:11 -0500

By default CXF Web Service Calls runs by default with HttpUrlConnection of Java. HttpUrlConnection is limited when it comes to authenticate against a NTML web service.

CXF provides the ability to change the implementation of the connection itself to org.apache.http.nio.client.HttpAsyncClient. Besides the full support of NTML it also provides better performance. Due that fact we changed the default connection to HttpAsyncClient of CXF Web Service Calls.

There are no known compatibility issues between these to implementations. If you face one, please contact us. And you are always still able to fallback by setting the use.async.http.conduit to false on the Web Service Client.

How to use WS-Addressing in a webservice call?

Alex Suter — Wed, 21 Feb 2018 10:36:38 -0500

I need to use web service standard WS-Addressing to call a web service. How can I use it?