Ext plugins are deprecated for Liferay DXP 7.1 and should only be used if
absolutely necessary.
The following app servers should be used for Ext plugin development in
Liferay DXP:
In most cases, Ext plugins are not necessary. There are, however, certain cases
that require the use of an Ext plugin. Liferay only supports the following Ext
plugin use cases:
Providing custom implementations for any beans declared in Liferay DXP’s
Spring files (when possible, use
service wrappers
instead of an Ext plugin). Liferay DXP 7.1 removed many beans, so make sure your
overridden beans are still relevant if converting your legacy Ext plugin
(how to ).
Overwriting a class in a Liferay DXP 7.1 core JAR. For a list of core JARs, see
the Finding Core Artifacts
section
(how to ).
Modifying Liferay DXP’s web.xml file
(how to ).
Adding to Liferay DXP’s web.xml file
(how to ).
Note: In previous versions of Liferay Portal, you needed an Ext plugin to
specify classes as portal property values (e.g.,
global.starup.events.my.custom.MyStartupAction), since the custom class had to
be added to the portal class loader. This is no longer the case in Liferay DXP 7.1
since all lifecycle events can use OSGi services with no need to edit these
legacy properties.
Ext plugins are used to customize Liferay DXP’s core functionality. You can learn
more about what the core encompasses in the
Finding Core Artifacts
article section. In this section, you’ll learn how to
You can also dive into the
Anatomy of an Ext Plugin
to familiarize yourself with its structure.
You’ll start by creating an Ext plugin.