since ‎16-02-2017
‎10-12-2019
jineetv21622325
Level 1
Re: AEM/CQ - javax.xml.namespace can't resolve OSGI dependency
Avatar

jineetv21622325

jineetv21622325
- Adobe Experience Manager
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

Views

642

Likes

0

Replies

0
Re: AEM/CQ - javax.xml.namespace can't resolve OSGI dependency
Avatar

jineetv21622325

jineetv21622325
- Adobe Experience Manager
AEM v6.2, Uber Jar v6.2.0, archetype v10.

Views

642

Likes

0

Replies

0
Re: AEM/CQ - javax.xml.namespace can't resolve OSGI dependency
Avatar

jineetv21622325

jineetv21622325
- Adobe Experience Manager
smacdonald2008 What should be the dependency added in pom.xml to make it pick appropriate version?

Views

633

Likes

0

Replies

0
Re: AEM/CQ - javax.xml.namespace can't resolve OSGI dependency
Avatar

jineetv21622325

jineetv21622325
- Adobe Experience Manager
Using AEM 6.2, archetype 10 and using Uber Jar as well.

Views

646

Likes

0

Replies

0
Re: AEM/CQ - javax.xml.namespace can't resolve OSGI dependency
Avatar

jineetv21622325

jineetv21622325
- Adobe Experience Manager
Thanks smacdonald2008​, I did find the dependency by entering javax.xml.namespace and below is the result returned:Package: javax.xml.namespaceVersion: 0.0.0.fragment_xmlExported by: org.apache.felix.framework (0)Maven dependency: org.apache.sling org.apache.sling.fragment.ws 1.0.2 providedAnd in my bundle: it is showing me this - javax.xml.namespace,version=[1.0,2) -- Cannot be resolvedIf this is an version issue, can you please tell me what I should I do to make this package resolved?Many than...

Views

642

Likes

0

Replies

0
Re: AEM/CQ - javax.xml.namespace can't resolve OSGI dependency
Avatar

jineetv21622325

jineetv21622325
- Adobe Experience Manager
The bundle which resolves:javax.xml.namespace,version=0.0.0.fragment_xml from org.apache.felix.framework (0)The bundle which doesn't resolve:javax.xml.namespace,version=[1.0,2) -- Cannot be resolved

Views

639

Likes

0

Replies

0
Re: AEM/CQ - javax.xml.namespace can't resolve OSGI dependency
Avatar

jineetv21622325

jineetv21622325
- Adobe Experience Manager
Error log:5.06.2017 23:11:22.800 *ERROR* [qtp110252325-58675] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unable to resolve com.xyz.cq.support.core [515](R 515.2): missing requirement [com.xyz.cq.support.core [515](R 515.2)] osgi.wiring.package; (&(osgi.wiring.package=javax.xml.namespace)(version>=1.0.0)(!(version>=2.0.0))) Unresolved requirements: [[com.xyz.cq.support.core [515](R 515.2)] osgi.wiring.package; (&(osgi.wiring.package=javax.x...

Views

664

Likes

0

Replies

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

jineetv21622325

jineetv21622325
- Adobe Experience Manager
'm using AEM 6.2 and I'm currently implementing WebService. I included all dependency jars in OSGI bundle which I created externally and all dependency issue got resolved except one:javax.xml.namespace,version=[1.0,2) -- Cannot be resolvedWhen I checked in the maven using depfinder tool, it showed me as below: org.apache.sling org.apache.sling.fragment.ws 1.0.2 provided However, in my other custom project, the javax.xml.namespace is showing resolved state.I'm stuck in this situation and any poin...

Views

3.0K

Likes

0

Replies

17
Re: AEM Post Servlet Ajax call fails on first time call when page opened in new browser.
Avatar

jineetv21622325

jineetv21622325
- Adobe Experience Manager
When I change the second Ajax call method in function postCommentFunction() from POST to GET after adding doGet method in Java Servlet, this works.Not sure what it has to do with POST.

Views

655

Likes

0

Replies

0
Re: AEM Post Servlet Ajax call fails on first time call when page opened in new browser.
Avatar

jineetv21622325

jineetv21622325
- Adobe Experience Manager
I'm using jQuery from AEM itself.

Views

653

Likes

0

Replies

0
AEM Post Servlet Ajax call fails on first time call when page opened in new browser.
Avatar

jineetv21622325

jineetv21622325
- Adobe Experience Manager
I have a requirement to post a comment on successful authentication and I'm using AEM login mechanism as below:1. Login using AJAX call$(document).ready(function() { if(userName && password) { $.ajax({ type:'POST', url : path[0]+"/j_security_check", data: { j_username: userName, j_password: password, j_validate:"true" }, success: function(data, textStatus, jqXHR){ console.log("passed security authentication"); postCommentFunction(); }, error: function(xhr, textStatus) { console.log(textStatus); ...

Views

2.4K

Like

1

Replies

5
Likes given to
Likes from