Prompt for the ConferenceApp

Please create a React-JS application for the ConferenceModule. The application  has to offer the following views for the user interface: 
    1. ConferenceView 
    2. ConferenceAttendeeView 
    3. ConferenceItemView 
    4. ConferenceTypeView 
    5. EventTaskDependencyView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below.

1. The ConferenceView must contain the following fields: 
    - name: FromDate   type: DATE 
    - name: ToDate   type: DATE 
    - name: ConferenceType   type: ConferenceType 
    - name: Room   type: Room 
The data source for the [ConferenceType] select control should be loaded from the relative URL: 
    "/ConferenceService/conferencetype"   (HTTP-GET) 
The data source for the [Room] select control should be loaded from the relative URL: 
    "/RoomService/room"   (HTTP-GET) 
An existing Conference entity should be loaded from the relative URL: 
    "/ConferenceService/conference/{id}"   (HTTP-GET) 
If a new Conference entity has been created, the new entity should be posted to the relative URL: 
    "/ConferenceService/conference"   (HTTP-POST) 
If an existing Conference entity has been updated, the modified entity should be sent to the relative URL: 
    "/ConferenceService/conference/{id}"   (HTTP-PUT) 
If an existing Conference entity has to be deleted, the following relative URL should be called: 
    "/ConferenceService/conference/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ConferenceAttendee columns: 
    - column: Teacher 
    - column: ExternalPerson 
    - column: Conference 
    - column: Student 
The table should have the title "ConferenceAttendees" und the data must be loaded from the server with the following relative URL: 
    "/ConferenceService/conferenceattendee/conference/{id}" 
Add a HTML table to the view with the following ConferenceItem columns: 
    - column: ItemTitle 
    - column: Conference 
    - column: DocumentPath 
The table should have the title "ConferenceItems" und the data must be loaded from the server with the following relative URL: 
    "/ConferenceService/conferenceitem/conference/{id}"

2. The ConferenceAttendeeView must contain the following fields: 
    - name: ExternalPerson   type: ExternalPerson 
    - name: Conference   type: Conference 
    - name: Teacher   type: Teacher 
    - name: Student   type: Student 
The data source for the [ExternalPerson] select control should be loaded from the relative URL: 
    "/ExternalPersonService/externalperson"   (HTTP-GET) 
The data source for the [Teacher] select control should be loaded from the relative URL: 
    "/StudentService/teacher"   (HTTP-GET) 
The data source for the [Student] select control should be loaded from the relative URL: 
    "/StudentService/student"   (HTTP-GET) 
The data source for the [Conference] select control should be loaded from the relative URL: 
    "/ConferenceService/conference"   (HTTP-GET) 
An existing ConferenceAttendee entity should be loaded from the relative URL: 
    "/ConferenceService/conferenceattendee/{id}"   (HTTP-GET) 
If a new ConferenceAttendee entity has been created, the new entity should be posted to the relative URL: 
    "/ConferenceService/conferenceattendee"   (HTTP-POST) 
If an existing ConferenceAttendee entity has been updated, the modified entity should be sent to the relative URL: 
    "/ConferenceService/conferenceattendee/{id}"   (HTTP-PUT) 
If an existing ConferenceAttendee entity has to be deleted, the following relative URL should be called: 
    "/ConferenceService/conferenceattendee/{id}"   (HTTP-DELETE)

3. The ConferenceItemView must contain the following fields: 
    - name: ItemTitle   type: STRING 
    - name: Conference   type: Conference 
    - name: DocumentPath   type: STRING 
The data source for the [Conference] select control should be loaded from the relative URL: 
    "/ConferenceService/conference"   (HTTP-GET) 
An existing ConferenceItem entity should be loaded from the relative URL: 
    "/ConferenceService/conferenceitem/{id}"   (HTTP-GET) 
If a new ConferenceItem entity has been created, the new entity should be posted to the relative URL: 
    "/ConferenceService/conferenceitem"   (HTTP-POST) 
If an existing ConferenceItem entity has been updated, the modified entity should be sent to the relative URL: 
    "/ConferenceService/conferenceitem/{id}"   (HTTP-PUT) 
If an existing ConferenceItem entity has to be deleted, the following relative URL should be called: 
    "/ConferenceService/conferenceitem/{id}"   (HTTP-DELETE)

4. The ConferenceTypeView must contain the following fields: 
    - name: Description   type: STRING 
    - name: TypeName   type: STRING 
An existing ConferenceType entity should be loaded from the relative URL: 
    "/ConferenceService/conferencetype/{id}"   (HTTP-GET) 
If a new ConferenceType entity has been created, the new entity should be posted to the relative URL: 
    "/ConferenceService/conferencetype"   (HTTP-POST) 
If an existing ConferenceType entity has been updated, the modified entity should be sent to the relative URL: 
    "/ConferenceService/conferencetype/{id}"   (HTTP-PUT) 
If an existing ConferenceType entity has to be deleted, the following relative URL should be called: 
    "/ConferenceService/conferencetype/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Conference columns: 
    - column: ToDate 
    - column: Room 
    - column: FromDate 
    - column: ConferenceType 
The table should have the title "Conferences" und the data must be loaded from the server with the following relative URL: 
    "/ConferenceService/conference/conferencetype/{id}"

5. The EventTaskDependencyView must contain the following fields: 
    - name: Source   type: EventTask 
    - name: Destination   type: EventTask 
The data source for the [Destination] select control should be loaded from the relative URL: 
    "/StudentService/eventtask"   (HTTP-GET) 
The data source for the [Source] select control should be loaded from the relative URL: 
    "/StudentService/eventtask"   (HTTP-GET) 
An existing EventTaskDependency entity should be loaded from the relative URL: 
    "/ConferenceService/eventtaskdependency/{id}"   (HTTP-GET) 
If a new EventTaskDependency entity has been created, the new entity should be posted to the relative URL: 
    "/ConferenceService/eventtaskdependency"   (HTTP-POST) 
If an existing EventTaskDependency entity has been updated, the modified entity should be sent to the relative URL: 
    "/ConferenceService/eventtaskdependency/{id}"   (HTTP-PUT) 
If an existing EventTaskDependency entity has to be deleted, the following relative URL should be called: 
    "/ConferenceService/eventtaskdependency/{id}"   (HTTP-DELETE)