The throw in CacheBoxProvider.cfc on line 111 puts the paramters in the order message, detail, type but that is incorrect. It's message, type, detail. This causes the error that's thrown to not be as useful since only the type shows up along with the message and no details.
Note, once this is fixed, it's super hard to read because the original message, detail, and stack trace are all crammed in the detail. Do we really need to even catch and rethrow this at all? Why don't we just let the original (and much more readable error) just bubble up?
Gliffy Diagrams
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
The throw in CacheBoxProvider.cfc on line 111 puts the paramters in the order message, detail, type but that is incorrect. It's message, type, detail. This causes the error that's thrown to not be as useful since only the type shows up along with the message and no details.
Note, once this is fixed, it's super hard to read because the original message, detail, and stack trace are all crammed in the detail. Do we really need to even catch and rethrow this at all? Why don't we just let the original (and much more readable error) just bubble up?