AMS to ACS Migration - Static template and JSP to Editable template

[nj2]

Hi, 

We are working on a migration project fom AMS to ACS. Our current project heavily relies on static template that are build using JSP. Could you please clarify the following question with respect to migration -

1. Is there any way to retain JSP as-is and still migrate from static template to editable template?
2. Is it necessary to migrate JSP to HTL
3. Are there any Adobe recommened migration guide for converting JSP based template to HTL
4. Is it necessary to convert components using JSP to HTL

We are looking for the best practices and any possible workarounds that would allow us to efficiently transition to ACS without a complete rewrite.

Any insight, recommendations would be appreciated.

Thanks, 

[chaudharynick · Accepted solution]

Hi @nj2 

1. Is there any way to retain JSP as-is and still migrate from static template to editable template?

no, editable templates will require HTL and new code and JSPs are not recommended at all now and best would be to migrate to HTL
2. Is it necessary to migrate JSP to HTL

AEM officially supports and promotes HTL now and have the better control on the html and proper segregation of the logic with java and html.
3. Are there any Adobe recommened migration guide for converting JSP based template to HTL

You can refer to AEM Modernization Tools(https://opensource.adobe.com/aem-modernize-tools/) it will help you in this.
4. Is it necessary to convert components using JSP to HTL

Yes, let me summarize the benefits of HTL

1. HTL is faster in execution as it avoids extra Java compilation
2. It has Built-in XSS (Cross-Site Scripting) protection
3. The Readability is better and cleaner, HTML-like syntax for frontend developers

4. Separation of logic & presentation (Uses Sling Models & data-sly-use)

5. Supports reusability via HTL templates & data attributes

6. It's a standard and JSP is deprecated for component development now.