Thank you Fabian foe your help,

Now it works for us.

We have to create a fragment to export the package CXF JAWS SPI with 7.3 version.

After that we use the CXF plugin in 3.3.0 version.

But for the maven dependency we use the 3.2.5 version.

Here the maven dependencies we have use :

<dependency>

    <groupId>javax.xml.bind</groupId>

    <artifactId>jaxb-api</artifactId>

    <version>2.3.1</version>

    <scope>provided</scope>

</dependency>

<dependency>

    <groupId>javax.xml.ws</groupId>

    <artifactId>jaxws-api</artifactId>

    <version>2.3.1</version>

    <scope>provided</scope>

</dependency>

<dependency>

    <groupId>javax.jws</groupId>

    <artifactId>javax.jws-api</artifactId>

    <version>1.1</version>

    <scope>provided</scope>

</dependency>

 <dependency>

        <groupId>org.apache.cxf</groupId>

        <artifactId>cxf-rt-frontend-jaxws</artifactId>

        <version>${cxf.version}</version>

        <scope>provided</scope>

</dependency>

The important is to use the same dependencies of Liferay to have no conflict.

Thank you SO much for your help Fabian,

Eric.

Hi Eric,

Indeed, you need to create a fragment to have an existing bundle export it.

In my DXP 7.2 setup, I got this:

Bundle-Name: cxf-provider-fragment
Bundle-SymbolicName: com.liferay.sample.fbo.cxf.provider.fragment
Fragment-Host:  com.liferay.portal.remote.soap.extender.impl
Export-Package: org.apache.cxf.jaxws.spi;version=3.2.5

You'll have to use the gogo shell to check the actual version of the package you are exporting.

My strategy relies on having my soap client use the same cxf version as liferay.

Sorry, I'd have to create a proper sample project for this. It's not inside of a repo I can share.

Kind regards,

Fabian

Hi Fabian,

In Liferay DXP 7.3 the version is 4.0.23 and the version of CXF is 3.2.14, so we create the fragment like this : 

Bundle-Name: Liferay Portal Remote SOAP Extender Implementation Fragment
Bundle-SymbolicName: test.remote-soap-extender
Bundle-Version: 1.0.0
Fragment-Host: com.liferay.portal.remote.soap.extender.impl;bundle-version="4.0.23"
Export-Package: org.apache.cxf.jaxws.spi;version=3.2.14

And in our module we import the same dependency (3.2.14) :

		<dependency>
		    <groupId>org.apache.cxf</groupId>
		    <artifactId>cxf-rt-frontend-jaxws</artifactId>
		    <version>3.2.14</version>
		    <scope>provided</scope>
		</dependency>

It seems to be better but after (the compilation is OK) but we need to exclude many packages:

Import-Package:\
	!com.sun.*,\
	\
	!javax.validation.*,\
	\
	!net.sf.cglib.proxy.*,\
	\
	!org.apache.abdera.*,\
	!org.apache.aries.*,\
	!org.apache.cxf.aegis.*,\
	!org.apache.cxf.ws.policy.*,\
	!org.apache.neethi.*,\
	!org.apache.velocity.*,\
	!org.apache.xml.resolver.*,\
	!org.apache.xmlbeans.*,\
	\
	!org.junit.*,\
	\
	!org.jvnet.fastinfoset.*,\
	!org.jvnet.staxex.*,\
	\
	!org.osgi.service.blueprint.*,\
	\
	!org.relaxng.datatype.*,\
	\
	!org.slf4j.spi.*,\
	\
	!org.springframework.*,\
	\
	org.apache.cxf.jaxws.spi,\
	*

And we still have an error with operation not found in wsdl...

After many hours and many days of work, we don't find a issue to this problem.
The same module works in java 8. Will it be possible to share an exemple of a SOAP client in Maven with java 11 ?

Eric.

Here are the errors we have in the logs :

The javax.jws.WebService annotation was already loaded by another classloader. Please check if there are multiple versions of the web service annotation jar in your classpath.
...
No method was found for the WSDL operation {http://xmlns.example.com/...