LRP-614 practice question 16 of 25

Hook plugins can only override core JSPs, services, language keys and Struts actions.

Full set: 144 questions
Answer options
A: True
B: False
Correct Answer:
FALSE
Explanation

The statement is incorrect because hook plugins in Liferay 6.1/6.2 have a broader range of capabilities than the four listed. While they can override core JSPs, wrap services, customize language keys, and override Struts actions, they can also be used for other critical customizations. These include, but are not limited to, overriding portal properties (via a portal.properties file), adding custom servlet filters, and implementing custom model listeners. The word "only" makes the statement an oversimplification and factually inaccurate.

Why Incorrect

This is a "True or False" question. The statement is false because it presents an incomplete and restrictive list of a hook plugin's capabilities. The existence of other customization options, such as overriding portal properties or adding servlet filters, directly contradicts the claim that hooks can only perform the four actions mentioned.

References

1. Liferay 6.2 Developer's Guide: The official documentation explicitly lists the various customizations possible with a hook, demonstrating a wider scope than the question suggests.

Source: Liferay, Inc., "Liferay Portal 6.2 Developer's Guide," Chapter 11: Overriding and Extending Liferay, Section: "Hook Plugins."

Reference: The guide details several types of hook customizations, including:

Customizing portal properties (portal.properties)

Customizing language keys

Customizing JSPs (including core JSPs and JSPs from other plugins)

Overriding a portal service (Service Wrappers)

Overriding a Struts action

Adding a servlet filter

Customizing authentication

Performing a custom action on user login events

Extending web.xml

This comprehensive list from the official vendor documentation proves that the capabilities are not limited to the four items in the question.

Scroll to Top