Solved! Go to Solution.
Views
Replies
Total Likes
AEM does not have the libs (including CXF) to expose a web service. You have really 2 choices. Assume you want to expose JCR data as a web service. You can follow that link. It talks about what you need to do.
Or 2 - you can setup a web service on a web server (ie Tomcat) and code a Java bean and use Apache CXF and the JCR API. THe bean will expose a WSDL and use the JCR API to perform CRUD (Create, Replace, Update, and Delete) operations on the JCR Data.
[img]CQWSDL.png[/img]
Views
Replies
Total Likes
AEM does not have the libs (including CXF) to expose a web service. You have really 2 choices. Assume you want to expose JCR data as a web service. You can follow that link. It talks about what you need to do.
Or 2 - you can setup a web service on a web server (ie Tomcat) and code a Java bean and use Apache CXF and the JCR API. THe bean will expose a WSDL and use the JCR API to perform CRUD (Create, Replace, Update, and Delete) operations on the JCR Data.
[img]CQWSDL.png[/img]
Views
Replies
Total Likes
Thanks mate. I rather go with the 2nd option as the 1st seems to be too much of a hack.
Views
Replies
Total Likes
Could you please share the link?
Views
Replies
Total Likes
How to access JCR API from bean on tomcat? Please reply.
Views
Replies
Total Likes
I would also go with the option of setting up a separate Tomcat.
Getting Apache CXF to work as SOAP service within the OSGi runtime of AEM will be very complex, if not impossible due to dependency conflicts.
Take a look at Apache Mule, the concept is interesting!
Views
Replies
Total Likes
Try doing a bit of reading & learning: http://www.amazon.com/Beginning-Java-EE-Expert-Voice/dp/143024626X
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies