Add strict flag to Application.cfc to error on invalid configuration

Description

troubleshooting issues with bad configuration is very difficult due to the lack of logging. I think ALL bad configuration should throw an exception because that makes sense, but at least provide some sort of strict flag for debugging bad configuration errors with datasources, orm paths, etc. The silent failures are difficult to figure out.

Status

Assignee

Unassigned

Reporter

Brad Wood

Labels

None

Priority

New
Configure