Cascade Referenced Missing Classpath Resource
Application fails to start with 'resource not found' error after Cascade generated code that references files that don't exist. This might be templates, configuration files, or other classpath resources.
Cascade generated code assuming files exist but didn't verify they're actually present.
Error Messages You Might See
Common Causes
- Cascade referenced template that doesn't exist: ResourceLoader.getResource('classpath:templates/missing.html')
- Configuration file path incorrect or file not in resources directory
- Cascade generated code for file that should be created but wasn't
How to Fix It
Check error message for resource path. Verify file exists in src/main/resources at correct location. Review Cascade-generated code for hardcoded paths. Create missing files if needed. Use IDE file search to locate actual files. Verify Maven/Gradle correctly includes src/main/resources in build output.
Real developers can help you.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
Where are classpath resources located?
src/main/resources directory. Files are copied to build/resources/main in compiled output.
How do I load classpath resources?
Use ResourceLoader, ClassPathResource, or Spring's @Value. Verify file exists in src/main/resources.