A solution that requires modifying the Blogs portlet by overriding several core JSPs and a Struts action is best developed as:
A single hook plugin
A Struts hook plugin and a JSP hook plugin
A single Ext plugin
A Struts hook plugin and several JSP hook plugins
Color schemes are defined in:
liferay-color-scheme.xml
portal-ext.properties
liferay-look-and-feel.xml
liferay-plugin-package.properties
An Ext plugin should be used to:
Create aportlet
Create a theme
Overwrite a portal JSP file
Create a servlet filter
Modify coreportletdeployment descriptors
Create a web service
The recommended way to cleanly redeploy an Ext plugin is to:
Remove the plugin WAR file from the server and redeploy
Set ext.redeploy .enabled to''true''
Remove the ext-plugin-[nameof plugin],xml file in the deployed Liferay application and redeploy
Start from a clean instance of the server and redeploy
Portlets that extend MVCPortlet require annotations on action methods.
True
False
The recommended way to automatically add tags when creating web content is to:
Create a model listener in a hook plugin and implement the onAfterCreate() method
Create a model listener in a hook plugin and implement the onBeforeCreate() method
Create an Ext plugin to extend and override JournalArticleLocalServicelmpI
Create a hook plugin and use a service wrapper to extend JournalArticleLocalService
The Plugins SDK uses:
portal-service.jar
JAR files from the user's home directory
portal-impl.jar
portal-plugin.jar
Only an Ext plugin can:
Override language keys
Modify the initialization parameters of a coreportlet
Create a model listener
Override a JSP
Override Liferay services