Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum
Prompt for the
HafenApp
Please create a React-JS application for the HafenModule. The application has to offer the following views for the user interface: 1. FaehrenRouteView 2. HafenView 3. HafenVerkehrsStatistikView 4. KvTerminalView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below. 1. The FaehrenRouteView must contain the following fields: - name: HafenStart type: Hafen - name: HafenZiel type: Hafen - name: IstFracht type: BOOL - name: IstPassagier type: BOOL - name: Name type: STRING - name: Notizen type: STRING - name: Region type: STRING The data source for the [HafenZiel] select control should be loaded from the relative URL: "/HafenService/hafen" (HTTP-GET) The data source for the [HafenStart] select control should be loaded from the relative URL: "/HafenService/hafen" (HTTP-GET) An existing FaehrenRoute entity should be loaded from the relative URL: "/HafenService/faehrenroute/{id}" (HTTP-GET) If a new FaehrenRoute entity has been created, the new entity should be posted to the relative URL: "/HafenService/faehrenroute" (HTTP-POST) If an existing FaehrenRoute entity has been updated, the modified entity should be sent to the relative URL: "/HafenService/faehrenroute/{id}" (HTTP-PUT) If an existing FaehrenRoute entity has to be deleted, the following relative URL should be called: "/HafenService/faehrenroute/{id}" (HTTP-DELETE) 2. The HafenView must contain the following fields: - name: IstInselHafen type: BOOL - name: IstKleinHafen type: BOOL - name: IstKvStandort type: BOOL - name: IstSeeHafen type: BOOL - name: Name type: STRING - name: Notizen type: STRING - name: Ort type: STRING - name: Region type: STRING An existing Hafen entity should be loaded from the relative URL: "/HafenService/hafen/{id}" (HTTP-GET) If a new Hafen entity has been created, the new entity should be posted to the relative URL: "/HafenService/hafen" (HTTP-POST) If an existing Hafen entity has been updated, the modified entity should be sent to the relative URL: "/HafenService/hafen/{id}" (HTTP-PUT) If an existing Hafen entity has to be deleted, the following relative URL should be called: "/HafenService/hafen/{id}" (HTTP-DELETE) Add a HTML table to the view with the following FaehrenRoute columns: - column: Notizen - column: IstFracht - column: Name - column: Region - column: HafenZiel - column: IstPassagier - column: HafenStart The table should have the title "FaehrenRoutes" und the data must be loaded from the server with the following relative URL: "/HafenService/faehrenroute/hafenziel/{id}" Add a HTML table to the view with the following FaehrenRoute columns: - column: Notizen - column: IstFracht - column: Name - column: Region - column: HafenZiel - column: IstPassagier - column: HafenStart The table should have the title "FaehrenRoutes" und the data must be loaded from the server with the following relative URL: "/HafenService/faehrenroute/hafenstart/{id}" Add a HTML table to the view with the following KvTerminal columns: - column: Notizen - column: Name - column: Ort - column: IstGeplant - column: Hafen - column: EroeffnungsJahr The table should have the title "KvTerminals" und the data must be loaded from the server with the following relative URL: "/HafenService/kvterminal/hafen/{id}" Add a HTML table to the view with the following HafenVerkehrsStatistik columns: - column: Hafen - column: IstBvwpBezug - column: VerkehrsStatistik - column: IstPrognose The table should have the title "HafenVerkehrsStatistiks" und the data must be loaded from the server with the following relative URL: "/HafenService/hafenverkehrsstatistik/hafen/{id}" Add a HTML table to the view with the following InfrastrukturProjektHafen columns: - column: InfrastrukturProjekt - column: Hafen - column: Rolle The table should have the title "InfrastrukturProjektHafens" und the data must be loaded from the server with the following relative URL: "/WasserstrasseService/infrastrukturprojekthafen/hafen/{id}" 3. The HafenVerkehrsStatistikView must contain the following fields: - name: Hafen type: Hafen - name: IstBvwpBezug type: BOOL - name: IstPrognose type: BOOL - name: VerkehrsStatistik type: VerkehrsStatistik The data source for the [VerkehrsStatistik] select control should be loaded from the relative URL: "/StudieService/verkehrsstatistik" (HTTP-GET) The data source for the [Hafen] select control should be loaded from the relative URL: "/HafenService/hafen" (HTTP-GET) An existing HafenVerkehrsStatistik entity should be loaded from the relative URL: "/HafenService/hafenverkehrsstatistik/{id}" (HTTP-GET) If a new HafenVerkehrsStatistik entity has been created, the new entity should be posted to the relative URL: "/HafenService/hafenverkehrsstatistik" (HTTP-POST) If an existing HafenVerkehrsStatistik entity has been updated, the modified entity should be sent to the relative URL: "/HafenService/hafenverkehrsstatistik/{id}" (HTTP-PUT) If an existing HafenVerkehrsStatistik entity has to be deleted, the following relative URL should be called: "/HafenService/hafenverkehrsstatistik/{id}" (HTTP-DELETE) 4. The KvTerminalView must contain the following fields: - name: EroeffnungsJahr type: LONG - name: Hafen type: Hafen - name: IstGeplant type: BOOL - name: Name type: STRING - name: Notizen type: STRING - name: Ort type: STRING The data source for the [Hafen] select control should be loaded from the relative URL: "/HafenService/hafen" (HTTP-GET) An existing KvTerminal entity should be loaded from the relative URL: "/HafenService/kvterminal/{id}" (HTTP-GET) If a new KvTerminal entity has been created, the new entity should be posted to the relative URL: "/HafenService/kvterminal" (HTTP-POST) If an existing KvTerminal entity has been updated, the modified entity should be sent to the relative URL: "/HafenService/kvterminal/{id}" (HTTP-PUT) If an existing KvTerminal entity has to be deleted, the following relative URL should be called: "/HafenService/kvterminal/{id}" (HTTP-DELETE)
Copy prompt
Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum