This is “Part I” of a series of educational videos – talking about life cycle considerations when defining a Web UI Architecture for your Business Application. Please take a look:

(Click into image for starting the video – or press >HERE<)

We updated the dark style of our style library. Please take a look within our >ONLINE DEMOS<.

(click into image for getting to the demos)

The name of the style is “default202201darkrisc”.

Setting up a Spring Boot project with CaptainCasa is “super-simple”!

CaptainCasa provides the adequate Maven project archetypes so that the creation of such project is a “one-button-action”. Check the >updated documentation< that explains what and how to do:

There are couple of shapes that you can use for the SCHEDULEITEM component. Example:

Schedule items components are used to render information that has a certain begin end end date/time. You may e.g. show/edit orders that are assigned to machines.

The items can be dragged/dropped, moved, sized at their ends – and may contain any other components. (In the example a text label was used.) Items can be arranged horizontally and vertically.

Tree structures now can be rendered as a “touch-able tree”, in order to increase the usability for mobile scenarios:

Each node is represented as tile. When touching a tile then its content is shown – or executed. The top line of tiles shows these nodes which are currently opened.

We recorded two “From the lab”-videos about the Multi Service Workplace.

The “Using the Demo” video is available >HERE<. It explains the features that are part of the demo workplace which was published at begin of this week.

The “Configuration” video is available >HERE<. It explains the basic steps of setting up a workplace scenario – combining different frontends of different services.

We published an online version of the “Multi Service Workplace” on our demo server. Please take a look >HERE<. Logon at tenant “DEMO” with user “user1” and password “user1”.

On the right you see tree showing available end points + their contained services + their contained frontends. Double clicking a frontend will start it within the content area. You may drag & drop frontends and arrange them in flexible ways.

Start “CaptainCasaDemo.com > Demos > Order 0001”, then double click on of the orders. The order processing (service 1) will open up a corresponding screen of the manufacturing processing (service 2). Both are completely independent services – but now combined within a common workplace. From the manufacturing you may click on one of the involved machines in order to get to the maintenance processing (service 3).

A first set of documentation is available >HERE<.

The “Multi Service Workplace” is tenant-based. We created a tenant “PLAYGROUND” that can be used for adding own configurations. Logon with tenant “PLAYGROUND”, user “admin”, password “admin”. – Please contact us if you would like to set up your own tenant.

We would like to invite you for an online info/feedback meeting. It is about a special topic in which we want to position the CaptainCasa Framework a little stronger: the design of a workplace that has access to dialogs from various services. Let’s call it a “cross-service workplace”.

Scenarios are for example:
1. Merging of non-CaptainCasa dialogs with CaptainCasa dialogs
2. Merging of CaptainCasa dialogs from various CaptainCasa applications
3. General mixing of UIs of different services

Or something more abstract: the merging of micro-frontends (== dialogs of a micro-service) into a multi-layered user workstation. Lovely CaptainCasa has not only thought about this, but also hacked something – and that’s exactly what I want to show you – and subject it to your feedback.

The meeting takes place at Thursday, Oct 28th, at 15:00h (German time zone). Expected duration: 45 minutes. Please check all the details, including the Zoom-link >HERE<.

The move from Java EE to Jakarta EE means some updating of package names. Example: what was “javax.servlet.*” in Java EE now is “jakarta.servlet.*” in Jakarta EE. – Maybe you already have experienced this when installing existing applications with Tomcat 10 – having received corresponding ClassNotFound-exceptions…

CaptainCasa as framework now comes in two variants:

• The Java EE variant (“default” variant)
• The Jakarta EE variant

You find corresponding downloads both on our download page and in our Maven repository.

Jakarta EE is still quite young. Nearly all Java server projects are based on Java EE – and moving an application from Java EE to Jakarta EE means quite high effort: you not only have to do some renaming within your own classes, but also need to update all your dependencies which internally reference corresponding “javax.*” classes. – Many projects are using Spring, which uses Java EE, and which is not available for Jakarta EE currently.

For all existing users of CaptainCasa:

• Is there anything to do on your side? – No! Just continue to use the  “Java EE” variant of CaptainCasa.
• Should you plan to move to Jakarta EE? – There is no requirement currently from a CaptainCasa framework perspective. The Java EE and the Jakarta EE variants are the same. Actually the Jakarta EE variant is automatically built from the Java EE variant.
• Is the move to Jakarta EE simple? – No. It’s definitely not a “by the way”-issue. Updating your code to use the new package names – this is simple. But then comes the long list of libraries that you depend on and which also need to be updated…

For new users of CaptainCasa:

• Should you start with Jakarta EE instead of Java EE? – We can only say: from a CaptainCasa perspective you can choose either the one or the other. So your decision is independent from the CaptainCasa framework. – If you plan to use Spring: no chance, currently, to go with Jakarta EE, so stay with Java EE.

We updated the Component Reference – which not contains both the API documentation and the examples from the demo workplace.

The reference can be accessed from the demo workplace and from the Layout Editor.