osgi-jax-rs-connector is not in use anymore in AEM6.5 | Adobe Higher Education
Skip to main content
G
GanaG
Level 2
June 6, 2023
Resuelto

osgi-jax-rs-connector is not in use anymore in AEM6.5

  • June 6, 2023
  • 1 respuesta
  • 958 visualizaciones
I am trying to expose Restful Services in AEM6.5.I am using jersey-all-2.22.2,publisher-5.3.1,provider-security-2.2 API.

I am getting "HTTP ERROR 503 Jersey is not ready yet!". Find screenshot1 is attached for the same.

 But looks like osgi-jax-rs-connector part of jersey is not in use anymore. https://github.com/hstaudacher/osgi-jax-rs-connector

Find screenshot2 is attached for the same.

What is the alternative API, alternative OSGI-REST Connector which can be used instead of osgi-jax-rs-connector in AEM6.5

Thanks,

Gana

Este tema ha sido cerrado para respuestas.
Mejor respuesta de ManviSharma

Hi,

 

In AEM 6.5, the recommended alternative to the osgi-jax-rs-connector for exposing RESTful services is the Adobe Granite REST API, which is built-in and does not require an external connector. It leverages AEM's Sling framework and allows you to define and implement RESTful services directly within AEM using scripts, servlets, or Java classes.

 

Reference docs[1]

[1]

https://experienceleague.adobe.com/docs/experience-manager-screens/user-guide/developing/rest-api.html?lang=en

 

1 respuesta

ManviSharma
Adobe Employee
ManviSharmaAdobe EmployeeRespuesta
Adobe Employee
June 6, 2023

Hi,

 

In AEM 6.5, the recommended alternative to the osgi-jax-rs-connector for exposing RESTful services is the Adobe Granite REST API, which is built-in and does not require an external connector. It leverages AEM's Sling framework and allows you to define and implement RESTful services directly within AEM using scripts, servlets, or Java classes.

 

Reference docs[1]

[1]

https://experienceleague.adobe.com/docs/experience-manager-screens/user-guide/developing/rest-api.html?lang=en

 

    G
    GanaGAutor
    Level 2
    June 7, 2023

    Hi,

    By using Adobe Granite REST API, can we have custom paths other than default path "api". Find the screenshot attached for reference.

    Also, can we have java method level services exposed similar to what we can achieve with osgi-jax-rs-connector?

    Is Adobe Granite REST API uses sling exporter approach to expose the RESTful services?

     

    Términos y condicionesAccessibility statement

    Loading footer...