AEM/CQ - javax.xml.namespace can't resolve OSGI dependency

@jineetv21622325 , I also faced similar error while upgrading from AEM 6.3 to 6.5 SP4. 

Error Log -

24.03.2020 15:09:40.573 *ERROR* [qtp1041007297-2360] org.apache.felix.http.jetty %bundles.pluginTitle: 
Cannot start (org.osgi.framework.BundleException: Unable to resolve com.XXX.XXXX.XXX [590](R 590.0): 
missing requirement [com.XXX.XXX.XXX [590](R 590.0)] osgi.wiring.package; 
(&(osgi.wiring.package=javax.xml.namespace)(version>=0.0.0)(!(version>=1.0.0))) 
Unresolved requirements: [[com.XXX.XXX.XXX [590](R 590.0)] 
osgi.wiring.package; (&(osgi.wiring.package=javax.xml.namespace)(version>=0.0.0)(!(version>=1.0.0)))])
org.osgi.framework.BundleException: Unable to resolve com.XXX.XXX.XXX [590](R 590.0): missing requirement

Reason - 

As you see in the error log above, Bundle Exception is due to failed OSGI Wiring. Version of javax.xml.namespace is not suffiecient or compatible enough. 

Solution -

• Find the version of the conflicted package exported by the System Bundle here - http://localhost:4502/system/console/bundles/0 
• Add the necessary entries to pom.xml so that requirement is fulfilled for the code build.
•  
   

  

smacdonald2008​, I found that if I include org.apache.axis2 dependency, the bundle shows unresolved for javax.xml.namespace. But on removing org.apache.axis2 dependency, the bundle goes in resolved state.

I'm implementing web service using Apache Axis 2 and I need to use this dependency for my project work.

Not sure what conflict it is creating with Apache Axis 2 API.

Thanks,

Jineet

AEM v6.2, Uber Jar v6.2.0, archetype v10.

smacdonald2008 What should be the dependency added in pom.xml to make it pick appropriate version?

I have done this from time to time when i need to get it to work But correct - the ideal way is to get it correct in the POM file!

Hi Scott,

this doesn't help if you need to do it again and again after every build :-)

Here is a tip (but you would need to do it each time you build the bundle) - open the bundle in ZIP tool. Open the  Manifest file.

Remove the version information beside the package - then it will pick up the available version in AEM.

Hi,

There's a version mismatch, so it looks like you compile against a wrong version of the AEM uber jar. What version of the uber.jar are you using and what version of AEM are you targetting? Or: what version of the AEM archetype are you using?

regards,

Jörg

Using AEM 6.2, archetype 10 and using Uber Jar as well.