Setting up a Spring Boot Project

CaptainCasa by default uses a Tomcat servlet container in which web applications are deployed at development time or in production scenarios (.war deployment). Of course any other servlet container (Jetty, JBoss, ...) can be used that supports Servlet API 3.1.

And there is also Spring Boot...! Spring Boot is liked by many developers because it produces self containing result files (.jar or .war) which incorporate the runtime container (Tomcat), so that you do not require an explicit e.g. Tomcat installation to deploy your system to – you can directly run it from the .jar or .war file.


Before reading this documentation: please read the documentation “Setting up a Maven Project”. The principal procedure is exactly the same as with a normal CaptainCasa-Maven project!

Spring Boot Support

The CaptainCasa Spring Boot integration includes the following functions:

Setting up a Spring Boot Project

For fast readers

All you need to do is:

Step by Step

In the following text Eclipse is used as IDE. Any other IDE can be used as well, of course. In the documentation “Setting up a Maven Project” you can find details on how to use the IntelliJ IDEA environment for executing the steps.

Create a new project...

...and select Maven-project:

Select any workspace location – you may the default workspace or select (as we did it in the example) a directory of your choice:

View the CaptainCasa archetype catalog of CaptainCasa:

For integrating the archetype catalog of CaptainCasa into your Eclipse you need to press the “Configure...” button and invoke the function “Add Remote Catalog...”:

Then add the information as follows:

The URL of the CaptainCasa archetype catalog is:

...back to the selection of the project archetypes: select the archetype “eclntwebapparchetype_springboot” and press “Next”:

Now define the Maven group id and the Maven artifact id:

I this example we use “sbtut1” for both.

After pressing the “Finish” button, the project is created:

You may check that the project properly builds by running it via Maven. Click the project with the right mouse button and select “Run As => Maven build”:

In the following dialog define the Maven goals “clean package”:

In the console you should see some output ending with...

...and in the project you should see that the corresponding application was created within the target directory:

You may have to refresh your file tree in Eclipse (right mouse button menu, select “Refresh”).

Your project is now set up!

Directly creating some layout in the project

Create the layout and the Java-code

You may now directly begin to develop CaptainCasa dialogs – without using CaptainCasa tooling at all. - Of course, we strongly recommend to use the tooling!...

Create the file “<project>/src/main/webapp/test.xml” and define its content as:

<?xml version="1.0" encoding="utf-8"?>




    <t:beanprocessing id="g_1" beanbinding="#{d.TestUI}" />

    <t:rowtitlebar id="g_2" text="Hello world" />

    <t:rowbodypane id="g_4" rowdistance="20">

        <t:row id="g_6">

            <t:field id="g_7" labeltext="Your name"

                text="#{}" width="100%" />


        <t:row id="g_3">

            <t:button id="g_9"

                actionListener="#{d.TestUI.onHelloAction}" text="Say Hello"

                width="150+" />


        <t:rowdistance id="g_13" height="20" />

        <t:row id="g_5">

            <t:label id="g_11" labeltext="Result"

                text="#{d.TestUI.result}" />






This is the layout definition of a dialog.

Now create the program “<project>/src/main/java/managedbeans/”:

package managedbeans;



import org.eclnt.editor.annotations.CCGenClass;

import org.eclnt.jsfserver.defaultscreens.Statusbar;

import org.eclnt.jsfserver.pagebean.PageBean;


@CCGenClass (expressionBase="#{d.TestUI}")


public class TestUI

    extends PageBean

    implements Serializable


    // ------------------------------------------------------------------------

    // members

    // ------------------------------------------------------------------------


    String m_result = "<not yet defined>";

    String m_name;


    // ------------------------------------------------------------------------

    // constructors & initialization

    // ------------------------------------------------------------------------


    public TestUI()




    public String getPageName() { return "/test.xml"; }

    public String getRootExpressionUsedInPage() { return "#{d.TestUI}"; }


    // ------------------------------------------------------------------------

    // public usage

    // ------------------------------------------------------------------------


    public void onHelloAction(javax.faces.event.ActionEvent event)


        if (m_name == null)


            Statusbar.outputError("Please define your name");



        m_result = "Hello world, " + m_name + "!";



    public String getResult() { return m_result; }

    public void setResult(String value) { this.m_result = value; }


    public String getName() { return m_name; }

    public void setName(String value) { this.m_name = value; }



Start Spring Boot via Maven and test

Run the project via Maven (“right mouse click > Run As... > Maven Build...”) and now define the tasks:

clean package spring-boot:run


The Spring Boot container will be started – you may observer corresponding output within the console window of Eclipse. If the start is successful then you may directly open up the browser and check the dialog.

Open the URL...



...and you should see the test page:

If you do not see the page then first check the console log of the Spring Boot container: in most cases the port which is used (8080) is already used by another program. Stop this program and/or re-configure the port of the Spring Boot container.

Continuous development...

