Monday 8 December 2014

Maven portlet development - Liferay service builder portlet


1. Navigate to the folder where you want to create Liferay plugin
2. Execute the command mvn archetype:generate. This will take some time for the first time. You might need to rerun this command for twice to get it complete.
3. It will ask to choose a number or apply filter. Enter filter for Liferay, simply type liferay and hit enter.
4. Select archetype for buil-service portlet. I.e. liferay-servicebuilder-archetype
5. Enter liferay portlet archetype version. E. g. Version of Liferay, for our case we need to choose 6.2.0-RC5.
6. Define value for property 'groupId': :org.wellOfJava.portlet. i. e. groupId will identify your project uniquely across all projects.
7. Define value for property 'artifactId': : sample-portlet. i. e. Name of the portlet. 
8. Define value for property 'version':  1.0-SNAPSHOT: : 1.0-SNAPSHOT  (or here you can just press enter)
9. Define value for property 'package':  org.wellOfJava.portlet: : org.wellOfJava.portlet. That will be package structure of your portlet.
10. Add properties tag in pom.xml after </dependencies> tag and before </project> end tag
11. Now if you open the directory you would find 2 directory created inside and one POM.xml file. This POM is parent file for both of the sab modules.
a) {portlet-name}-portlet
i. This directory contains all necessary files for Liferay portlet.
b) {portlet-name}-portlet-service
i. This directory is specifically for developing service builder classes. 
12. Now the portlet is ready to add service builder layer. You would find service.xml file in {portlet-name}-portlet\src\main\webapp\WEB-INF. Modify the file as per your requirement. 
13. Now execute following command on the parent POM.
a) mvn liferay:build-service
b) mvn clean install
14. Import the parent POM file in eclipse and both of the sub module will be imported to eclipse. As well portlet project will also have dependency for service builder jar file. 

The portlet is ready for further development. You can carry on as you develop portlet in liferay-sdk.

Monday 8 September 2014

Spring Web Service Client Using Maven with Liferay Portlet


  • Create one simple maven base project in Eclipse.
  • Save your wsdl file in the resource directory with WSDL extension. Make sure about the extension
  • Copy following build and dependencies tag. 
<build>

    <plugins>

        <plugin>

            <groupId>org.apache.cxf</groupId>

            <artifactId>cxf-codegen-plugin</artifactId>

            <version>${cxf.version}</version>

            <executions>

                <execution>

                    <id>generate-sources</id>

                    <phase>generate-sources</phase>

                    <configuration>

                    <sourceRoot>src/main/java</sourceRoot>

                    <wsdlOptions>

                        <wsdlOption>

                            <wsdl>${basedir}/src/main/resources/TestService.wsdl</wsdl>

                        </wsdlOption>

                    </wsdlOptions>

                    </configuration>

                    <goals>

                        <goal>wsdl2java</goal>

                    </goals>

                </execution>

            </executions>

            <dependencies>

                <dependency>

                    <groupId>xerces</groupId>

                    <artifactId>xercesImpl</artifactId>

                    <version>2.9.1</version>

                </dependency>

            </dependencies>

        </plugin>

    </plugins>

</build>

    <dependencies>

        <dependency>

            <groupId>org.apache.cxf</groupId>

            <artifactId>cxf-tools-common</artifactId>

            <version>${cxf.version}</version>

        </dependency>

        <dependency>

            <groupId>org.apache.cxf</groupId>

            <artifactId>cxf-rt-frontend-simple</artifactId>

            <version>${cxf.version}</version>

        </dependency>

        <dependency>

            <groupId>org.apache.cxf</groupId>

            <artifactId>cxf-rt-transports-http</artifactId>

            <version>${cxf.version}</version>

        </dependency>

    </dependencies>

    <properties>

        <cxf.version>2.7.7</cxf.version>

    </properties>
  • build maven project “mvn clean install -DskipTests
  • Use service class to get ServiceImplPort class. Then call your method. E.g. testService.getTestServiceImplPort().getTest();
  • In your portlet pom file. Add dependency for your maven project your have created in first step. 
  • Build your portlet with maven. Jar file for the services will be copied in the lib of portlet war file.
To Read more about CXF, Please visit http://cxf.apache.org/docs/using-cxf-with-maven.html

Tuesday 2 September 2014

Spring MVC portlet using maven

Create Maven base Liferay portlet
Please following the below link to create a Liferay portlet using maven command prompt.
http://wellofjava.blogspot.com/2014/08/maven-portlet-development-for-command.html

