Generating Stubs(webservices) in Liferay

-

Generating stubs in liferay ,

1. we can generate the stubs in eclipse as

        File ---> New ---> Others --->type webservices and select webservices client ---> Paste the WSDL in the service defination and move the slide till to TestClient and click on the "finish" to generate.

WSDL can of type below http://localhost:8080/api/axis/Portlet_Blogs_BlogsEntryService?wsdl

When i am trying to do in liferay eclipse it is not allowing to generate the stubs. So i am used Plain tomcat to generate the stubs.

2. We can also generate the stubs by ant

   Drag and Drop the build.xml in ant

   Locate the build-client . Double click on it . It Generate the <portlet-name>-portlet-client.jar file in the docroot/WEB-INF/client folder.
 
   This lib contains the stubs. By Using that stubs we can write the our own implementations.

Comments

  1. UnknownMay 5, 2014 at 2:43 PM

    hi can u give me the detailed flow of process of generating WSDL in the liferay portlet.

    ReplyDelete
  2. VenkaJune 6, 2014 at 10:25 PM

    Hi Ravi,

    In Liferay WSDL file will be generated automatically

    I will share you the details

    1.First three should we methods to be write in the "ServiceImpl" classes
    2.After that we should be build the service in ant (build-service) task.
    Now you can see the SOAP classes are generated automatically.
    3.Again the execute the ant task(build-wsdd) it will generate the webservices.
    4. Again the excute the ant task (build-deploy).

    Hit the following URL of the default liferay service
    http://localhost:8080/api/axis

    Portlet specific http://localhost:8080//api/axis

    Thats it!!


    If you feel still detail steps are required . I will post the new post for the generation of the WSDL.

    ReplyDelete

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

Executing the BackGround Task

-
In Liferay we can exceute the background task asynchrously. The Background Task framework allows the developers to create and manage any kind of tasks that need to be run in a separated thread without the need of knowing anything about JAVA threading or concurrency Here the code ThemeDisplay themeDisplay = (ThemeDisplay) request.getAttribute(WebKeys.THEME_DISPLAY); Map taskContextMap = null; String taskName = null; String servletContextNames [] = new String[1] ; Portlet portlet = PortletLocalServiceUtil.getPortletById(request.getAttribute(WebKeys.PORTLET_ID).toString()); servletContextNames[0] = portlet.getContextName(); try { BackgroundTaskLocalServiceUtil.addBackgroundTask(themeDisplay.getUserId(), themeDisplay.getScopeGroupId(), taskName, servletContextNames,TestBackgroundTaskExecutor.class, taskContextMap,new ServiceContext()); } catch (PortalException e) { e.printStackTrace(); } catch (SystemException e) { e.printStackTrace(); } ...
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 t...
Read more