This article is about my intership in Technopolis S.A. . It was my first summer working in a company and it was pretty interesting.I was 2 months there and my superior told me to develop a project based on gitlab that company uses. I had to learn to use the Gitlab API, more specific, i had to use...
Our project is a Liferay Workspace Project and lives in git. The test environment is on a remote server. So, our goal is to
Liferay comes bundles with an integrated Elastic Search server. This answers in port 9200. If you call the url http://localhost:9200/ you will get the following json.
Working with gradle in our IDE is not a problem. The problems begin when we choose to deploy our modules which contain third party libraries in liferay...
We will make a MvcPortlet with a Service builder which on a button click will store a message in the database and then display it.
In liferay 6.2 (yes, it is alive), if you are working with a miltilingual site, you can use a very handy way to define multilingual fields, for example in the preferences of a custom portlet.
PortletResponseUtil is a class to be used in the serveResource, in case you want to serve a file.
Liferay 6.2 is nice, but the guys working on the themes, should make a time travel in the past and use bootstrap 2.3... They don'y like it at all. There are many articles in the web about using bootstrap 3 in a liferay 6.2 theme, but all of them had problems or didn't work at all.
In some of our projects we have the problem, that the portlet plugins are big and slow and the deploy time takes a lot of time. Especially for the web developers, who make for example a css change in a portlets css file and want to see quickly if it is fixed, its very annoying.
At last, after almost two years, I managed finally to make the integration tests work. And it is not so complicated as it seems to be. So straight to the point.