Documentation

CaptainCasa Knowledge Center

All documentation resources that you find below are loaded into the AI powered CaptainCasa Knowledge Center. You can access the information in two ways:

• Direct Prompt Access
  • The Knowledge Center provides an own prompt which you use for directly asking any development-related question about CaptainCasa Enterprise Client.
• Embed resources via MCP interface
  • Integrate the information into your own AI based prompting environment (e.g. Claude) by using the MCP interface. The URL is https://www.captaincasa.online/ccda_kbox/mcp
  • Additional information about the usage of MCP is available HERE.

General documentation

• Tutorials “First Steps”
  • How to execute first steps with CaptainCasa Enterprise Client
• Developer’s Guide
  • This is the “big documentation” behind CaptainCasa Enterprise Client
• Developer’s Guide – RISC Addons
  • Selected topics with explicit relation to the RISC client processing
• RapidApp!
  • The low-code plugin for speeding up your application development
• Installation Guide
  • How to install
• Component Reference
  • All components with all attributes
• Security Guide
  • Security is an important part of web front-ends! Read here what functions are included in the CaptainCasa runtime and how to configure.
• JavaDoc
  • The server-side API
  • The most up to date JavaDoc documentation is part of the download‘s /documentation-directory

Project Setup

• Setting up a Maven Project
  • Using Maven to create, manage and build your projects
• Setting up a Spring Boot Project
  • Using Maven to create a Spring Boot project
• Setting up a Spring Boot Project with CDI
  • Using Maven to create Spring Boot project – utilizing Spring’s CDI functions
• Setting up Spring Boot version of Toolset by Maven
  • Automatically synchronizing the toolset version with your project version

Demo Workplace

• Demo Workplace
  • The central resource for getting to know the components in detail – many examples, many XML definitions and many Java code snippets…

Specific Documentation

• Change Log
  • List of weekly changes
• Dockerizing you Application
  • Example how to transfer your application into a Docker image to be easily deploy-able
• Styling Issues
  • Selected issues and hints how to use the style management
• Tutorial – Creating a workplace
  • Step by step guide to create a workplace and a function tree for your application
• Adding Client Side Components
  • How to add own JavaScript controls to the client side.
• Page Bean Patterns
  • Splitting up the logic of complex screens into page beans
• Page Bean Component Controls
  • Building “real” controls from Page Bean implementations
• Using HotSwapAgent during development
  • Reloading classes without restarting the application
• Fail over Management
  • Transferring “wake-up-state” from one session to the next
• Subdevice Connectivity
  • How to integrate client side interfaces (Legic Card reader, serial scanner, …)
• Developing with JBoss
  • Setting up development (including hot deployment) with JBoss application server
• Model View Controller
  • Organizing your server side logic
• Using Component Adapter Binding
  • Efficiently use CaptainCasa components in typical form scenarios
• Separating projects “by .jar”
  • Splitting up into several projects and easily combine “by .jar”
• Usage of Java Server Faces (JSF)
  • Why CaptainCasa is NO traditional JSF framework
• Tomcat in a Box
  • How to start Tomcat and the Browser in “fat client mode”
• Extending the Toolset
  • Adding own plug-ins into the CaptainCasa toolset

CaptainCasa Addons

• Addon Components
  • The Addons-package contains useful components being pre-built by CaptainCasa as Page Bean Components.
  • The JavaDoc for the addons is available HERE
• CCEE CaptainCasa “Enterprise Edition”
  • The CCEE library is a usefule collection of server side frameworks to simplify application development: managing persistence, job scheduling, etc.
  • The JavaDoc for the CCEE package is available HERE
• CaptainCasa Spring Integration
  • Usage of Spring, so that for example UI-classes are loaded by Spring context definitions.
• Cluster and Version Manager
  • Simple setup of cluster scenarios, in which multiple nodes take over the processing
  • Management of versions in a way that system upgrades do not interrupt users