» Home > Documentation
Remember you can get more information about JRapid joining our mailing list or following us on Twitter.
Read this starting guide if you want to get started with JRapid.
Read this starting guide if you want to start using JRapid with Eclipse.
A helpful guide that you may need when deploying JRapid apps to your own server.
Document type definition file for the JRapid input file.
Read this starting guide if you want to build a sample app for testing
JRapid entities are the key elements for modeling data. Entities can be database tables like a company, a seller, a user, a product, etc or they can be transient entities (also called "verb" entities) like login, change password, discard, etc.
JRapid defines subsets in order to get a restricted collection of instances (records) of an entity.
Listings are the way of showing the existing instances of an entity in the database. They provide access to the whole dataset also allowing filtering, ordering and action execution on each instance.
Defaultsets assign a set of default values for entity's properties. They can be also called "entities initializers". These default values can be fixed values like the default value of a property or dynamic values.
Actions are hooks (buttons, links, selects) that can be added to JRapid applications in different locations (local, form, select, button).
Panels are flat HTML pages that merge specific components of the application (like listings, forms, plain HTML and reports).
The "transient" attribute for an entity specifies that the entity will not be persisted in the database. Transient entities are common when using "related-entity" actions.
JRapid provides integration with reporting tools. Initially, it allows developers to easily include reports designed for Jasper Reports. Reports can be fully parameterized through JRapid generated screens.
Learn how to build RESTful Web Services using JRapid.
Users, privileges, roles and authentication are very common issues to take into account during an application development process.
Naming conventions are important for making project understanding easier to developers. Check our recommendations.