Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM 6.4 -> 6.5.6 : Apache felix framework 6.02 not resolving dependencies

sagar_verliani
Level 2
Level 2

Hi All,

 

In our upgrade project, We are unable to get header for javax Webservices called.

Seems like Apache felix framework bundle(5.6.1) was already providing that previously in 6.4

Now in 6.5, the same bundle is not having webservices related dependencies.

Do we have any documentation for this or any guidance available to resolve this.

 

We have added below dependencies in our core/pom.xml

<dependency>
<groupId>javax.xml.ws</groupId>
<artifactId>jaxws-api</artifactId>
<version>2.3.1</version>
</dependency>
<dependency>
<groupId>com.sun.xml.ws</groupId>
<artifactId>jaxws-rt</artifactId>
<version>2.3.1</version>
</dependency>
<dependency>
 
After adding this also we are getting following error in our project log:
20-10-28 07:59:47.472 ERROR [com.aem.project.core.service.impl.projectserviceimpl] WebServiceException {}
javax.xml.ws.WebServiceException: Provider com.sun.xml.internal.ws.spi.ProviderImpl not found
1 Accepted Solution
Anudeep_Garnepudi
Correct answer by
Community Advisor
Community Advisor

Hi @sagar_verliani 

This issue not related to AEM. Issue seems to be in Webservices along with Java11. Please go through below like. It might help.

https://stackoverflow.com/questions/54032558/jdk-11-jax-ws-provider-com-sun-xml-internal-ws-spi-prov...

AG

View solution in original post

19 Replies
santhosh_kumark
Community Advisor
Community Advisor

Hi @sagar_verliani ,

 

Hope this helpx article help you in fixing this issue.

https://helpx.adobe.com/in/experience-manager/kb/jaxws-webservice-calls-not-working-aem-65.html

https://stackoverflow.com/questions/54032558/jdk-11-jax-ws-provider-com-sun-xml-internal-ws-spi-prov...

This issue is may be due to the fact that CFX packages have been removed from AEM and you have to install those externally.

To resolve the issue, you can install the "cfx-bundles-1.0.zip" package which provides the minimal set of jar files for the 2.3.0 release of CXF DOSGi

 

Regards,

Santosh

Anudeep_Garnepudi
Community Advisor
Community Advisor

Hi @sagar_verliani 

Try below two methods. Hope one of them will work.

  1. Add <type>pom</type>  to dependency jaxws-rt<dependency>
    <groupId>com.sun.xml.ws</groupId>
    <artifactId>jaxws-rt</artifactId>
    <version>2.3.1</version>
    <type>pom</type>
    </dependency>
  2. Or upgrade to version 2.3.3

        <dependency>
        <groupId>com.sun.xml.ws</groupId>
        <artifactId>jaxws-rt</artifactId>
        <version>2.3.3</version>
        </dependency>

AG

sagar_verliani
Level 2
Level 2

Hi All,

 

Our project POM is pointing to jdk 1.8 and AEM Server is running on jdk 11, do you think if this is an issue?

Anudeep_Garnepudi
Community Advisor
Community Advisor

Hi @sagar_verliani 

If you have a local AEM instance try to run in Java 8 and see.

AG

Anudeep_Garnepudi
Community Advisor
Community Advisor

Hi @sagar_verliani 

Try adding below dependency.

<dependency>

    <groupId>com.sun.xml.ws</groupId>

    <artifactId>rt</artifactId>

    <version>2.3.1</version>

</dependency>

Hope this works!

AG

sagar_verliani
Level 2
Level 2
Hi, this didn't worked, but we have tried adding deoendencies as per adobe's article , now we are getting this error 2020-11-02 07:48:07.469 ERROR [com.aem.project.core.service.impl.projectServiceImpl] WebServiceException {​​​​​​​}​​​​​​​ javax.xml.ws.soap.SOAPFaultException: Fault string, and possibly fault code, not set at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:161) [org.apache.cxf.cxf-rt-frontend-jaxws:3.2.0]
Anudeep_Garnepudi
Correct answer by
Community Advisor
Community Advisor

Hi @sagar_verliani 

This issue not related to AEM. Issue seems to be in Webservices along with Java11. Please go through below like. It might help.

https://stackoverflow.com/questions/54032558/jdk-11-jax-ws-provider-com-sun-xml-internal-ws-spi-prov...

AG

View solution in original post

sagar_verliani
Level 2
Level 2
no this not the issue, issue is with AEM only and that to particularly with SOAP related services but we have fixed this.
sagar_verliani
Level 2
Level 2

Hi All,

 

We are getting null when fetching values of soapMessage or soapEnvelope or soapHeader.

This was working earlier in 6.4.

Now in 6.5 the javax.xml.ws dependency which is present OOTB bundle (servicemix jaxb api) is updated to v2.2.0 as opposed to v2.1.0 in 6.4 present in felix framework bundle OOTB

Need more inputs to solve this

@Anudeep_Garnepudi @santhosh_kumark @kautuk_sahni 

Anudeep_Garnepudi
Community Advisor
Community Advisor
Hi @sagar_verliani, try adding javax.xml.ws version 2.2.0 in Import-Package list and see.