Posts

Getting Users / Deployment, AWS SES Setup

Get List of USers GET : localhost:8080/users?page=1&limit=50  (passed as url query parameter) @RequestParam is more useful on a traditional web application where data is mostly passed in the query abatements  while @PathVariable is more suitable for RESTful web services where URL contains values  e.g. http://localhost:8080/book/9783827319333, here data, which is ISBN number is part of URI. 1. controller getUSers 2. service 3. repository 4. postman LOGIN ->  GET with the above url   WITH or WITHOUT limit Deploying an app in remote server using maven 1. Go to properties after right clicking the project. 2. Check the loaction of the project 3. In your Command line, go to the above location ex) cd D:\t-projects\je\workspace\firstProject 4. type 'dir' to list the files contained. you should see 'pom.xml' in the root folder of the project, which means you can use maven command to run the app without using spring tool su...

Troubleshooting - Last day of work in 2018

Image
The above error in console means that the classes in com.liferay.portal.search.web.internal.display.context are not accessible. The probable cause of this issue is either the mismatch version of dependencies, or unexported package from Liferay Api. If the version of dependencies defined in build.gradle matches the version bundled in liferay 7.1(can be figured out through App Manager under Configuration), the next step is to look into export-package list in bnd.bnd in Liferay Api Only the packages listed in 'Export-Package' can be accessible, and there is no other way around to access to unexported package outside. (That is how OSGI works) If you do really want to access this portal-search-web, you can remove this default module from OSGI and re-build a new portal-search-web with your customization which requires lots of work. In the case of overriding JSP, there is no need to do the aforementioned way. It can be done by the JSP overrides using OSGI fragm...

Failed to export packages / not accessible

https://dev.liferay.com/develop/tutorials/-/knowledge_base/7-1/exporting-packages might be caused by the mismatch version of dependency, so make sure to use the right version bundled on Liferay 7.1
Image

Liferay Component

Image
https://dev.liferay.com/en/participate/liferaypedia/-/wiki/Main/Components

git pull vs git fetch and merge

Image
https://longair.net/blog/2009/04/16/git-fetch-and-merge/

Clean up Liferay DXP

1. 'temp' under tomcat 2. 'inside' of work under tomcat ( never delete work folder) 3. 'state' under osgi