Should I migrate away from ColdSpring

3 views
Skip to first unread message

hofar...@houseoffusion.com

unread,
Mar 19, 2015, 11:31:59 AM3/19/15
to ColdFusion Technical Talk

I've been using ColdSpring for a good number of years and it is pretty much
a part of almost every site that I have developed. When trying to access
http://coldspringframework.org/ to look at the docs, I get a service
unavailable error. It was like this when I tried to access it about a month
ago as well. Is the site defunct?

I know that the project has not been worked on for some time, so my
question is, should I consider migrating my sites to another dependency
injection solution? If so, which would you suggest? I've briefly looked at
Wirebox and DI/1, but have never put either one into play. Also, what kind
of work am I looking at to convert my existing sites? The thought of doing
this gives me heartburn, but I don't want to have to scramble if some
future CF or Java update breaks ColdSpring.

I appreciate any input.

Dean


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:360269

hofar...@houseoffusion.com

unread,
Mar 19, 2015, 8:46:09 PM3/19/15
to ColdFusion Technical Talk

I like ColdSpring. I like having "XML documentation" for that layer of my
codebase. As such, I have several sites that I don't plan to migrate to
DI/1 or WireBox. I also do a lot of Java consulting work, and switching
from Spring (Java) to ColdSpring (CFML) is less painful for my brain. :)
That being said, lots of people like DI/1 and Wirebox, but all you'd "gain"
by moving to them is being able to say "yes we're now using DI/1 instead of
ColdSpring".

I don't see why ColdSpring would be more likely to break from a future CF
update than any other library. One should always test code when changing
flavors of CF, that's not specific to ColdSpring.

Personally, I'd leave the site alone at least for now. Future projects, I
consider DI/1 or Wirebox, depending on the stack and requirements. I'm
also semi-secretly hoping someone maintains ColdSpring moving forward, but
I'm probably in the minority on that.

2 cents. Hope that helped.

-Nolan

PS. Shameless plug! I'm giving a talk at dev.Objective() titled "Dependency
Injection: Why Is It Awesome and Why Should I Care?" Ya'll should come
watch! :)
Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:360270

hofar...@houseoffusion.com

unread,
Mar 20, 2015, 12:37:24 PM3/20/15
to ColdFusion Technical Talk

Thanks, Nolan, I appreciate your insights. I'm pretty much on the same page
as you, but I guess I am mainly concerned that with the ColdSpring site
apparently gone, that I can't even get to the documentation to try to
either troubleshoot an issue or even expand on features that I haven't
worked with before, not necessarily that ColdSpring is more or less likely
to fail than other libraries.

I will probably end up doing what you suggested, leave existing sites
alone, but maybe try one of the newer and maintained libraries for future
projects.

Thanks again,

Dean

On Thu, Mar 19, 2015 at 8:45 PM Nolan Erck <nolan...@gmail.com> wrote:

>
> I like ColdSpring. I like having "XML documentation" for that layer of my
> codebase. As such, I have several sites that I don't plan to migrate to
> DI/1 or WireBox. I also do a lot of Java consulting work, and switching
> from Spring (Java) to ColdSpring (CFML) is less painful for my brain. :)
> That being said, lots of people like DI/1 and Wirebox, but all you'd "gain"
> by moving to them is being able to say "yes we're now using DI/1 instead of
> ColdSpring".
>
> I don't see why ColdSpring would be more likely to break from a future CF
> update than any other library. One should always test code when changing
> flavors of CF, that's not specific to ColdSpring.
>
> Personally, I'd leave the site alone at least for now. Future projects, I
> consider DI/1 or Wirebox, depending on the stack and requirements. I'm
> also semi-secretly hoping someone maintains ColdSpring moving forward, but
> I'm probably in the minority on that.
>
> 2 cents. Hope that helped.
>
> -Nolan
>
> PS. Shameless plug! I'm giving a talk at dev.Objective() titled "Dependency
> Injection: Why Is It Awesome and Why Should I Care?" Ya'll should come
> watch! :)
>
>
>
>
>
>
>
>
>
>
> On Thu, Mar 19, 2015 at 8:31 AM, Dean Lawrence <dea...@gmail.com> wrote:
>
> >
Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:360274

hofar...@houseoffusion.com

unread,
Mar 20, 2015, 8:10:51 PM3/20/15
to ColdFusion Technical Talk

FYI, on the ColdSpring Google group there is now a small discussion about
the ColdSpring docs and making sure they have a good home on a server
somewhere.

-Nolan
Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:360278

hofar...@houseoffusion.com

unread,
Mar 20, 2015, 8:23:24 PM3/20/15
to ColdFusion Technical Talk

Great! Thanks for the heads up, Nolan.

On Fri, Mar 20, 2015 at 8:10 PM Nolan Erck <nolan...@gmail.com> wrote:

>
> FYI, on the ColdSpring Google group there is now a small discussion about
> the ColdSpring docs and making sure they have a good home on a server
> somewhere.
>
> -Nolan
>
>
Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:360279

hofar...@houseoffusion.com

unread,
Mar 21, 2015, 6:08:19 AM3/21/15
to ColdFusion Technical Talk

I am happy to offer free hosting to get the site back up.
<javascript:;>>
Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:360280
Reply all
Reply to author
Forward
0 new messages