Jetty released a headache.

There was no problem with the previous application migration. Suddenly, a bean registration error occurred when migrating an application from JBoss to jetty, prompting that the bean has been registered and there are two configuration files.

The view path is an XML in war, and there is also one under/tmp/jetty-XXXXX/webinf/WEB-INF/classes. But why didn't the previous applications conflict?

 

The camel compared to the original application is either placed under the WEB-INF, or the application first into a jar package placed in the WEB-INF/lib/, XML file is not placed in the WEB-INF/classes directory or subdirectory.

So it is not copied to/tmp/jetty-XXXXX/webinf/WEB-INF/classes. Repackage and solve the problem.