Prompt for the LiteraturApp

Please create a React-JS application for the LiteraturModule. The application  has to offer the following views for the user interface: 
    1. BaeckereiLiteraturView 
    2. GroessenklasseView 
    3. LiteraturView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The BaeckereiLiteraturView must contain the following fields: 
    - name: Baeckerei   type: Baeckerei 
    - name: Literatur   type: Literatur 
The data source for the [Baeckerei] select control should be loaded from the relative URL: 
    "/BaeckereiService/baeckerei"   (HTTP-GET) 
The data source for the [Literatur] select control should be loaded from the relative URL: 
    "/LiteraturService/literatur"   (HTTP-GET) 
An existing BaeckereiLiteratur entity should be loaded from the relative URL: 
    "/LiteraturService/baeckereiliteratur/{id}"   (HTTP-GET) 
If a new BaeckereiLiteratur entity has been created, the new entity should be posted to the relative URL: 
    "/LiteraturService/baeckereiliteratur"   (HTTP-POST) 
If an existing BaeckereiLiteratur entity has been updated, the modified entity should be sent to the relative URL: 
    "/LiteraturService/baeckereiliteratur/{id}"   (HTTP-PUT) 
If an existing BaeckereiLiteratur entity has to be deleted, the following relative URL should be called: 
    "/LiteraturService/baeckereiliteratur/{id}"   (HTTP-DELETE)

2. The GroessenklasseView must contain the following fields: 
    - name: MaximalUmsatz   type: DOUBLE 
    - name: MindestUmsatz   type: DOUBLE 
    - name: Name   type: STRING 
An existing Groessenklasse entity should be loaded from the relative URL: 
    "/LiteraturService/groessenklasse/{id}"   (HTTP-GET) 
If a new Groessenklasse entity has been created, the new entity should be posted to the relative URL: 
    "/LiteraturService/groessenklasse"   (HTTP-POST) 
If an existing Groessenklasse entity has been updated, the modified entity should be sent to the relative URL: 
    "/LiteraturService/groessenklasse/{id}"   (HTTP-PUT) 
If an existing Groessenklasse entity has to be deleted, the following relative URL should be called: 
    "/LiteraturService/groessenklasse/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BaeckereiStatistik columns: 
    - column: AnzahlMitarbeiter 
    - column: AnzahlBaeckereien 
    - column: StatistikJahr 
    - column: GesamtUmsatzMioEuro 
    - column: Groessenklasse 
    - column: AnzahlAzubis 
    - column: Land 
The table should have the title "BaeckereiStatistiks" und the data must be loaded from the server with the following relative URL: 
    "/LandService/baeckereistatistik/groessenklasse/{id}"

3. The LiteraturView must contain the following fields: 
    - name: Autor   type: STRING 
    - name: Erscheinungsjahr   type: INT 
    - name: Isbn   type: STRING 
    - name: Titel   type: STRING 
    - name: Verlag   type: STRING 
An existing Literatur entity should be loaded from the relative URL: 
    "/LiteraturService/literatur/{id}"   (HTTP-GET) 
If a new Literatur entity has been created, the new entity should be posted to the relative URL: 
    "/LiteraturService/literatur"   (HTTP-POST) 
If an existing Literatur entity has been updated, the modified entity should be sent to the relative URL: 
    "/LiteraturService/literatur/{id}"   (HTTP-PUT) 
If an existing Literatur entity has to be deleted, the following relative URL should be called: 
    "/LiteraturService/literatur/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BaeckereiLiteratur columns: 
    - column: Literatur 
    - column: Baeckerei 
The table should have the title "BaeckereiLiteraturs" und the data must be loaded from the server with the following relative URL: 
    "/LiteraturService/baeckereiliteratur/literatur/{id}"