Prompt for the GerichtstypApp

Please create a React-JS application for the GerichtstypModule. The application  has to offer the following views for the user interface: 
    1. GerichtstypView 
    2. RichterView 
    3. SpruchkoerperMitgliedView 
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 GerichtstypView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Ebene   type: LONG 
    - name: Name   type: STRING 
An existing Gerichtstyp entity should be loaded from the relative URL: 
    "/GerichtstypService/gerichtstyp/{id}"   (HTTP-GET) 
If a new Gerichtstyp entity has been created, the new entity should be posted to the relative URL: 
    "/GerichtstypService/gerichtstyp"   (HTTP-POST) 
If an existing Gerichtstyp entity has been updated, the modified entity should be sent to the relative URL: 
    "/GerichtstypService/gerichtstyp/{id}"   (HTTP-PUT) 
If an existing Gerichtstyp entity has to be deleted, the following relative URL should be called: 
    "/GerichtstypService/gerichtstyp/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Gericht columns: 
    - column: Name 
    - column: Postleitzahl 
    - column: IstErsteInstanz 
    - column: Bundesland 
    - column: Strasse 
    - column: IstLetzteInstanz 
    - column: Gerichtstyp 
    - column: Stadt 
The table should have the title "Gerichts" und the data must be loaded from the server with the following relative URL: 
    "/GerichtService/gericht/gerichtstyp/{id}"

2. The RichterView must contain the following fields: 
    - name: Ernennungsdatum   type: DATE 
    - name: Gericht   type: Gericht 
    - name: IstBerufsrichter   type: BOOL 
    - name: Nachname   type: STRING 
    - name: Titel   type: STRING 
    - name: Vorname   type: STRING 
The data source for the [Gericht] select control should be loaded from the relative URL: 
    "/GerichtService/gericht"   (HTTP-GET) 
An existing Richter entity should be loaded from the relative URL: 
    "/GerichtstypService/richter/{id}"   (HTTP-GET) 
If a new Richter entity has been created, the new entity should be posted to the relative URL: 
    "/GerichtstypService/richter"   (HTTP-POST) 
If an existing Richter entity has been updated, the modified entity should be sent to the relative URL: 
    "/GerichtstypService/richter/{id}"   (HTTP-PUT) 
If an existing Richter entity has to be deleted, the following relative URL should be called: 
    "/GerichtstypService/richter/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following SpruchkoerperMitglied columns: 
    - column: Spruchkoerper 
    - column: Rolle 
    - column: Richter 
The table should have the title "SpruchkoerperMitglieds" und the data must be loaded from the server with the following relative URL: 
    "/GerichtstypService/spruchkoerpermitglied/richter/{id}"

3. The SpruchkoerperMitgliedView must contain the following fields: 
    - name: Richter   type: Richter 
    - name: Rolle   type: STRING 
    - name: Spruchkoerper   type: Spruchkoerper 
The data source for the [Spruchkoerper] select control should be loaded from the relative URL: 
    "/GerichtService/spruchkoerper"   (HTTP-GET) 
The data source for the [Richter] select control should be loaded from the relative URL: 
    "/GerichtstypService/richter"   (HTTP-GET) 
An existing SpruchkoerperMitglied entity should be loaded from the relative URL: 
    "/GerichtstypService/spruchkoerpermitglied/{id}"   (HTTP-GET) 
If a new SpruchkoerperMitglied entity has been created, the new entity should be posted to the relative URL: 
    "/GerichtstypService/spruchkoerpermitglied"   (HTTP-POST) 
If an existing SpruchkoerperMitglied entity has been updated, the modified entity should be sent to the relative URL: 
    "/GerichtstypService/spruchkoerpermitglied/{id}"   (HTTP-PUT) 
If an existing SpruchkoerperMitglied entity has to be deleted, the following relative URL should be called: 
    "/GerichtstypService/spruchkoerpermitglied/{id}"   (HTTP-DELETE)