Moqui Framework is a seamlessly integrated, enterprise-ready framework for building enterprise automation applications based on Java. It includes tools for database interaction (relational, graph, document), logic in local and web services, web and other UI with screens and forms, security, file/resource access, scripts, templates, localization, caching, logging, searching, business rules, workflow, multi-tenancy, and integration.
With the Mantle Business Artifacts add-on it is a foundation for building eCommerce, ERP, CRM, SCM, MRP, EAM, POS, etc applications.
NOTE: the code repository for Moqui is hosted on GitHub at: https://github.com/moqui/moqui
- Comprehensive 3-tier enterprise application framework: UI, service/logic, data
- Persistence facade facilitates use of relational data model throughout application instead of requiring object mapping
- API designed around a central object (ExecutionContext) that represents the state of the application and framework tools
- API includes facade interfaces for web, user, messages, l10n, resources (access, execution), logging, cache, transactions, entities, services, and screens
- Database driven authorization configurable for all artifacts (ie entities, services, screens, screen transitions, etc)
- Flexible multi-tenant support built-in (multi-database approach)
- Can run in a JEE application server or just a servlet container (Tomcat, Jetty, anywhere you can deploy a WAR file), and comes OOTB with Atomikos and Winstone for embedded use
- Deploy as a WAR file with external or embedded runtime directory, or run from command line since the war file is also an executable jar file
- Uses ehcache for distributed caching, and Quartz Scheduler for asynchronous and scheduled services (or other custom jobs)
- Security (authentication and authorization) runs through Apache Shiro and can be configured for external authentication using LDAP and other standard or custom authc systems
- Supports JSON-RPC and XML-RPC service interfaces OOTB, and includes tools for building REST-JSON and REST-XML APIs
- Written mostly in Groovy, and Groovy is the default scripting language (with easy support for adding others)
- FreeMarker is used for transforming XML Screens, Forms and Actions, and is the default template language (with support for easily adding other template engines)
- Native Apache Camel endpoints for flexible and powerful integration with other systems and applications
There are no 3 star reviews.