The method to define a column in a layout template is
$layout.createColumn()
$layout.defineColumn()
$processor.processColumn()
$layout.addColumn()
The JavaScript method that executes after all the portlets on the page have finished loading is:
Liferay.Portlet.ready(fn)
AUI().ready(fn)
Liferay.on('allPortletsReady',fn)
None of the above
A JSR-286 standard portlet extends
LiferayPortlet
MVCPortlet
GenericPortlet
StrutsPortlet
Any Java class
Thecompanyld" is a(n)
Portal instance
Organization
Site
Team
Site administrators would like to search for web content based on the review date. The review date is not currently indexed when web content is published. The recommended way to add the review date to the search index is to:
Create an Ext plugin and overwrite the Journal indexer to index the review date
Create a hook plugin and override the Journal service to index the review date
Create a hook plugin and override the edit article Struts action to index the review date
Create a hook plugin and implement an indexer post processor to index the review date
The recommended way to add new functionality in Liferay is to
Create Ext plugins
Createportlet, theme, layout template or hook plugins
Modify Liferay's source code directly
All of the above
Instanceable portlets: (Please select all correct answers.)
Have unique preferences perportlet
Can be added to a page multiple times
Share the same data within the same site
Can be displayed in the Control Panel
Share the same data on the same page
To generate remote services with Service Builder
Pass the switch "-Dremote-service=true" to the Ant "build-service" target
Set the attribute "remote-service'' to "true" on the "entity" element in service,xml
Set the attribute "remote-service" to "true" on the "service-builder" element in service.xml
The method to embed the non-instanceable Language portlet with the name "82" in a theme is
$theme.include("82")
$theme.runtime("82")
$theme.runtime("82_INSTANCE_abcl23")
$theme.include("82_INSTANCE_abcl23")
The method to embed a portlet in a layout template is:
$layout.addPortlet()
$processor.processPortlet()
$layoutembedPortlet()
$layout. process PortIet()
Portlet events are distributed to portlets on different pages by setting the property:
portlet.event.distribution=all-pages
event.distribution =all-pages
portlet.event.distribution=layout-set
No specific property setting is required
In a JSP that includes the <liferay-theme: defineObjects /> tag, the method to check permissions is:
permissionChecker.hasPermissionO
portalUtil.getPermissionChecker().hasPermission()
permissionUtil.hasPermission()
renderRequest.getPermissionChecker().hasPermission()
The portlet lifecycle includes the methods: (Please select all correct answers.)
destroy ()
processEvent()
service()
render()
serveResource()
processAction()
The recommended way to turn off portlet borders in a custom theme is to:
Modifyportlet.vm to hide theportletborders
Set the theme setting "portlet-setup-show-borders" to "false"
Create a JSP hook that overrides port!et_wrapper.jsp to hide theportletborders
Set the portal property "portlet.setup.show.borders" tofalse"
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 create new methods in a core service is to use a service wrapper hook.
True
False
The recommended way to implement a new SSO solution that captures the SSO header is to:
Create an Ext plugin that adds a sen/let filter to capture the SSO header
Create a hook plugin that implements a servlet filter to capture the SSO header
Modify the portal source code and create an SSO servlet filter in the portal to capture the SSO header
Create a hook plugin to override the Struts action for the Loginportletto capture the SSO header
Service Builder is able to: (Please select all correct answers.)
Generate Hibernate configuration files
Generate base implementations of models, services, persistence and basic finders
Generate struts-config.xml and tiles-defs.xml
Generate web services
A hook plugin can extend and override: (Please select all correct answers.)
Core portal Struts actions
CoreportletStruts actions
Portletplugin Struts actions
Layout template Struts actions
Given the service.xml: <entity name="AcmeItem" local-service = "true'' remote-service="false"> <column name= "acmeltemld" type= "long' primary= "true" /> <column name= groupld" type="long" /> </entity> The generated classes include: (Please select all correct answers.)
AcmeltemServiceUtil
AcmeltemModel
AcmeltemLocalServiceUtil
AcmeltemJSONSerializer
AcmeltemPersistencelmpI
The hooks that can import classes from the plugin class loader are: (Please select all correct answers.)
Auto login hooks
JSP hooks
Service wrapper hooks
Servlet filter hooks
Struts action hooks
indexer post processor hooks
When adding new users to Liferay, the form will display the Details, Organizations and Personal Site sections based on the following property in portal.properties: users.form.add.main =detaiIs,organizations,personal-site The "users.form.add.main" property is listed in the liferay-hook_6_l_0.dtd as a portal property that can be overridden with a hook. Deploying a hook with the following property in the portal.properties file will remove the Personal Site section: users.form.add.main =details,organizations
Hook plugins can only override core JSPs, services, language keys and Struts actions
An Expando is
A tool for writing newportlets in Liferay
A code generator which generates services based on service.xml
A service in Liferay which allows you to dynamically define a collection of data
A new administrative interface in 6.1
The recommended way to implement code that only runs once to modify columns in the database is with a(n):
GlobalStartupAction
ServicePreAction
UpgradeProcess
ServicePostAction
VerifyProcess
GlobalShutdownAction
The bundled property file that contains settings for a development environment is
portal-ext. properties
portal-developer, properties
developer, properties
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
To customize the User service in a hook plugin, create a class that extends
UserServicelmpI
UserServiceBaseImpI
UserService
UserServiceWrapper
The recommended way to override multiple JSPs in the Documents and Media portlet is to
Create a separate hook plug in for each JSP
Create an Ext plugin
Create a hook plugin that contains all the JSPs
Copy them directly into Liferay
Default rankings in the Message Boards portlet are set as portlet preferences. To make all new instances of the portlet display custom rankings, it is recommended to
Navigate to System Defaults in the Control Panel and update theportletpreferences
Create a hook plugin that modifies the defaultmessage.board.ranks portal property
Create an Ext plugin that contains the desired configuration inportlet-ext.xml
Create a JSP hook that overrides the rankings for all instances of the Message Boardsportlet
The method to send a redirect response and prevent resubmitting a form when a user refreshes the page is
clearRequ estPara mete rs ()
removeDuplicates()
removeParameters()
send Red irect()
If multiple Ext plugins modify struts-config-ext.xml:
Liferay merges all of the plugins into one plugin and deploys the combined plugin
Liferay only deploys the first plugin that modifies struts-config-ext.xml and does not deploy subsequent plugins
The last plugin deployed takes precedence
All of the plugins deploy successfully
Methods for retrieving the current users ID include: (Please select all correct answers.)
ThemeDisplay.getUserId()
PortaIUtil.getUserld(renderRequest)
request.getRemoteUser()
Liferay.getUserld(renderRequest)
Page.getUserld()
Developing for Liferay requires
IntelliJ
Eclipse
NetBeans
Liferay Developer Studio
The <liferay-ui: icon-menu> tag is used to
Display a list of actions
Display navigation
Display a list of breadcrumbs
Display categories
Portlets are placed in the Control Panel using
portlet.xml
liferay-portlet.xml
liferay-plugin-package.properties
liferay-look-and-feel.xml
The recommended way to validate a user against an external system when adding a user through the UI or a web service is to
Create a hook plug in to add a model listener to the User object
Create a service wrapper hook that modifies the User service
Create a Struts action hook to perform validation when the user form is submitted
Create an Ext plugin to modify the core Spring configuration to override the User service
All Service Builder entities contain a local reference to: (Please select all correct answers.)
CounterLocaIService
AssetLocaIService
ResourceLocalService
SocialLocalService
WorkflowLocaISe rvice
An administrator would like to add a new travel preferences section in the Miscellaneous section of the user form. The travel preferences are stored as custom fields. The recommended way to implement the solution using a hook plugin is to: (Please select all correct answers.)
Modify html/portlet/users_admin/edit_user.jsp to add the travel preferences section to theMiscellaneous section
Set the portal property "users.form. my.account, miscellaneous"to "travel-preferences" and add the corresponding JSP
Create a Struts action hook to persist the Expando value to the database
Add the custom fields to the relevant JSP using <liferay-ui;custom-attribute>
A class that extends MVCPortlet must implement
init()
doView()
doEdit()
The JavaScript method that executes after each portlet on the page loads is
Liferay.on(allPortletsReady', fn)
When a hook plugin overrides the language keys for the locale "en_US" the text presented for the locale comes from:
The core Language.properties
The plugin Language.properties
The plugin Language_en.properties, then the core Language.properties
The plugin Language_en.properties, then the core Language_en.properties
The method to retrieve an integer submitted as a form field named "widgetCount"' is:
GetterUtil.getInteger(actionRequest, "widgetCount")
RequestUtiI.getInteger(actionRequest,"widgetCount )
HTMLUtil.getInteger(actionRequest, "widgetCount")
ParamUtil.getInteger(actionRequest, "widgetCount")
FormUtil.getInteger(actionRequest, "widgetCount")
AlloyUtil.getInteger(actionRequest, "widgetCount")
The Ant target that removes compiled class files from the plugin is
obliterate
destroy
remove
clean
reset
terminate
Customizations to a theme are made in the folder
_unstyled
.styled
themes
_diffs
custom
The method to retrieve a list of users added directly to an organization is
OrganizationLocalServiceUtil.getOrganizationUsers()
UserLocalServiceUtil.getOrganizationUsers()
GroupLocalServiceUtil.getOrganizationUsers()
To remove some of the core portlets from the Add Application menu and add them in the Control Panel
Create a hook plugin that modifies the portal properties default.control.panel.portlets and default.add .application.portlets
Create an Ext plugin that modifies liferay-plugin-package.xml and liferay-display.xml
Create an Ext plugin that modifies liferay-portlet-ext.xml and liferay-display.xml
Create an Ext plugin that modifies liferay-look-and-feel.xml
All render logic must be implemented in the JSP when using MVCPortlet
The descriptor liferay-display.xml
Defines the initial views for the portlet
Defines the categories in the Add Application menu
Provides the ability to use Liferay's permission system
To display the language key "add-part'' use
<liferay-ui:locale key= "add-part" />
<liferay-ui:language key= "add-part" />
<liferay-ui;message key = "add-part" /
<aui-ui:message key ="add-part" />
Default RSS feeds are set as portlet preferences. To make all new instances of the RSS poitlet display a single custom RSS feed, it is recommended to
Create a hook plugin to add a model listener to the layout to update the portlet preferences of any RSS portlet added to the page
Create an Ext plugin that contains the desired configuration in portlet-ext.xml
Create a JSP hook that overrides the RSS portlet's default configuration settings
Navigate to System Defaults in the Control Panel and update the portlet preferences
ThemeDisplay.getUserId() returns a value of -1 for the Guest user.
To allow more than one instance of a portlet on the same page setinstanceabletotrue" in
liferay-display.xml
liferay-plugin-package.xml
liferay-layout-template.xml
web.xml
The business logic for UserLocalServiceUtil is found in
Use rLocaIServiceUtil
UserLocalServicelmp
Use rLocalService
UserServiceUtil
Portlets that extend MVCPortlet require annotations on action methods.
A hook plugin can be used to: (Please select all correct answers.)
Modify a portal language key
Modify a theme plugin
Override a portal JSP
Override the User service
Override PortalLDAPUtil
The recommended way to strip content from the outgoing response is to:
Create a hook plugin that implements a service post action to strip content from the response
Create an Ext plugin that implements a servlet filter to strip content from the response
Create a hook plugin that implements a servlet filter to strip content from the response
Create a hook that implements a request post processor to strip content from the response
To customize the default success message displayed by MVCPortlet
Add a custom key to the SessionMessages object
Override the language key default-success-message in Language.properties
Provide a <default-message-mapping> entry in liferay-portlet.xml
Pass a parameter called 'success'' in the ActionURL and map it to a custom language key
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
Supported plugin types in the Plugins SDK include: (Please select all correct answers.)
AlloyUI plugins
Ext plugins
Hook plugins
Web plugins
Layout template plugins
Portlet plugins
Objects stored in the portlet application scope session are available to
Any portlet on the same page
Any portlet in the same portlet application
Any portlet within the portal applicatio
Only the portlet that stored the object in the session
To start Liferay with developer properties
Set the porta I.developer, mode property in portal-ext.properties to ''true
Include portal-developer.properties during Java startup, or in portal-ext.properties
Navigate to Server Administration in the Control Panel and set the portal.developer.mode property to "true"
Copy portal-developer.properties from the portal's classes directory to the Liferay home directory and restart the server
The method to get the value of a custom field for a User object named "user" is:
ExpandoLocalServiceUtil.getAttribute(user)
user.getExpandoBridge().getAttribute()
user.getExpando()
PortalUtil.getExpando(user)
In portal.properties: login,events.post=\ com.liferay.portal.events.ChannelLoginPostActionA,\ com.liferay.portal.events.Defaultl_andingPageAction,\ com.liferay.portal.events.LoginPostAction A hook plugin can insert a new class between DefaultLandingPageAction and LoginPostAction
The descriptor liferay-portlet.xml:
Defines Liferay-specific portlet features
Defines the categories of the Add Application menu
Identifies portlets that only run onLiferay
Not all of the fields in the User object are searchable out of the box. The recommended way to make these fields searchable is to
Create a hook plugin that overrides the User service to index the required fields
Create a hook plugin that overrides the edit user Struts action to index the required fields
Create an Ext plugin that extends the User indexer to index the required fields
Create a hook plugin that implements an indexer post processor to index the required fields
Events supported by JSR-286 portlets for interportlet communication are: (Please select all correct answers.)
Publishing events
Processing events
Global events
Lifecycle events
The recommended way to display a web content article in a theme
Use the AssetEntry service in portal_normal.vm to get the desired article
Embed the Web Content Display portlet, passing in the desired article ID to the portlet URL
Embed the Web Content Display portlet, passing in portlet preferences set to the desired article
Create a JSP hook that gets the desired article from the JournalArticle service
After removing a customization from an Ext plugin, the recommended way to redeploy in a development environment is to
Redeploy the plugin and restart the server
Undeploy the original plugin and deploy the updated plugin
Start with a clean instance of the server and deploy all plugins
Redeploy all plugins and restart the server
The following statements about plugins are true: (Please select all correct answers.)
All plugins are hot-deployable
Plugins can be used to modify core portal behavior
Plugins can be used to modify the layout of a page
Liferay supports six different types of plugins
Plugins are the preferred development approach
The "companyId" is a(n):
Creating a Struts action hook requires the following elements in liferay-hook.xml: (Please select all correct answers)
<struts-hook>
<struts-action-path >
<struts-action-impl>
<override-struts-path>
<struts-action >
The Plugins SDK uses
portal-service.jar
JAR files from the user's home directory
portal-impl.jar
portal-plugin.jar
The descriptor liferay-hook.xml defines the location to override a core JSP using
<url-pattern>
<custom-jsp-global>
<custom-jsp-dir>
<jsp-override>
<include-and-override>
To map a Service Builder entity to an existing database table in service.xml the entity name must match the database table name
In portal.properties, the following property lists portlets that can be embedded on any page: portlet.add(default.resource.check.whitelist=3,56_INSTANCE_0000,5S,S2,S6,87,88/103,113,145, 164, The property is listed in liferay-hook_6_l_0.dtd as a property that can can be overridden with a hook. The recommended way to prevent embedding the Search portlet ("3") is to create a hook plugin
The location of the XML file that determines permissions for a portlet plugin is configured by
The VM argument "resource-actions-configs"
The portlet property "resource.actions.configs"
The init parameter "resource-actions-configs"
A portal property "plugin.resource.actions.configs"
AlloyUI is
A JavaScript library
A CSS framework
A tag library
The JavaScript method that executes as soon as the HTML document has finished loading is
Liferay.on(fn)
Advantages of hook plugins over Ext plugins include: (Please select all correct answers.)
A hook plugin is hot deployable, while an Ext plugin is not
A hook plugin has direct access to the portal class loader, while an Ext plugin does not
A hook plugin provides an easier upgrade path for overriding core services and JSPs
A hook plugin can modify service layer classes, while an Ext plugin cannot
The recommended way to add a custom class to Liferay's startup process is to
Create a portal-ext.properties file in the Liferay Home directory that adds the custom class to global.startup.events, and add the custom class to the deployed Liferay application
Create an Ext plugin that replaces the value of global.startup.events with the custom class, and add the custom class to the plugin
Create a portal-ext.properties file in the Liferay Home directory that replaces the value of global.startup.events with the custom class, and add the custom class to portal-impl.jar
Create an Ext plugin that adds the custom class to global.startup.events, and add the custom class to the plugin
Tables are created in the database for a Service Builder entity after
The Ant "build-service" target has run
The portlet is deployed for the first time
The portlet is added to a page for the first time
Tables must be created manually
After a portlet completes the action phase
Only that portlet enters the render phase
All portlets on the page enter the render phase
Any portlet whose data has changed enters the render phase
Nothing happens since the render phase occurs before the action phase
When embeddding a plugin portlet in a layout template with $processor.processPortlet() use the
Portlet name
Fully qualified portlet ID
Portlet URL
Fully qualified display name
The following code: GetterUtil.getlnteger("one") returns
0
1
The code throws a java.lang.ArithmeticException
The code throws a com.liferay.portal.kernel.exception.SystemException
The method to get theme settings in a theme is
$portalUtil.getSetting()
$theme.getSetting(
$layout.getSetting(
$themeDisplay.getSetting()
The recommended way to customize how the User object indexes information is through a(n):
Hook plugin
Direct modification of the portal source
Ext plugin
Ext environment
The recommended way to implement a service wrapper hook that customizes the authenticateByScreenName() method of the User service using a class called com.sample.MyUserLocalServicelmpI is to: (Please select all correct answers.)
Add the following to liferay-hook.xml: <service> <service-type>com.liferay.portal.service.UserLocalService</service-type> <service-impl>com.sample.MyUserLocalServiceImpl</service-impl> </service>
Copy all of the methods from UserLocalServicelmpI to MyUserLocalServicelmpI
Override the authenticateByScreenName() method in MyUserLocalServicelmpI
Add the following to liferay-plugin-package.properties:required -deploymentcontexts=UserLocalServ ice
Implement custom logic and call super.authenticateByScreenNameQ if applicable
Service Builder entities are defined in
service, xml
MVCPortlet directs page flow using:
The controller() method
A render parameter called "mvcPath"
A direct link to the JSP with a relative URL
A public render parameter called "path"
The following classes can be imported when overriding a core JSP using a hook plugin: (Please select all correct answers.)
Classes residing in the global class loader
Classes residing in the portal class loader
Classes residing in the portlet plugin class loader
Classes residing in the hook plugin class loader
User-specific properties in the Plugins SDK for the user "jsmith'' are configured in
build.jsmith.properties
pom.xml
pom.jsmith.properties
portal.settings
portal.properties
portal-ext.properties
The permissionChecker.hasPermission() method requires the following parameters to determine if a user has the permissions to update a resource: (Please select all correct answers.)
Group ID
User ID
Action ID
Company ID
Resource primary key
Resource name
Liferay's core remote services: (Please select all correct answers.)
Can only return primitive types
Perform permission checking
Must be invoked through web services
Are accessed through Java or web services
Language hooks cannot be used to add new language keys
Liferay's persistence layer: (Please select all correct answers.)
Relies on Enterprise JavaBeans to ensure compatibility with all major application servers
Uses Hibernate by default to ensure compatibility with all major database servers
Can be invoked directly from the UI layer
Can be configured to use JPA
To define portlet actions in separate classes using MVCPortlet: (Please select all correct answers.)
Each class must implement the MVCAction interface
Each class must implement the ActionCommand interface
Each class must implement a processCommand() method that returns a boolean to indicate if the action completed
Each class must implement a renderCommand() method
A Liferay utility to verify the format of an email address is
Validator.isEmailAddress()
HTMLUtil.isEmailAddress()
StringUtil.isEmailAddress()
Corrector.isEmailAddress()
GetterUtil.isEmailAddress()
ParamUtil.isEmailAddress()
The portal properties that a hook plugin can override are defined in
Iiferay-hook_6_l_0.dtd
liferay-hook.xml
portal-hook.properties
portal-hook_6_l_0.dtd
The file containing the HTML document for a typical page is
portal.vm
portal_normal.vm
liferay-portal.vm
init.vm
The standard JSR-286 portlet modes are: (Please select all correct answers.)
Help
Configuration
Print
Edit
View
About
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
To display a success message in a JSP use:
<liferay-ui:success message="part-deleted-successfully" />
<liferay-ui:success key= "part-deleted-successfully" />
<alloy-ui:success key="part-deleted'' message="part-deleted-successfully" />
<liferay-ui:success key= "part-deleted" message="part-deleted-successfully" />
A portlet application only needs the standard web.xml deployment descriptor to be considered valid.
The method to retrieve a list of organizations where a user has direct membership is
OrganizationLocalServiceUtil.getUserOrganizations()
UserLocaIServiceUtil.getUserOrganizations()
GroupLocalServiceUtil.getUserOrganizations()
The recommended way to share language keys across portlet applications is
Create a resource bundle in one portlet and declare a dependency in the other portlets
Create an Ext plugin with the language keys from all of the portlets
Create a symbolic link in the portlets pointing to an external resource bundle
Create a hook plugin containing language keys from all of the portlets
The best way to add a new language key to the portal is through
The Control Panel
A hook plugin
An Ext plugin
Modifying Liferay's source
The recommended way to add support for a new locale is to
Create an Ext plugin that adds a language properties file for the desired locale
Create an Ext plugin that adds a language properties file for the desired locale and implements a servlet filter mapping using IlSnFilter
Create a hook plugin that adds a language properties file for the desired locale and implements a servlet filter hook to invoke IlSnFilter through PortalClassLoaderFilter
Create a portlet plugin that overrides the core language filter to recognize the desired locale
The settings in portal-developer.properties
Enable faster deployment of plugins
Disable minification of CSS and JavaScript
Assist deployment from a development to a production environment
Precompile Velocity and FreeMarker templates
Portlets can use interportletcommunication to: (Please select all correct answers.)
Pass any serializable object as an event payload
Trigger multiple events
Invoke events directly from the render phase
Enforce the processing order of events
The recommended way to make an isolated change to a core JSP is to
Create an Ext plugin to create a backup of the original JSP and extend the backup JSP
Create a hook plugin to override the original JSP using the <liferay-util:buffer> tag to copy the contents of the JSP
Create a hook plugin to override the original JSP using the <file-name>-override.jsp pattern
Create an Ext plugin to override the original JSP using the <liferay-util:include> tag to copy the contents of the JSP
Liferay's core JavaScript framework is
jQuery
Dojo
MooTools
AlloyUI
YUI
A Struts action hook cannot define new Struts actions
AlloyUI is a framework built on
YUI2
YUI3
A portlet can be assigned to a category in the Add Application menu using
liferay-category.xml
liferay-menu.xml
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
Default CSS files in a theme are imported by
base.css
ma in.css
style.css
import.ess
The recommended plugin type to use for a new servlet filter is a(n):
Ext
Portlet
Hook
Theme
To hide the default success message in a portlet that extends MVCPortlet
Add the following when creating an action URL: <portlet:actionURL name="addRecord" var="addRecordURL" add-process-action-success-action="false" />
Add the following to liferay-portletxml: <add-process-action-success-action>false</add-process-action-success-action>
Add the following to portlet.xml: < in it-pa ram> < na me >add -process-action -success-action </na me > <value>false</value> </init-param>
The default success message can only be overridden by supplying a customized success message using: SessionMessages.add(actionRequest, "custom-success-message");
An administrator would like to search for blog entries by the Twitter account of the author. The recommended way to add the Twitter account to the index and add the term to the search query is to
Create a hook plugin that overrides the BlogsEntry service to index the Twitter account and add the term to the search query
Create a hook plugin that overrides the Struts actions to index the Twitter account on update and add the term to the search query
Create an Ext plugin that extends the BlogsEntry indexer to index the Twitter account and add the term to the search query
Create a hook plugin that implements an indexer post processor to index the Twitter account and add the term to the search query
The method to embed a portlet in a theme is
$theme.addPortlet()
$theme.runtime()
$theme.embedPortlet()
$theme.processPortlet()
Color schemes are defined in
liferay-color-scheme.xml
The <portlet: defineObjects /> tag defines the variables: (Please select all correct answers.)
"portletPreferences"
"renderRequest"
"remoteUser"
"portletSession''
To ensure that all portlets added to the right-hand column of this layout template have a blue background: <div class="my_2_column" id="main-content" role="main"> <div class= portlet-layout > <div class="aui-w50 portlet-column portlet-column-first" id="left-hand"> $processor.processColumn("column-l\ portlet-column-content portlet-column-content-first") </div> <div class="aui-w50 portlet-column portlet-column-last" id = "right-hand"> $processor.processColumn("column-2\ "portlet-column-content portlet-column-content-last") </div> </div> </div>
Add the following CSS to the theme: #main-content .right-hand .portlet { background:blue; }
Add the following CSS to the theme: #right-hand .portlet { background:blue; }
Provide a custom JSP hook that overwrites the default style for ".column-2"
Add the following CSS to the theme: #right-hand {portlet-background:blue;}
The method to set the value of a custom field for a BlogsEntry object ("blog") is
PortalUtil.setExpando(blog)
blog.getExpandoBridge().setAttribute()
ExpandoLocalServiceUtil.setAttribute(blog)
blog.setExpandoQ
The default variables in a theme are defined in
main.vm
variables.vm
As a best practice, a portlet plugin imports classes from: (Please select all correct answers.)
portlet.jar
ext-impl.jar
The recommended way to override the updateLastLogin() method and create a new method called updateLastlmpersonation() for the User service is to
Create a hook plugin and implement a service wrapper that overrides the updateLastLogin() method and creates the updatel_astImpersonation() method in the User service
Create a portlet plugin and implement a service wrapper hook that overrides the updatel_astLogin() method in the User service and build a new service in the plugin that references the User service and creates the updatel_astImpersonation() method
Create an Ext plugin that modifies portal-spring.xml to replace the User service with a new service that overrides the updatel_astLogin() method and creates the updatel_astImpersonation() method
Create a hook plugin and implement a service wrapper that overrides the updatel_astLogin() method and create an Ext plugin that builds a new service to implement the updateLastImpersonation() method for the User service.
After adding new functionality to an Ext plugin, the recommended way to deploy in a development environment is to
Stop the server, redeploy the plugin and restart the server
Undeploy the original plugin, clean the server and deploy the updated plugin
Undeploy all plugins and deploy the updated plugin prior to redeploying the other plugins
When a hook overrides a core JSP named view.jsp
The new view.jsp overwrites the original file and the original view.jsp is no longer available
The original view.jsp is moved to a temporary folder
The original view.jsp is renamed to view.portal.jsp
The contents of the original view.jsp and the new view.jsp are merged automatically
Liferay's core local services: (Please select all correct answers.)
Contain the business logic of the service
Enforce permission checking
Are required if using remote services
Communicate to the database through the persistence layer
Beta-portlet.war requires services that are in alpha-portlet.war. To guarantee beta-portlet.war deploys after alpha-portlet.war
Add the following to portletxml in beta-portlet.war: < init-pa ram> <name>required-deployment-contexts</name> <value>alpha-portlet</value> </init-param>
Add the following to liferay-plugin-package.properties in beta-portlet.war:required-deploy mentcontexts=alpha-portlet
Add the following to liferay-portlet.xml in beta-portlet.war: <required-deployment-contexts>alpha-portlet</required-deployment-contexts>
It is not possible to declare this type of dependency
Public render parameters are of the type:
List
RenderParameter
String
Object
RenderRequest
Service Builder does not generate
SQL statements to create tables
Hibernate and Spring configuration files
Axis web services
The view layer
The recommended way to modify the Wiki portlet configuration to recognize a new public render parameter defined in a portlet plugin
Create a hook plugin and add the public render parameter definition to portlet-custom.xml
Create an Ext plugin and add the public render parameter definition to portlet-ext.xml
Create a portlet plugin and re-implement the logic of the Wiki portlet and define the new public render parameter in portlet.xml
Create an Ext plugin and add the public render parameter definition to portlet-custom.xml
The element that defines a database table in service.xml is
<entity>
<table>
<db-table>
<object>
If the expiration cache in portlet.xml is set to "-1":
The finder cache does not expire
Ehcache does not expire
The portlet cache does not expire
To define a primary key named ''bookld" in service.xml
<primary-column name= bookld" />
<column name = bookld primary = true" />
<primary name= "bookld" />
<column primary="bookId" />
The method to retrieve a list of users that have been added directly to a site is
SiteLocalServiceUtil.getSiteUsers()
UserLocalServiceUtil.getSiteUsers()
UserLocalServiceUtil.getGroupUsers()
SiteLocalServiceUtil. getGroupUsers ()
Portlet application security roles are mapped to Liferay roles in:
liferay-role.xml
The service() method in GenericPortlet handles all requests for a particular portlet and dispatches to the appropriate method based on the portlet mode.
The recommended way to escape text is
StringUtil.escape()
HtmlUtiI.escape()
DisplayUtil.escape()
JSPUtil.escape()
FormUtil.escape()
GetterUtil.escape()
The Classic theme is built using
HTML 4
XHTML
HTML 5
HTML 6
WML
The descriptor liferay-portlet.xml defines
Events
The portlet class
The CSS class wrapper
Resource bundles
