Say my constructors were named after the components could I still use ColdSpring?
You received this message because you are subscribed to the Google Groups "ColdSpring-Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coldspring-use...@googlegroups.com.
To post to this group, send email to coldspri...@googlegroups.com.
Visit this group at http://groups.google.com/group/coldspring-users.
For more options, visit https://groups.google.com/groups/opt_out.
It would be more straightforward to add an init() method to the components that in turn called the custom unit methods.
That would be preferred to changing the ColdSpring framework.
Thanks for your thoughts/responses. I actually do not have any code yet. All the apps I am now supporting follow the CF bean convention and do work great with ColdSpring. However, I have been working with beans for about 9 months now but I still do not fully understand them. I am at least unable to clearly explain it to any one. The best I can do is to describe how to use them. This bothered me so I did some research and I came across WEB4J. This framework is not an IoC but an MVC one and it was build around using immutable objects instead of beans as much as possible. Now my line of thinking did not take me that far however I do agree with their rationale and I immediately understand immutable objects more than I now understand beans. This is what prompted my question. Brian, yes I am looking to fully instantiate at construction.
BTW, I use ColdSpring 2