Supported properties in hook by liferay

-
In Liferay we know that we can override some of the properties using hooks. To remember all those supported properties is quite difficult.

Also how can we know  whether that particular properties  is supported or not ?

So we have class called HookHotDeployListener class to check the supported properties. Look into the SUPPORTED_PROPERTIES string array variable where it listed all the supported properties.

This is how it is listed

public class HookHotDeployListener extends BaseHotDeployListener implements PropsKeys {

public static final String[] SUPPORTED_PROPERTIES = {
"admin.default.group.names", "admin.default.role.names",
"admin.default.user.group.names",
"asset.publisher.asset.entry.query.processors",
"asset.publisher.display.styles",
"asset.publisher.query.form.configuration", "auth.forward.by.last.path",
"auth.public.paths", "auth.verifier.pipeline", "auto.deploy.listeners",
"application.startup.events", "auth.failure", "auth.max.failures",
"auth.token.ignore.actions", "auth.token.ignore.origins",
"auth.token.ignore.portlets", "auth.token.impl", "auth.pipeline.post",
"auth.pipeline.pre", "auto.login.hooks",



and so on ...

By this we can verify that our property can be override using hook or not.

Comments

Post a Comment

Popular posts from this blog

How to know which liferay version we are using

-
Image
Sometimes we have to know which liferay version we are using, so how can we know? We can know the liferay version in different ways. 1. Liferay has provided some utility methods to know the which liferay version we are using , Here is the utility method ReleaseInfo.getReleaseInfo() It prints this statement " Liferay Portal Community Edition 6.2 CE GA2 (Newton / Build 6201 / March 20, 2014) " as i am using community version it shoes as CE. 2. Also we can also identify by response headers as below screenshot. If your using the chrome, right click on the browser and click inscept element , and navigate to the network  . you will see the URLS , click on the any url. 3. Also we can see during server startup as below statement Liferay Portal Community Edition 6.2 CE GA2 (Newton / Build 6201 / March 20, 2014)
Read more

Viewing the SQL Query in liferay : debugging the SQL Query in Hibernate

-
Sometimes we have to know SQL query hiting in DB to retrieve the list. Suppose When we are writing the DynamicQuery , Some times we have to know SQL query it is generating to hit DB. So generally it is useful when we are debugging the Query it is generated. In hibernate we used the write the property in XML file as hibernate.show.sql to view the query. In Liferay also we can also set the below property to true in the portal-ext.properties to view the SQL query at the console. hibernate.show_sql=true. By adding the above property it will just reterive the parameters. What if we want to display the parameters. Add the below properties in log4j.properties it will display the paramters also. # logs the SQL statements #log4j.logger.org.hibernate.SQL=debug # Logs the JDBC parameters passed to a query #log4j.logger.org.hibernate.type=trace In Liferay log4j is located in the below location tomcat-7.0.42\webapps\ROOT\WEB-INF\classes Also we want to see hibernate ses
Read more

Opening portlet in popup

-
  Sometimes, we may get requirements to open portlet in a popup. We can use below Javascrpit function to open in apopup. AUI().use('aui-base','aui-component','aui-parse-content','aui-node','liferay-form',     'liferay-portlet-url', 'liferay-util-window', 'plugin','aui-io-request', function(A){                    var renderURL = Liferay.PortletURL.createRenderURL();       renderURL .setWindowState("exclusive");        renderURL.setPortletId(" <portlet-name> ");       var  url = renderURL.toString();             A.io.request(url, {                 on: {                  success: function(event, id, obj) {                        var responseData = this.get('responseData');                        if (responseData) {                              Liferay.Util.openWindow({                                                                                               dialog: { 
Read more