I originally developed an AngularJS + Spring MVC application, named A. I duplicated this web application by copying and pasting the project folder into another one called B.
After running both applications, I noticed they exhibited identical behavior.
My objective is to simplify application A, starting with refactoring the folders containing .html files.
The current folder structure for A is as follows:
src/main/webapp
|--- WEB-INF/
|--- META-INF/
|--- static/
|--- js/
|--- css/
|--- index.html
|--- sth.html
The updated folder structure for B looks like this:
src/main/webapp
|--- META-INF/
|--- js/
|--- css/
|--- index.html
|--- sth.html
To summarize, I moved all resources from the 'static' folder up a level.
Next, I need to modify the WebMvcConfigurerAdapter in A starting with the old configuration:
@Configuration
@EnableWebMvc
@ComponentScan(basePackages = "my.package.name")
public class Configurations extends WebMvcConfigurerAdapter {
// Code here...
}
I plan to create a new WebMvcConfigurerAdapter for B:
@Configuration
@EnableWebMvc
@ComponentScan(basePackages = "my.package.name")
public class Configurations extends WebMvcConfigurerAdapter {
// Code here...
}
In essence, I removed the 'static/' prefix from each path.
However, upon running the application, I encountered an Error 500 when requesting 'sth', even though 'index.html' displayed correctly.
GET http://localhost:8080/MyWebApp/sth 500 (Internal Server Error)
Tomcat kept logging a StackOverflowError exception repeatedly.
SEVERE: Servlet.service() for servlet dispatcher threw exception
java.lang.StackOverflowError
at javax.servlet.ServletRequestWrapper.getRemoteAddr(ServletRequestWrapper.java:221)
at javax.servlet.ServletRequestWrapper.getRemoteAddr(ServletRequestWrapper.java:221)
at javax.servlet.ServletRequestWrapper.getRemoteAddr(ServletRequestWrapper.java:221)
// More stack trace...
This issue seems related to the controllers and routing within the AngularJS app. Here is an example of the index controller:
@Controller
@RequestMapping("/")
public class IndexController {
// Code here...
}
Furthermore, the controller responsible for the 'sth' page:
@Controller
public class TemplateController {
// Code here...
}
The AngularJS router setup within the app.js file:
// Angular code here...
Lastly, the controller handling 'sth' functionality:
// Controller code here...
It appears that there might be something crucial missing, possibly due to front-end structural issues or configuration oversights. My limited experience with AngularJS and Spring MVC makes it challenging to identify the root cause of the problem.