RapidClipse automatically creates a standard project structure consisting of six main areas (packages). Thus, RapidClipse determines an application architecture that strictly separates different application layers, especially the UI layer, the data storage layer (Entities) and the data query layer (Data Access).
Entities - List of entities created for the project. In Java, entities are the counterpart to the tables in a relational database and at runtime are used as data containers that receive query results.
Data Access - List of data access objects created for the project. Usually there is a corresponding Data Access Object (DAO) for each entity that is responsible for the access to the linked data source.
Business Objects - In this area, you can create the Java classes for your own application logic.
User Interface - In this section, you can create the views for your graphical interface. The MainView.java class is the first view created by RapidClipse by default.
Themes - The SCSS files that define the theme of the application are created here.
Resources - Here is where all files that the application can access at runtime can be saved, including pictures and voice files for the internationalization of an application.
Within this standard package you can create additional packages, if required, to structure your project. However, you can also deviate from this standard structure and structure your project completely on your own using the standard Eclipse Project Explorer.
JRE System Library - Files of Java Runtime Environment.
Maven Dependencies - Required libraries which are automatically downloaded from Maven Repository and included into the RapidClipse project.
ehcache.xml - EhCache configuration file. By default, RapidClipse uses EhCache as a second-level cache for Hibernate to grant quicker database access via Hibernate.
log4j.properties - Log4J configuration file. By default, RapidClipse uses Log4J to log application messages.