Closed ggotti closed 6 years ago
Ok that's my fault - I had the idea that WARs were not used anymore, and that's still the case here. We should put the file back, it doesn't cost much and solves the issue.
I just added back the file, but no time to test the AWS sub-generator yet
Thanks @ggotti this works now perfectly, following commit https://github.com/jhipster/generator-jhipster/commit/0269dae888b0487305129d4a5fdcb00b9dae3864
Overview of the issue
When the AWS Subgenerator successfully deploys an Application to AWS, the html page screen appears, but all services return a 404.
The issue is the WAR generated in the new JHipster 5.0x version does not have the necessary SpringBootServletInitializer code to allow the WAR to be scanned correctly by Tomcat; it appears that this functionality was previously in the "_ApplicationWebXml.java" file.
Motivation for or Use Case
Feature doesn't work.
Reproduce the error
jhipster aws
generator. Get a coffee.Related issues
7061, #7086, #7457
Suggest a Fix
JHipster Version(s)
JHipster configuration, a
.yo-rc.json
file generated in the root folder.yo-rc.json file
JDL for the Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryJDL entity definitions
Environment and Tools
java version "1.8.0_121" Java(TM) SE Runtime Environment (build 1.8.0_121-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
git version 2.16.2
node: v8.9.4
npm: 5.6.0
yeoman: 1.8.5
yarn: 1.5.1
Docker version 18.03.0-ce, build 0520e24
docker-compose version 1.20.1, build 5d8c71b
Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryBrowsers and Operating System