Prompt for the ProtocolApp

Please create a React-JS application for the ProtocolModule. The application  has to offer the following views for the user interface: 
    1. ProtocolView 
    2. ProtocolFeatureView 
    3. StockListingView 
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 ProtocolView must contain the following fields: 
    - name: Description   type: STRING 
    - name: InitialReleaseDate   type: DATE 
    - name: IsOpenStandard   type: BOOL 
    - name: Name   type: STRING 
An existing Protocol entity should be loaded from the relative URL: 
    "/ProtocolService/protocol/{id}"   (HTTP-GET) 
If a new Protocol entity has been created, the new entity should be posted to the relative URL: 
    "/ProtocolService/protocol"   (HTTP-POST) 
If an existing Protocol entity has been updated, the modified entity should be sent to the relative URL: 
    "/ProtocolService/protocol/{id}"   (HTTP-PUT) 
If an existing Protocol entity has to be deleted, the following relative URL should be called: 
    "/ProtocolService/protocol/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ProtocolFeature columns: 
    - column: Description 
    - column: Protocol 
    - column: Name 
The table should have the title "ProtocolFeatures" und the data must be loaded from the server with the following relative URL: 
    "/ProtocolService/protocolfeature/protocol/{id}" 
Add a HTML table to the view with the following ProtocolParticipant columns: 
    - column: Role 
    - column: Protocol 
    - column: Company 
The table should have the title "ProtocolParticipants" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/protocolparticipant/protocol/{id}"

2. The ProtocolFeatureView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: Protocol   type: Protocol 
The data source for the [Protocol] select control should be loaded from the relative URL: 
    "/ProtocolService/protocol"   (HTTP-GET) 
An existing ProtocolFeature entity should be loaded from the relative URL: 
    "/ProtocolService/protocolfeature/{id}"   (HTTP-GET) 
If a new ProtocolFeature entity has been created, the new entity should be posted to the relative URL: 
    "/ProtocolService/protocolfeature"   (HTTP-POST) 
If an existing ProtocolFeature entity has been updated, the modified entity should be sent to the relative URL: 
    "/ProtocolService/protocolfeature/{id}"   (HTTP-PUT) 
If an existing ProtocolFeature entity has to be deleted, the following relative URL should be called: 
    "/ProtocolService/protocolfeature/{id}"   (HTTP-DELETE)

3. The StockListingView must contain the following fields: 
    - name: Company   type: Company 
    - name: DelistingDate   type: DATE 
    - name: Exchange   type: STRING 
    - name: IndexName   type: STRING 
    - name: ListingDate   type: DATE 
    - name: ListingType   type: STRING 
    - name: Ticker   type: STRING 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing StockListing entity should be loaded from the relative URL: 
    "/ProtocolService/stocklisting/{id}"   (HTTP-GET) 
If a new StockListing entity has been created, the new entity should be posted to the relative URL: 
    "/ProtocolService/stocklisting"   (HTTP-POST) 
If an existing StockListing entity has been updated, the modified entity should be sent to the relative URL: 
    "/ProtocolService/stocklisting/{id}"   (HTTP-PUT) 
If an existing StockListing entity has to be deleted, the following relative URL should be called: 
    "/ProtocolService/stocklisting/{id}"   (HTTP-DELETE)