SERVICE BULIDER

-


I have referred the some of the documents and materials about service Bulider.

Here is some of the statments. 

ServiceBuilder will create models, services, and service persistence first in the folder ext/ext-service, which will form ext-service.jar and it goes to the $CATALINA_HOME/lib/ext in Ext deployment. Here are the packages of the services for the portlet, Reports:
com.ext.portlet.reports.model
com.ext.portlet.reports.service
com.ext.portlet.reports.service.persistence
Then ServiceBuilder will create implementations of models, services and service persistence in the folder, ext/ext-impl. This will form ext-impl.jar and it goes to $CATALINA_HOME/webapps/ROOT/WEB-INF/lib in Ext deployment. Here are packages of the implementations of the services for the portlet, Reports:
com.ext.portlet.reports.model.impl
com.ext.portlet.reports.service.base
com.ext.portlet.reports.service.http
com.ext.portlet.reports.service.impl
com.ext.portlet.reports.service.persistence



Service Builder divides the source it generates into two layers:

        Interface layer and an implementation layer.

The interface layer gets generated in the aforementioned service folder. You will never change anything in the interface layer manually; Service Builder always generates the code that is found there.

 The implementation layer gets generated in your src folder and is initially just skeleton code which allows you to implement the functionality you need.




Comments

Post a Comment

Popular posts from this blog

Theme display in javascript

-
We know that we can access the themedisplay in java as ThemeDisplay themeDisplay = (ThemeDisplay) request.getAttribute(WebKeys.THEME_DISPLAY) But how can we access in javascript? Here we go Liferay.ThemeDisplay.getScopeGroupId() Liferay.ThemeDisplay.getCompanyId() Liferay.ThemeDisplay.getPlid() Liferay.ThemeDisplay.getLayoutId() By this we can access the groupId, companyid ... etc
Read more

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