So I think ColdSpring made a very good showing at the conference - even if just considering the number of excellent questions we were asked in the hallways, bar, etc. AOP was in full-force, with a lot of folks bouncing great ideas for usage of Chris and I. Not one "so all it does is logging?" was heard.
So with that said, I thought I'd update this list on some of the cool new features we've discussed (and even implemented). 1) During one of Joe Rinehart's pre-conference talks, it was asked whether a regular java Spring BeanFactory could bet set as a parent of a ColdSpring BeanFactory. We actually didn't know for sure whether it would work - and I played with this the whole way home. Turned out we needed to write a little adapter class (you wrap your Java Spring BeanFactory in an instance of coldspring.beans.util.JavaSpringBeanFactoryAdapter and then pass that to a setParent() method on a regular ColdSpring BeanFactory). For reference: http://code.coldspringframework.org/browse/CSP-63 2) AutoProxying - Those of you who saw and learned how ColdSpring's AOP framework is used may have drawn the conclusion that there's a lot of verbosity to the configuration of a single proxy (applying AOP to a single component takes a rather large definition in the xml). As you can imagine, this could become a serious pain if you wanted to apply advice across your entire codebase. What autoproxying does is allow you to configure an advisor that will not only match method signatures, but also the names/types of components, so that you can configure a single proxy to apply advice across an entire beanFactory. 3) Expanded pointcut model - Chris is also working on expanding the way that you can configure the mappedNames property of an advisor (the string pattern you use to map an advisor to methods being called). Right now you just are concerned with the name of the method being called - the expanded syntax would also allow you to match arguments - meaning if you only wanted to apply advice when a numeric value between 100 and 150 was passed to a certain method, you could express that via the expanded pointcut syntax. 4) Whatever you think is missing from ColdSpring 1.0 Have a great holiday weekend! thanks, Dave
