@kautuk_sahni unfortunately the suggestions didn't help solve my issue, so now I am trying to build a brand new client with latest jakarta dependencies and have that deployable in AEM. But even this is not yet finished. When I have that working I will post here the solution, and maybe even create a ...

@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 a...

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 lookin...

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>jaka...

We need it as a soap client implementation. We can't switch to rest as the endpoint service doesn't support it

@daniel-strmecki can you please share what implementation did you switch to? We are not bound to CXF and if we can achieve the same using other client implementation, we would gladly change this.Thank you in advance,Diana

Hi, AEM 6.5 SP22We are trying to upgrade CXF (3.3.5 is the current version) to 4.0.7 (latest version that support jdk 11). But once we upgrade the version, the bundles start to have dependencies issues. We've tried adding the compile dependencies both required and optional specified in https://mvnre...