SOAP Client in AEM 6.5 SP22

[diana-raileanu]

Hi everyone,

I need help setting up a brand new soap client. I have the wsdl generation done. I have added my jakarta dependencies:

<dependency>
    <groupId>jakarta.xml.soap</groupId>
    <artifactId>jakarta.xml.soap-api</artifactId>
    <version>3.0.2</version>
</dependency>
<dependency>
    <groupId>jakarta.xml.ws</groupId>
    <artifactId>jakarta.xml.ws-api</artifactId>
    <version>4.0.2</version>
</dependency>
<dependency>
    <groupId>jakarta.xml.bind</groupId>
    <artifactId>jakarta.xml.bind-api</artifactId>
    <version>4.0.2</version>
</dependency>
<dependency>
    <groupId>jakarta.activation</groupId>
    <artifactId>jakarta.activation-api</artifactId>
    <version>2.1.3</version>
</dependency>
<dependency>
    <groupId>jakarta.jws</groupId>
    <artifactId>jakarta.jws-api</artifactId>
    <version>3.0.0</version>
</dependency>

In core pom.xml I have also:

<bnd><![CDATA[
    Import-Package: jakarta.activation.*;version=0.0.0,jakarta.xml.*;version=0.0.0,jakarta.jws.*;version=0.0.0,*
    ]]></bnd>

They are then embedded in all module and I see them all active in bundle list:

However my bundle for this soap client is not resolving a dependency:

Any idea what other dependency am I missing?
Thank you in advance!

[arunpatidar]

Hi @diana-raileanu 

Please check if this helps

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/issue-with-osgi-bundle-in-... 

[diana-raileanu]

In this post, the java packages have been overwritten by boot delegation, that is totally different to my issue where one custom dependency is not resolving - this dependency is not included in aem OOTB, so the solution suggested there is not of any help. But anyway thank you @arunpatidar for looking into it.

[Tethich]

Hi @diana-raileanu 

Maybe you can leverage some of the properties for the boot delegation support and play around with them in your sling.properties file:
https://sling.apache.org/documentation/configuration.html#osgi-boot-delegation-support-1

Maybe org.osgi.framework.system.packages.extra=com.sun  or org.osgi.framework.system.packages.extra=com.sun.* ?

I also believe this thread could give you a direction to find a solution: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/issue-with-osgi-bundle-in-...

[giuseppebag]

If possible, you should try to embed or import the artifact that is responsible for the missing package.

To determine which artifact is importing or requiring a specific dependency in a Maven project, you can use the dependency:tree goal provided by the Maven Dependency Plugin. This tool generates a tree-like representation of all dependencies in your project, including transitive dependencies, and allows you to trace the origin of any specific dependency.

This will show only the parts of the dependency tree that include the specified artifact:

mvn dependency:tree -Dincludes=com.example:some-artifact

[diana-raileanu]

@giuseppebag I gave it a try with just package name com.sun.xml because I actually don't know which artifact is missing. When I google the missing dependency, the sources/suggestions are different based on if the soap client uses javax or the new namespace jakarta. And most common suggestion is to add com.sun.xml.ws » jaxws-ri dependency - but this is not a jar to embedded it so easy, so I tried embedding the dependencies specified in the jaxws-ri pom, but when I install them one by one, they don't get activated (status is always installed) as they require more dependencies, so after like 25 additional jars installed in bundle console, I stopped because I didn't see progress.