FAQ

Environment

• Do I need Docker? No. Standard deployment is JDK + jar + MySQL, and the docs ship no container images or orchestration files.
• Which databases are supported? MySQL first. Multi-database support is out of the core scope; when needed it arrives as a capability pack and the core stays untouched.
• Can I skip installing Gradle? Yes, the repository bundles the wrapper; always use ./gradlew.

Usage

• Can I add business modules to the core repository? No. The core holds zero business code — that is precisely the precondition for long-term maintenance. Business lives in your repository and extends through capability packs.
• Is there low-code or online form building? No. Generating code and then writing business by hand is more controllable than "complex scenarios assembled by configuration".
• Can I raise the pagination cap? Not recommended. The cap is a guardrail, not a limit; narrow the query scope instead of enlarging the page.

Permissions

• What if I forget to annotate an endpoint with authorization? Startup fails (deny by default); it never becomes a public endpoint.
• How do I sync a changed permission code? Change the constants class; the build verifies the three places agree and tells you which one you missed.
• Are data scope and role permissions the same thing? No. Roles decide whether you may act; data scope decides which rows you can see.

Upgrades

• Will an upgrade change my business code? No. Customization stays in your business repository; upgrading the core affects the core only.
• Can we change the framework core for our customer? Not recommended, and we do not accept core changes for a single customer. Needed capabilities arrive as extension points or capability packs.

Other

• How does it compare with other frameworks? The website makes no comparisons. We publish metrics and methods you can run yourself; you produce the numbers.
• Licensing and commercial use? See the license in the source repository; for commercial cooperation see the contact page on this site.