Thank you too Aritz! I am glad that this paradigm helped you!

Hello Marcos,

I updated the Readme.md on github with some instructions on how to download and install the liferay server 7.2 . It is actually one maven command

mvn bundle-support:init

but I share and some very helpful links of liferay developer guide.

After the above, if you follow the  rest instructions on README.md file  and start the liferay server (the tomcat basely) you will see the angular/spring boot portlet inside the available portlets of portal. 

If you mean that I am not starting the application by running a main method, yes you are right. The spring boot portlet does not need an embedded tomcat that spring boot offers because it "lives" inside the portlet container which portlet container lives inside the liferay portal which liferay portal lives in tomcat. So if you look at  angular-spring-boot-portlets/wars/books-catalog-portlet/pom.xml

you will see that the spring-boot-starter-tomcat is provided.

<dependency>

      <groupId>org.springframework.boot</groupId>

       <artifactId>spring-boot-starter-tomcat</artifactId>

       <scope>provided</scope>

</dependency>

  The above does not mean that the portlet has nothing to do with the actual spring boot ,

it is an actual spring boot application with portlet specific configuration. 

You sure can do it. But when you develop it into a portlet (your code being in a controller), you can easily drop it on any page.  One of the main advantages you get it over here is, you get all the power of Liferay portlet. i.e., preferences, on the fly-styling, on the fly-javascript, configuration and most importantly, authentication. There's a lot to this authentication part. For starters, you can switch onto your developer tools in chrome, go to network tab and capture the XHR requests that are made on the page load, observe the request' s made to the controller and see all the parameters. Again, it takes a lot of time and effort to get a solid understanding of this. :-)