I've discovered a fairly obscure failure condition for ColdSpring AOP - I havn't tracked down the ultimate source of the bug, but hopefully this might be of help.Environment
Adobe Coldfusion 9.01
ColdSpring 2a1 or ColdSpring 2 develop
AOP on beans, using AOP schemaCondition
An application based mapping named 'application', for example
this.mappings['/application'] = getDirectoryFromPath(getCurrentTemplatePath());
I was doing this to provide a general mapping to the root of my application.Outcome
When the mapping is present Coldspring AOP fails to apply, without obvious error or exception.
The bean factory contains aop-config-autoproxycreator, but the beans that would be proxied appear in their regular non-proxied form.
A fresh restart of the ColdFusion server is usually required to produce the error when the mapping is present.
Similarly removing the mapping does not correct the condition without a server restart.
Also, for some values of the mapping AOP seems to work - mostly for what would appear to be broken or nonsense values such as 'asdf'.