How tombovelo/framework works
Project type and purpose
• A FrontController to centralize all HTTP requests
• Annotation classes (@Get, @Post, @RestAPI, @Url, etc.) for mapping URLs to controller methods
• A ModelView abstraction for returning data + view name
• Wrappers for request- and session-handling (MyRequestWrapper, MySession)
• Validation and error-handling (Required, RequiredRoles, DetailedValidationException, ErrorPage)
• Utility components (MyFile, Utils)
File structure
• All classes live at top level (no subdirs). They fall into these logical packages/components:
a. Core Controller Layer: FrontController.java, Controller.java, Mapping.java, VerbAction.java
b. Annotations & Routing: Get.java, Post.java, Url.java, RestAPI.java
c. Model & View: ModelView.java, UserInterface.java
d. Request/Session Wrappers: MyRequestWrapper.java, MySession.java
e. Validation & Errors: Required.java, RequiredRoles.java, DetailedValidationException.java, DuplicateUrlException.java, BuildException.java, ErrorPage.java
f. Utilities & Helpers: MyFile.java, Params.java, Numerique.java, Utils.java
README
• The README only states “framework” and contains garbled characters—no additional architecture guidance.
Elements
• Extension points (Annotations, Validation) in another
• Utility modules (MyFile, Utils) in a third