Define Maven dependencies for Sping MVC portlet
Now you will need to add following dependencies in Maven file to make spring portlet.


<dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-webmvc-portlet</artifactId>
    <version>${spring.version}</version>
</dependency>
<dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-core</artifactId>
    <version>${spring.version}</version>
</dependency>
<dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-context</artifactId>
    <version>${spring.version}</version>
</dependency>

Add spring.version as property. You can choose version as per your use.
               
<properties>
    <spring.version>3.1.0.RELEASE</spring.version>
</properties>


Define Portlet for Spring mvc
In portlet.xml file, you need to define portlet class which will act as controller for portlet. When you create portlet in Liferay using SDK or using maven, You will find following line in portlet.xml.

<portlet-class>com.liferay.util.bridges.mvc.MVCPortlet</portlet-class>

You need to change this portlet class to use spring mvc framework.


<portlet-class>org.springframework.web.portlet.DispatcherPortlet</portlet-class>

When a DispatcherServlet or DispatcherPortlet is set up for use and a request comes in for that specific dispatcher, it starts processing the request. The sections below describe the complete process a request goes through when handled by such a dispatcher, from determining the application context right through to rendering the view.

Create Spring application context file
Now you need to create a spring context file for spring mvc which will contains bean definitions of controller and viewResolver. Create one xml file with name of your portlet or application-context.xml or any other name as per your organization standard.
You need to put this file under WEB-INF. Either you can put this file in your directory under WEB-INF e.g. WEB-INF/spring.
Add the following content in it.


<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:p="http://www.springframework.org/schema/p" xmlns:context="http://www.springframework.org/schema/context" xmlns:aop="http://www.springframework.org/schema/aop" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd">
</beans>

Add following lines within <beans> tag to enable spring annotations.  

<context:annotation-config />
<bean class="org.springframework.web.portlet.mvc.annotation.DefaultAnnotationHandlerMapping" />


Pointing Spring application context file in Portlet configuration

Now once you have to create the context file. You need to point this context file through your portlet configuration to make it effective. Add init-param parameter to portlet definition in portlet.xml file. E.g.
 
<init-param>
    <name>contextConfigLocation</name>
    <value>/WEB-INF/spring/application-context.xml</value>
</init-param> 
   
Put viewrenderservlet entry in web.xml file.
It is necessary to load spring render servlet. Because ViewRendererServlet is a bridge servlet, mainly for the Portlet MVC support. For usage with Portlets, this Servlet is necessary to force the portlet container to convert the PortletRequest to a ServletRequest, which it has to do when including a resource via the PortletRequestDispatcher.
Add following xml snippet in web.xml

<servlet>
    <servlet-name>view-servlet</servlet-name>
    <servlet-class>org.springframework.web.servlet.ViewRendererServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
    <servlet-name>view-servlet</servlet-name>
    <url-pattern>/WEB-INF/servlet/view</url-pattern>
</servlet-mapping>

Configuring viewResolver
Spring mvc uses view resolver to forward request to JSP. Spring supports many kind of resolvers. Following are the list of all the view resolvers.

  • AbstractCachingViewResolver, 
  • AbstractTemplateViewResolver, 
  • BeanNameViewResolver, 
  • FreeMarkerViewResolver, 
  • InternalResourceViewResolver, 
  • JasperReportsViewResolver, 
  • ResourceBundleViewResolver,
  • UrlBasedViewResolver, 
  • VelocityLayoutViewResolver, 
  • VelocityViewResolver, 
  • XmlViewResolver, 
  • XsltViewResolver
For easy to use purpose you can use InternalResourceViewResolver. This is very easy to use and it can handle JSP. Add following code snippet to add view resolver to your portlet.

<bean id="jspViewResolver" class="org.springframework.web.servlet.view.InternalResourceViewResolver">
    <property name="viewClass" value="org.springframework.web.servlet.view.InternalResourceView" />
    <property name="prefix" value="/WEB-INF/jsp/" />
    <property name="suffix" value=".jsp" />
    <property name="order" value="1" />
</bean>

In prefix property we have to give the folder path where we kept all JSP files.
In suffix property we have to give as ".jsp".
Create a jsp file in /WEB-INF/jsp directory.

Create Portlet Controller
Now we need to implement controller to handle tasks for portlet. In controller each method is invoked by Request Parameter mapping.
We have used different annotation to implement controller.


@Controller(value = " SpringMVCTestController ")
@RequestMapping("VIEW")
public class SpringMVCTestController {
    @RenderMapping
    public String handleRenderRequest(RenderRequest request,RenderResponse response,Model model){
        return "defaultRender";
    }
}


