Skip to main content
Level 7
June 20, 2023
Respondido

Comparing Groovy Console, running Groovy script from command prompt, Sling Servlet, Apache Sling Pipes

  • June 20, 2023
  • 1 resposta
  • 637 Visualizações

Hey all,

 

If there is any scenario like: To modify the jcr property of a component or a template in whole project(Usually arises during AEM upgrade or to fix some bug in all the existing pages), which is better?

1: Writing Sling Servlet

2: Use of Groovy Console

3: Use of Standalone Groovy script from command prompt(Since system has latest groovy installed

4: Apache Sling Pipes.

 

@krishna_sai 

Este tópico foi fechado para respostas.
Melhor resposta por Tanika02

@mahesh_gunaje  - 

 

  • If the changes are relatively simple and limited in scope, using the Groovy Console or a standalone Groovy script can be effective.

 

  • For more complex or extensive modifications, writing a Sling Servlet or utilizing Apache Sling Pipes would provide better control and flexibility.

 

I've lately used sling pipes for similar purposes, and you can learn more about them by reading wonderful articles : 

 

https://blog.developer.adobe.com/apache-sling-pipes-real-world-examples-1c5691b9084e 

 

https://www.linkedin.com/pulse/aem-make-your-lazy-developer-life-easier-sling-pipes-peltier/ 

1 Resposta

Tanika02
Tanika02Resposta
Level 7
June 20, 2023

@mahesh_gunaje  - 

 

  • If the changes are relatively simple and limited in scope, using the Groovy Console or a standalone Groovy script can be effective.

 

  • For more complex or extensive modifications, writing a Sling Servlet or utilizing Apache Sling Pipes would provide better control and flexibility.

 

I've lately used sling pipes for similar purposes, and you can learn more about them by reading wonderful articles : 

 

https://blog.developer.adobe.com/apache-sling-pipes-real-world-examples-1c5691b9084e 

 

https://www.linkedin.com/pulse/aem-make-your-lazy-developer-life-easier-sling-pipes-peltier/