How kriolos/kriolos-obiz works
Main components
• Build & CI environment
– GitHub Actions workflow (build.yml)
– Maven Wrapper & root pom.xml (multi-module aggregator)
• Maven modules (subprojects)
– application: core business logic & tests
– branding: NetBeans branding layer (NBM)
– kriolos-obiz-libs: shared libraries (je, krpos)
– kriolos-opos-nbm: POS UI + embedded web server (NBM)
– kriolos-obiz-suite: NetBeans RCP application aggregator
– unicenta-pos: integration or extension (placeholder)
• Runtime platform
– NetBeans Rich-Client Platform (core modules: window system, lifecycle, lookup)
– Deployed NBM modules: branding, application logic, POS UI/server
• Embedded server & handlers
– WebServer (HTTP listener)
– SaleDocHandler, SaleDoc (REST endpoints)
Relationships & interactions
• Build-time dependencies
– The root pom.xml declares modules → each submodule has its own pom.xml
– kriolos-obiz-suite depends on all NBM modules + NetBeans platform dependencies
– application, branding, kriolos-opos-nbm depend on kriolos-obiz-libs
• Runtime composition
– NetBeans Platform loads NBM modules (branding first, then core, then POS UI)
– POS UI components (PosTopComponent, SettingsTopComponent) invoke business APIs in application module
– POS UI also communicates (via HTTP) with the embedded WebServer in the same JVM
– Handlers in the server module process incoming requests, call into application/core libs for data manipulation
Architectural patterns & design principles
• Plugin modularity (NetBeans Platform)
• Separation of concerns
– UI layer (NBM GUI)
– Business logic (application module + shared libs)
– Infrastructure (embedded HTTP server module)
– Branding/theme (branding NBM)
• Maven multi-module structure for clear build isolation
• Use of NetBeans Lookup for loose coupling between modules
• Clear component labels (module names + roles)
– Build → packaging dependencies
– Module loading sequence in RCP
– Data flow (UI → core logic, UI → server, server → handler → libs)