Define controller
Now once your controller is ready, you need to define this controller as bean in spring configuration file.


<bean class="com.myowncompany.test.springmvc.controller.MyFirstSpringMVCTestController" />

Thursday 7 August 2014

Maven Portlet Development - For Command Prompt Lovers


  • Navigate to the folder where you want to create Liferay plugin
  • Execute the command mvn archetype:generate. This will take some time for the first time. You might need to rerun this command for twice to get it complete.
  • It will ask to choose a number or apply filter. Enter filter for Liferay, simply type liferay and hit enter.
  • Select proper archetype for particular pulgin e.g for Liferay portlet pulgin select liferay-portlet-archetype
  • Enter liferay portlet archetype version. E. g. Version of Liferay, for our case we need to choose 6.2.0-RC5.
  • Define value for property 'groupId': :org.wellOfJava.portlet. i. e. groupId will identify your project uniquely across all projects.
  • Define value for property 'artifactId': : sample-portlet. i. e. Name of the portlet. 
  • Define value for property 'version':  1.0-SNAPSHOT: : 1.0-SNAPSHOT  (or here you can just press enter)
  • Define value for property 'package':  org.wellOfJava.portlet: : org.wellOfJava.portlet. That will be package structure of your portlet.
  • Add properties tag in pom.xml after </dependencies> tag and before </project> end tag
  • <properties>
    <liferay.version>6.2.0-RC5</liferay.version>
    <liferay.maven.plugin.version>6.2.0-RC5</liferay.maven.plugin.version>
    </properties>
    
  • Navigate to the directory, where pom.xml of the plugin exist. Execute the command mvn clean install –DskipTests. For building war file
  • After successful build import into eclipse

Wednesday 30 July 2014

Simple Captcha Text Producer Implementation

This blog is in reference to the Liferay hook in Marketplace. Following is the link for the Captcha Internationalization.
Captcha Internationalization Hook

Same Concept can be used to implement multilingual Captcha for any web site.

Simple Captcha is the opensource implementation for captcha service. Please check the following URL for more details about SimpleCaptcha.
http://simplecaptcha.sourceforge.net/

Simple Captcha is providing textProducer for Captcha implementation. The textProducer class produces a string with some random Character or Numbers or Alphanumeric. Just simply add that captcha as attribute into the Session. Give an input Field in the HTML form for user to insert captcha text. Once user submits the form, compare the input field with the value stored in the session. This is how captcha will work.

Simple captcha is providing textProducer for Arabic, Chinese and Digits. Most of the time digit in captcha will work fine. In case customer asks for regional language for the captcha. You need to simply make your own implementation for the textProducer. Please refer the implementation of the ArabicTextProducer from SimpleCaptcha.
http://sourceforge.net/p/simplecaptcha/code/ci/master/tree/Java/src/nl/captcha/text/producer/ArabicTextProducer.java

You just need to implement TextProducer interface from SimpleCaptcha and provide your own implementation for your language. You can refer following code that I have developed for Gujarati text producer. 

package com.wellofjava.captcha.text.producer;

import nl.captcha.text.producer.DefaultTextProducer;
import nl.captcha.text.producer.TextProducer;

public class GujaratiTextProducer implements TextProducer {

    static final int DEFAULT_LENGTH = 5;

 private static char[] GUJARATI_CHARS = { '\u0627', '\u0A85', '\u0A86',
   '\u0A87', '\u0A88', '\u0A89', '\u0A8A', '\u0AE6', '\u0AE7',
   '\u0AE8', '\u0AE9', '\u0AEA', '\u0AEB', '\u0AEC' };
  
    private final TextProducer _txtProd;
    
    public GujaratiTextProducer() {
        this(DEFAULT_LENGTH);
    }
    
    public GujaratiTextProducer(int length) {
        _txtProd = new DefaultTextProducer(length, GUJARATI_CHARS);
    }
    
    @Override
    public String getText() {
        return _txtProd.getText();
    }
}

Tuesday 22 July 2014

