New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
debugger resources are 404 not found #68
Comments
Are you sure to deploy on a Servlet 3.x compatible container?
|
I'm using the lastest version of spring boot and without web.xml configuration. The embed tomcat is 8.0.2x. I think it's Servlet 3.x. |
I think it comes from the Servlet API version. Let me try to reproduce and I get back to you. |
I've tested with the spring-boot-sample-tomcat sample app. I've just added the following configuration class:
No particular issue with the debugger. Do you know what could differ between your app and the above sample? Spring Boot: 1.3.0.BUILD |
I have the same configuration in my project and I also have some other custom filters and interceptors, I don't know if that will be the problem. How can I debug for this? |
Interesting. Could you please try to configure the filter as the first one in the filter chain?
|
I found that my own resource handler cause the problem, how can I adopt the debugger with the resource handler? This is the resource handler:
|
Try:
The above will only work in a Servlet 3.x container. So it should work with Spring Boot. |
It's not working, still 404 not found. 😢 |
I'm wondering if it's an ordering issue or not.. What happens if you declare the most specific rule in first?
|
I have tried but the result is the same. |
Some logs would help. Could you please turn on DEBUG logs on |
one of the resource file:
|
Thanks! Using JavaConfig:
Or XML:
Then the custom resource handler for Dandelion shouldn't be needed. |
I have
tool.debugger = true
in the configuration and append?ddl-debug
to the url to enable debugger. Resource files are appended to html, but all of them are 404 not found. Any thing I can do with this?The text was updated successfully, but these errors were encountered: