Foren

Liferay 6.2 + AngularJS vs Liferay 7.0 + AngularJS

thumbnail
Nurul Amin, geändert vor 7 Jahren.

Liferay 6.2 + AngularJS vs Liferay 7.0 + AngularJS

New Member Beiträge: 8 Beitrittsdatum: 27.11.15 Neueste Beiträge
I heard, it is easier to write AngularJS portlet with Liferay 7.0 (DXP) compared to Liferay 6.2.

Is it true? Why?

As Liferay natively is based on AUI, I was expecting effort to use AngularJS in Liferay 6.2 or 7.0 is similar.

What do you think?
thumbnail
David H Nebinger, geändert vor 7 Jahren.

RE: Liferay 6.2 + AngularJS vs Liferay 7.0 + AngularJS

Liferay Legend Beiträge: 14919 Beitrittsdatum: 02.09.06 Neueste Beiträge
I think the AMD loader is the part that should make it easier, making it possible to quickly add new JS extensions.

From a portlet perspective, they are similar in implementation and similar in problems.
thumbnail
Nurul Amin, geändert vor 7 Jahren.

RE: Liferay 6.2 + AngularJS vs Liferay 7.0 + AngularJS

New Member Beiträge: 8 Beitrittsdatum: 27.11.15 Neueste Beiträge
Thanks for your reply.

AMD loader. Okay.

It would be great, if you can explain a bit more.

Thanks in advance.
Ricardo Legorreta, geändert vor 7 Jahren.

RE: Liferay 6.2 + AngularJS vs Liferay 7.0 + AngularJS

New Member Beiträge: 9 Beitrittsdatum: 03.12.15 Neueste Beiträge
I could integrated AngulrJS with Liferay 6 with no problem.

Does anybody has experience t migrate AngularJS to Liferay DXP? Is there any POC?

Thanks,
thumbnail
Ujjainee Sarkar, geändert vor 7 Jahren.

RE: Liferay 6.2 + AngularJS vs Liferay 7.0 + AngularJS

Regular Member Beiträge: 127 Beitrittsdatum: 20.07.16 Neueste Beiträge
Hello Ricardo,
Did you find any poc for migration? I have also migrated my angular Js portlets from Liferay 6.2CE to Liferay DXP with the help of Liferay Code Upgrade tool but none of the functions are working like before. Do you have any solution for that?
thumbnail
David H Nebinger, geändert vor 7 Jahren.

RE: Liferay 6.2 + AngularJS vs Liferay 7.0 + AngularJS

Liferay Legend Beiträge: 14919 Beitrittsdatum: 02.09.06 Neueste Beiträge
Remember that any URLs you invoke against the back end will be prefixed with "/o", so like "/o/my-angular-portlet/xxx" sort of thing.