Suggestion required from experts | Community
Skip to main content
arnab26
arnab26
Level 2
October 16, 2015
Solved

Suggestion required from experts

  • October 16, 2015
  • 8 replies
  • 1467 views

Hi All,

I need a suggestion from AEM experts. We are working on ecommerce development. We have integrated AEM5.6.1 with Hyris, using custom java REST API's. 

Now we are planning to migrate this from AEM5.6.1 to AEM6.1 (jsp to sightly). Can someone please suggest whether this will be feasible approach to migrate this kind of dynamic website where almost each line will have a call to API methods for content rendering.

 

Thanks,

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Hi,

Migrating to sightly isn't a problem per se, be it a very dynamic or a static site. It just enforces a strong separation of concerns between the markup creation (by sightly) and the model/the logic (probably implemented using sling models). And that's always a good idea.

kind regards,
Jörg

8 replies

Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
October 16, 2015

If your current application is already built in AEM, nothing wrong in upgrading the version !

edubey
edubey
Level 10
October 16, 2015
Its good to have the components in sightly, taking the overall consumption of time it will be easy for the project maintenance as well for the UI development. Custom xtype are independent of JSP or sightly so there won't be any effect. Now the time it will consume to convert into sightly totally depend upon you and your development team.
joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi,

Migrating to sightly isn't a problem per se, be it a very dynamic or a static site. It just enforces a strong separation of concerns between the markup creation (by sightly) and the model/the logic (probably implemented using sling models). And that's always a good idea.

kind regards,
Jörg

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

You are on the correct path - you can port these components to Sightly. In AEM 6.1 - you can use either JSP or Sightly. It supports both ways for component development. 

arnab26
arnab26Author
Level 2
October 16, 2015

Thanks.

The environment is already upgraded to AEM6.1 from AEM5.6.1. I wanted to know whether this is a good thought to migrate all components into sightly. Keeping in mind "How much time consuming this will be?", "Is it good to have such kind of dynamic website in sightly?, "Will all functionality work?(such as custom xtypes)?

 

Regards,

Arnab

Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
October 16, 2015

Hi Arnab,

2 different things here..

Sightly : Is the templating engine and it just controls the view script. So even without changing it from jsp to sightly it works as is and going forward any new components can happen in sightly. However, it is good to migrate slowly to sightly to be on safe if the backward compatibility is removed in future versions of AEM. 

Xtypes: xtypes really belong to 'dialog' and unless you want to support Touch UI dialog, you dont have to worry about custom xtypes. If you have to create Touch UI dialogs, then you may have to do some rework there.

Both things are not mandatory with the upgrade. Its upto the requirement/business what needs or if you would like to use the new features !

 

Hope it helps !

arnab26
arnab26Author
Level 2
October 16, 2015

Thanks.

The environment is already upgraded to AEM6.1 from AEM5.6.1. I wanted to know whether this is a good thought to migrate all components into sightly. Keeping in mind "How much time consuming this will be?", "Is it good to have such kind of dynamic website in sightly?, "Will all functionality work?(such as custom xtypes)?

 

Regards,

Arnab

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

Its not required to write component in Sightly when using AEM 6.1. JSP is fully supported. 

Terms & ConditionsAccessibility statement

Loading footer...