The OData Boilerplate combines OpenUI5 with Spring Boot, OLingo and JPA and allows you to easily and quickly boot up a JVM based OData app based on modeling your data model in using JPA.
For convenience, a base-diagram for the JPA diagram editor has been provided as well. Once your data model is finished, the application with update the database schema of the connected database on first run. After every change and restart, the application will attempt to alter the database schema according to the changes detected in the JPA model.
By default, the application comes with just one entity: Members, that is automatically populated with a few names from Application.java
Once the application is running, you can browse to http://localhost:8080 to run the sample OpenUI5 application that is using the OData service. The service itself is available from http://localhost:8080/odata.svc
- Deploys on any VM, including Tomcat, HANA Cloud Platform, Azure, but also on plain Java using built-in Tomcat
- Full CRUD support on all JPA entities
- Feature-complete OData v2 support, including $filter, $expand, $select, $count, $top, etc
- Language dependent annotation support for Smart controls (through i18n.properties files)
- Connects to most SQL databases, including SQL server, HANA, MySQL, HSQLDB, Derby
- Automatically creates database schema based on JPA model
To be able to run this application, you need Java JDK 1.7 (or higher) and Maven.
To install the boilerplate, you can just clone this repository to your computer.
After cloning it, set the connection parameters to connect to a database in application.properties
To run the application just enter mvn spring-boot:run -P jar
To stop the application press control-C
To build a jar run mvn clean package
To run the jar mvn -jar target/odata-0.1.0.jar
The boilerplate is compatible with both the local as well as the cloud-runtime of HANA cloud platform and will compile to a WAR when Maven profile 'hcp' is selected (which happens to be the default ;).
When the application is run on the HCP cloud, it will automatically connect to the default database connection and start updating the database schema there. It is of couse still possible to connect the Java application to another data-source using the cockpit.
When you run the application from Eclipse on a local HANA Cloud Platform runtime, the site will be available on http://localhost:8080/odata. Also, through configuration of web.xml, authentication is switched on. When you run the application on a local HCP runtime without modifying web.xml, you need to add a user to your local server. You can do this by double clicking your HCP local server and adding a user to the 'users' tab.
To get the application running on Azure, it is probably easiest to compile the app to a jar using mvn -P jar, After that, you can just pick up the jar file from the target directory and FTP it into an Azure web application. To make Azure aware of the jar file, point the web.config to the jar file, as described on this page: https://azure.microsoft.com/documentation/articles/web-sites-java-custom-upload/#springboot
To make the logging go into the right directory, make sure this line is present in the application.properties file in the resources directory: logging.path = D://home//LogFiles. You may also want to remove the logback.xml from the resources directory, which is required for HANA Cloud Platform, but not for Azure.
The only reason that the repository package is there, is because I liked the boilerplate to create some initial (demo/test) data on first launch. However, if you don't need this, it is safe to remove the repository package. It is not necessary to create a repository class for every entity in the model and only modelling entity classes will suffice when you just want to have tables in the database and expose them through OData.
There are some limited (for now) features to add annotations allowing you to leverage smart controls and templates. At this moment it is possible to add annotations on attribute level by applying the @Sap annotation and/or @SAPLineItem just before the attribute definition, e.g.:
@Sap(filterable=true, sortable=true)
@SAPLineItem
private String lastName;
The sap:label annotation with a language dependent label is automatically added, if the label has been defined in an i18n table in the resources directory. i18n-tags should be formatted according to . notation, for example: Member.LastName=Achternaam. A sample i18n table has been provided in the boilerplate.
Applying the @SAP annotation will result in SAP annotations being added in an almost similar to what SAP Gateway would do:
<Property
Name="LastName" Type="Edm.String"
sap:label="Achternaam"
sap:filterable="true" sap:updatable="false" sap:sortable="true" sap:creatable="false"
xmlns:sap="http://www.sap.com/Protocols/SAPData"/>
Applying the @SAPLineItem annotation will add the annotated property to the UI.LineItem section, which contains the default fields show in the Smart Table control.
Please note that the annotations feature is not complete, but can very easily be extended when you leverage the boilerplate logic provided in JPAEdmExtension.
- Fork it!
- Create your feature branch:
git checkout -b my-new-feature - Commit your changes:
git commit -am 'Add some feature' - Push to the branch:
git push origin my-new-feature - Submit a pull request :D
To have a look at the boilerplate output, please have a look at any of these urls:
- Sample OpenUI5 app: http://odataboilerplate.azurewebsites.net/
- OData endpoint: http://odataboilerplate.azurewebsites.net/odata.svc/
- OData metadata: http://odataboilerplate.azurewebsites.net/odata.svc/$metadata
This software is published under MIT license.
Please refer to LICENSE.TXT for more details