EXT Module run time dependencies Liferay 7.2EXT Module run time dependencies Liferay 7.2https://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1184887202024-03-28T21:19:18Z2024-03-28T21:19:18ZRE: EXT Module run time dependencies Liferay 7.2Olaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184944852020-02-13T08:24:49Z2020-02-13T08:24:49Z<div class="quote-title">yogesh chandra:</div><blockquote><br />Hi,<br />I have done customization in LDAPUserExporterImpl we are updating our custom table during exportUser method call . To updating custom table I have used entity's LocalServiceUtil to update the table. Do you have other ways to do customization in LDAPUserExporterImpl ??</blockquote>If you mean that you've used UserLocalService: You can add any code using ServiceWrappers. Any *LocalServiceUtil classes are just static lookup classes for the actual service and absolutely don't need to be touched. In fact, you shouldn't even use them in the OSGi world any more, rather use a @Reference to the service you need - this will take care of proper dependency management.<br />Your short description sounds like you won't need to do anything on the LDAP-side. But if you look at the 7.2 LDAPUserExporterImpl implementation, it contains several references that would allow you to provide alternative implementations, e.g. (but not limited to) <a href="https://github.com/liferay/liferay-portal/blob/master/modules/apps/portal-security/portal-security-ldap-impl/src/main/java/com/liferay/portal/security/ldap/internal/exportimport/LDAPUserExporterImpl.java#L467">one to a PortalToLDAPConverter</a> service with a quite <a href="https://github.com/liferay/liferay-portal/blob/master/modules/apps/portal-security/portal-security-ldap-api/src/main/java/com/liferay/portal/security/ldap/exportimport/PortalToLDAPConverter.java">small API</a>. Anything declared a @Reference in that file is a dynamic component that you could implement as well, without any need for Ext - it'll just be a standard OSGi bundle.Olaf Kock2020-02-13T08:24:49ZRE: EXT Module run time dependencies Liferay 7.2yogesh chandrahttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184940972020-02-13T06:13:21Z2020-02-13T06:13:21ZHi,<br />I have done customization in LDAPUserExporterImpl we are updating our custom table during exportUser method call . To updating custom table I have used entity's LocalServiceUtil to update the table. Do you have other ways to do customization in LDAPUserExporterImpl ??yogesh chandra2020-02-13T06:13:21ZRE: EXT Module run time dependencies Liferay 7.2David H Nebingerhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184859382020-02-12T14:31:47Z2020-02-12T14:31:47ZA standard part of our Upgrade Assessment package for Liferay EE/DXP users is to review plugin use and, when we find an EXT plugin, emphasize that it should be eliminated and replaced with standard OSGi-based implementations.<br /><br />We do this because the EXT is one of the biggest barriers to upgrading Liferay, and it was often used incorrectly to affect change in the portal. Eliminating the EXT plugins makes future upgrades easier and discards poor design/implementation details.David H Nebinger2020-02-12T14:31:47ZRE: EXT Module run time dependencies Liferay 7.2Olaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184894572020-02-12T12:43:55Z2020-02-12T12:43:55Z<div class="quote-title">yogesh chandra:</div><blockquote><br />I am upgrading Liferay 6.2 to Liferay 7.2 and I have EXT written in Liferay 6.2 which I want Upgrade in Liferay 7.2.<br /></blockquote>My recommendation is to not upgrade your ext, but figure out the reason why you wrote it in the first place, then evaluate if some of the many new extension points can be used to implement a less invasive plugin than ext. Ext is notoriously hard to maintain, needs to be reevaluated even on minor updates, and targets the implementation that has no guarantee of stability. Most likely, the code that you've been targeting has been changed between 6.2 and 7.2 anyway.<br />On top of that, I see no reason at all for a UserExtLocalServiceUtil in the first place, not even on 6.2 - it's just forwarding calls to the appropriate service, and ServiceWrappers have been around forever. This strengthens my recommendation from above. My assumption is that you won't need an ext at all. And if you do, it will be a lot smaller than in the past, accompanied with additional standard plugins that target the API.<br />Let us know the underlying problems that your ext used to solve, and we might point you to the appropriate extension points.Olaf Kock2020-02-12T12:43:55ZEXT Module run time dependencies Liferay 7.2yogesh chandrahttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184887192020-02-12T11:16:21Z2020-02-12T11:16:21ZHi,<br />I am upgrading Liferay 6.2 to Liferay 7.2 and I have EXT written in Liferay 6.2 which I want Upgrade in Liferay 7.2.I have created a new EXT project in Liferay 7.2 and customized all the classes required. After deployment of EXT, it's in Active state in GOGO shell. The issue I am facing with run time dependencies like "java.lang.NoClassDefFoundError