You now could continue development by updating the XML file in the text editor, by updating the code, by adding new dialogs, etc. After updating the files in the project you need to restart the already Spring Boot container (or you may use Spring Boot's live-reload functions to keep the container running, see chapter below).

But: of course it is nicer to uses the CaptainCasa tool-set – so that you can edit layouts and generate code structures in an efficient and much more comfortable way.

Using the CaptainCasa tool set

Adding the Spring Boot project

Start the CaptainCasa environment by:

Your browser should look like:

Open “File > Import project...” from the menu...

...and select the project directory of your Spring Boot project:

The project will be loaded. If you already created the test.xml-dialog from the previous chapter you can directly double-click and edit it:

Now: just as normal...

Now you can work with the tool set “just as normal”, including:

All the artifacts that your create or edit are files within your Maven project – there is no management of redundancy, the original files of the project are used.

Behind the scenes

The CaptainCasa tool set loads the application that you develop into its “Application Tomcat” (port 50000). In this Tomcat you will see the corresponding “webapp”:

This means: the project is not running in the Spring Boot container but is running in the Tomcat server that comes as “Application Tomcat” (port 50000). Spring Boot always both runs in an own environment (actually Spring Boot does nothing else than packaging some Tomcat around the application...) and it runs the same way in a normal Tomcat environment.

Please check the project file (.ccproject) that describes the integration between the Spring Boot project and the tool set:

























The “${project}” variable points to the root directory of the project (in our example this way: “C:\temp\sbtut1”). So you see how the tool set knows where to look for layouts (“webcontentdirectory”-attribute) or where to look for code (“javasourcedirectrory”).

An interesting but important item is the “deploycopyinfo” element: this tells the toolset that the un-packaged application is contained in the target-directory of the project – which is exactly the one that is “filled” when executing the Maven “clean package”.

When reloading or hot deploying a project then the tool set will always:

This means: for normal development of dialogs you very seldomly have to execute the “big Maven build” (“clean package”) within the Spring Boot project. The “relaod” and “hotdeploy” will automatically copy the changed classes and webapp-resources on top of the files that result from the last Maven build.


You now have a created a Spring Boot project with CaptainCasa included.

The project may be run

Starting the Spring Boot container

Normal starting

While in the normal Maven project you use “mvn clean pacakge” to build the project, you now use “mvn clean spring-boot:run” to build and start your project.

Because CaptainCasa's layout tools require access to the “.war” image of the project we recommend to combine both and always call:

mvn clean package spring-boot:run


As result both the .war image will be built and the Spring Boot runtime will be started.

Starting in debug mode

There are several ways to start the Spring Boot container in debug mode. One way is to adapt the pom.xml in the following way:









                        -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=50010








Using live-reload

The live reload functions of Spring can be just used in a normal way. This means: you have to add the following to your pom.xml:







Some more inner details

Tomcat as environment <=> Spring Boot as environment

During development your project is run in two runtimes:

Starter class

The project archetype adds some Spring-Starter class into the project:

package springbootstartup;


import java.util.HashSet;

import java.util.Set;


import javax.servlet.ServletContext;

import javax.servlet.ServletException;

import javax.servlet.SessionTrackingMode;


import org.eclnt.jsfserver.managedbean.HotDeployManager;

import org.eclnt.jsfserver.util.CCInitialize;

import org.springframework.boot.SpringApplication;

import org.springframework.boot.autoconfigure.SpringBootApplication;

import org.springframework.boot.web.servlet.ServletContextInitializer;

import org.springframework.context.ApplicationContext;

import org.springframework.context.annotation.Bean;

import org.springframework.web.context.ServletContextAware;

import org.springframework.web.socket.server.standard.ServerEndpointExporter;



public class SBApplication


    public static void main(String[] args)

    {, args);




    public ServletContextAware endpointExporterInitializer(final ApplicationContext applicationContext)


        return new ServletContextAware()



            public void setServletContext(ServletContext servletContext)


                // code from

                ServerEndpointExporter exporter = new ServerEndpointExporter();



                // initialize web socket management which was left out in "big" intialization







    public ServletContextInitializer initializer()


        return new ServletContextInitializer()



            public void onStartup(ServletContext servletContext) throws ServletException


                // set tracking mode

                Set<SessionTrackingMode> stms = new HashSet<>();



                // initialize

                CCInitialize.setInitWebSocketPolling(false); // is initialized in endpointExporterInitializer

                CCInitialize.initializeCCEnvironment(servletContext,true); // true => forceReset!

                // set classloader in HotDeployManager in order to support live reload



                // output some information



                    System.out.println("########## " + servletContext.getRealPath("/"));


                catch (Throwable t)










You can move this class to any package of your choice – all relevant Spring parts are annotated and will be discovered automatically by Spring.

The “SBApplication” class contains the instructions how to start the CaptainCasa runtime within the Spring Boot container. The central method to do so is “CCInitialize.initializeCCEnvironment(...)” - but there are other, special definitions as well: