DefaultProperties for ColdSpring Bean Factories

So I was playing with the defaultProperties configuration as mentioned on several sites, including this article by Dan Vega that got me going down the path. I wasn’t able to get it working at first, until I did a little messing around. Turns out that this:

1
2
3

      <entry key="devFilepath">
               <value>${baseFilepath}\logs</value>
      </entry>

Won’t work. The ColdSpring engine won’t find this as a configuration to populate. Instead, you have to make sure the whole space between the tags is what you want to have replaced, like so:

1
2
3

      <entry key="devFilepath">
               <value>${devFilepath}</value>
      </entry>

Hope that helps someone out!

Limit on CFC Size?

So a few months ago I wrote a post about a java.lang.StackOverflowError I had experienced with Model-Glue and ColdSpring.   You can read about it here and here.  We it reared it’s ugly head again today.  I’m not sure exactly what is happening and maybe someone with a better knowledge of ColdSpring can help me out here.  I solved the problem by moving my new function into a different Service.cfc.  Why this worked?  I don’t know, but it seems that it has something to do with the size of the file.  It’s only running about 1500 lines in the service, but I have another service with more functions that runs 3000 lines of code.  But moving it out, definitely solves the ColdSpring compile error and allows me to move forward with development.

Any thoughts out there?

java.lang.StackOverflowError – Solution!

Okay, so this turned out to be a twofold thing. One – I had a circular reference in my ColdSpring file. BeanA needed BeanB and BeanB needed BeanA. The problem was that even though I saw this and had tried to fix it, it wouldn’t solve the problem. I still kept getting the StackOverflowError showing. Then I happened across this post which basically had a thing about the circular references and that you should use a setter injection instead of constructor injection in order to fix the problem. I hadn’t thought of using setter injection for anything other than the things autowired by ModelGlue such as my services in my controllers or the beanfactory so this was a new way of thinking of it for me. The beauty of it though was that it worked! My code now compiled.

My thanks go out to Dan Wilson for getting me pointed in the right direction on the google group for Model-Glue!

java.lang.StackOverflowError

I’ve been working on building a fairly large Model-Glue application and it’s been up and running for going on 4 months. Yesterday I was working on some of the planned enhancements when I ran into a 500 ROOT CAUSE: java.lang.StackOverflowError problem. I’ve tracked it down to one instance of adding one referenced bean onto one of my service instances. I can comment out the bean and everything compiles. I can change it to one of my DAO beans and it works, I change it to another of my service beans and it causes the StackOverflowError again.

I have moved some of the ColdSpring.xml out to includes to reduce the file size and that has had no effect. I updated to 1.2 and had no change either. I’ve seen some minor changes in the rest of the error stack when I change up the service I’m including, but it’s more often than not this as the next couple lines:

at coldfusion.runtime.LocalScope.bindInternal(LocalScope.java:373)
at coldfusion.runtime.LocalScope.bindInternal(LocalScope.java:387)
at cfAbstractBeanFactory2ecfc1246833417$funcRESOLVEBEANNAME.runFunction(coldspringbeansAbstractBeanFactory.cfc:193)
at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:418)
at coldfusion.filter.SilentFilter.invoke(SilentFilter.java:47)
at coldfusion.runtime.UDFMethod$ReturnTypeFilter.invoke(UDFMethod.java:360)
at coldfusion.runtime.UDFMethod$ArgumentCollectionFilter.invoke(UDFMethod.java:324)
at coldfusion.filter.FunctionAccessFilter.invoke(FunctionAccessFilter.java:59)
at coldfusion.runtime.UDFMethod.runFilterChain(UDFMethod.java:277)
at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:192)
at coldfusion.runtime.CfJspPage._invokeUDF(CfJspPage.java:2471)

followed by a repeating of the above with several other calls to the cfAbstractBeanFactory instance. I know I’m not providing much, but I’m absolutely stumped as to what can be causing the problem. The bean I am adding that causes the error is also used as a ref bean on another bean without causing the problem. Any ideas that I could poke around at would be much appreciated!