Liferay HSQL DB Access

        Normally at the time of development, we have fixed name of database which will be used for production environment. We configure the same DB in our local or development environment for the build. But in case of doing POC, preparing demo for PreSales or making some reusable component, we might not have access to such environment, or as per the system requirement, It might not be a good idea to spend time after configuring other DB.

        Liferay is using HSQL database by default. Here is the steps to access that HSQL database using DatabaseManager.


  1. Go to {server}\lib\ext , Make you have hsql.jar file under that location. If it's not there. Find the location of that jar.
  2. Open command prompt with the location of step-1
  3. Run this command in command prompt "java -cp hsql.jar org.hsqldb.util.DatabaseManager"
  4. Database manager will open as per the below image.
  5. Select "HSQL Database Engine Standalone" for dropbox of type.
  6. Now in URL text field you need to enter location of the DB file. So if you check in your Liferay bundle. There would be lportal HSql DB in "{liferay-portal}\data\hsql" directory. So you need to give path to DB as like "{liferay-portal}\data\hsql\lportal", here lportal is the DB.
  7. Username will be 'SA' and password will be blank. 
        Once the DB is connected. You will be able to see the list of the tables on the left hand side. As well you can execute any query using the same browser.


       One important point, If the Liferay instance is running. There would be lock on DB. So you won't be able to access the DB. 

Monday 14 July 2014

Mobile/SMS Verification


        Now a days, Most of the site needs to verify the mobile number and email address of their users for security purpose. Liferay is providing email verification OOB. I have developed a reusable component to verify mobile number of the customer using SMS service.

        This plugin will help to integrate that functionality directly to the Liferay portal.

        Key Features
  • Admin can enable/disable mobile verification very easily.
  • Mobile verification can be set to be mandatory/optional.
  • Further development depending upon mobile verification can be done easily. As mobile number and its status is stored in User Custom Attribute.

        Component is available in Liferay Marketplace.
        Mobile Verification

        Let me know if you need any further information about this component. 

Tuesday 1 July 2014

LDAP server Error Codes

Code(decimal)Error code (string)Description
0LDAP_SUCCESSSuccess
1LDAP_OPERATIONS_ERROROperations error
2LDAP_PROTOCOL_ERRORProtocol error
3LDAP_TIMELIMIT_EXCEEDEDTimelimit exceeded
4LDAP_SIZELIMIT_EXCEEDEDSizelimit exceeded
5LDAP_COMPARE_FALSECompare false
6LDAP_COMPARE_TRUECompare true
7LDAP_STRONG_AUTH_NOT_SUPPORTEDStrong authentication not supported
8LDAP_STRONG_AUTH_REQUIREDStrong authentication required
9LDAP_PARTIAL_RESULTSPartial results
16LDAP_NO_SUCH_ATTRIBUTENo such attribute
17LDAP_UNDEFINED_TYPEUndefined attribute type
18LDAP_INAPPROPRIATE_MATCHINGInappropriate matching
19LDAP_CONSTRAINT_VIOLATIONConstraint violation
20LDAP_TYPE_OR_VALUE_EXISTSType or value exists
21LDAP_INVALID_SYNTAXInvalid syntax
32LDAP_NO_SUCH_OBJECTNo such object
33LDAP_ALIAS_PROBLEMAlias problem
34LDAP_INVALID_DN_SYNTAXInvalid DN syntax
35LDAP_IS_LEAFObject is a leaf
36LDAP_ALIAS_DEREF_PROBLEMAlias dereferencing problem
48LDAP_INAPPROPRIATE_AUTHInappropriate authentication
49LDAP_INVALID_CREDENTIALSInvalid credentials
50LDAP_INSUFFICIENT_ACCESSInsufficient access
51LDAP_BUSYDSA is busy
52LDAP_UNAVAILABLEDSA is unavailable
53LDAP_UNWILLING_TO_PERFORMDSA is unwilling to perform
54LDAP_LOOP_DETECTLoop detected

64LDAP_NAMING_VIOLATIONNaming violation
65LDAP_OBJECT_CLASS_VIOLATIONObject class violation
66LDAP_NOT_ALLOWED_ON_NONLEAFOperation not allowed on nonleaf
67LDAP_NOT_ALLOWED_ON_RDNOperation not allowed on RDN
68LDAP_ALREADY_EXISTSAlready exists
69LDAP_NO_OBJECT_CLASS_MODSCannot modify object class
70LDAP_RESULTS_TOO_LARGEResults too large

80LDAP_OTHERUnknown error
81LDAP_SERVER_DOWNCan't contact LDAP server
82LDAP_LOCAL_ERRORLocal error
83LDAP_ENCODING_ERROREncoding error
84LDAP_DECODING_ERRORDecoding error
85LDAP_TIMEOUTTimed out
86LDAP_AUTH_UNKNOWNUnknown authentication method
87LDAP_FILTER_ERRORBad search filter
88LDAP_USER_CANCELLEDUser cancelled operation
89LDAP_PARAM_ERRORBad parameter to an ldap routine
90LDAP_NO_MEMORYOut of memory