Skip to content
Model Layer Implementation for a J2EE Pull MVC WebApp
Java TSQL
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
modality-api-client
modality-api-server
modality-core
modality-examples
modality-webapp-auth
modality-webapp-oauth-client
modality-webapp-oauth-server
modality-webapp
src/site
velocity-tools-apiclient
velocity-tools-model
.gitignore
LICENSE
README.md
pom.xml

README.md

Modality

Modality is a set of tools which stick to the J2EE and JDBC standards to provide a lightweight, loosely coupled and highly cusomizable MVC architecture based on the Java J2EE servlets API.

Its design is based on a bottom-up approach rather than top-down. This makes Modality an anti-framework: its various components do stick to the underlying norms, have a minimal interdependance and just do the specific task they are intended to, leveraging the learning curve and added complexity, and nevertheless those components assembly covers all the basic needs of a fully functional MVC webapp.

  • the Model layer is addressed with a generic ORM Java API witouth any code generation and with minimal optional caching, providing a complete database structure reverse enginering feature.
  • the View layer is Apache Velocity, but other Java View layer technologies can easily be used instead.
  • there is no centralized Controller, but rather a set of configuration files (like WEB-INF/web.xml, the webapp application descriptor), conventions and helpers, plus any standalone controller implemented as a J2EE filter (like a form data validation one) can easily be added.

Child modules:

You can’t perform that action at this time.