Comments on: IoC and the Dependency Injection Pattern in Flex

By: Fernando Ghisi

Fernando Ghisi — Sun, 25 Oct 2009 23:33:17 +0000

Excellent post! Simple and informative.

Thanks.

By: diamondTearz

diamondTearz — Thu, 21 May 2009 20:03:27 +0000

Thanks for taking the time to put this explanation of Dependency Injection together. It helped clarify a lot of the details.

By: iteratif

iteratif — Mon, 16 Mar 2009 23:01:51 +0000

A french solution : http://code.google.com/p/indigoframework
it’s the first implementation of IOC in AS3, look here : http://iteratif.free.fr/blog/index.php?2007/01/24/64-le-framework-architectural-indigo

Iteratif
++

By: Greg Baker

Greg Baker — Sat, 24 Jan 2009 16:33:00 +0000

Another very good Flex framework is Mate.
It too is MXML based.

http://mate.asfusion.com/

Greg

By: Mike

Mike — Thu, 22 Jan 2009 08:58:35 +0000

For those interested in Flex and IOC, Flicc - http://flicc.sourceforge.net/ - is also worth a look. Since it’s configuration is based on MXML rather than XML, you get some extra comile time checking as well as a more concise markup.

By: Hem Talreja

Hem Talreja — Sat, 22 Nov 2008 04:58:06 +0000

Hi Martin,

I have implemented a sample application using Swiz.

http://www.hemtalreja.com/?p=258

Enjoy!!!
-Hem

By: Ahmad

Ahmad — Sun, 28 Sep 2008 12:14:51 +0000

Thanks Eric. Actually I didn’t know much about the injection pattern before, but I did lots of reading after I saw this post. And now I do understand the need for more interface to apply the interface injection.

By: Martin

Martin — Wed, 24 Sep 2008 19:41:25 +0000

Hey Eric,

This is a really nice post about IoC and prana. Thank you!

I was wondering if you have taken a look at the swiz framework, which also implements IoC however via annotations versus xml. If you have, would you mind sharing your thoughts about swiz and how it compares to prana? I do not have much experience with either of the frameworks, especially swiz, so any thoughts would be appreciated!

Thanks and keep it up, man!

By: eric

eric — Tue, 23 Sep 2008 13:01:00 +0000

Hey Ahmed,

Good point, the reason why Interface injection is not the most desirable mechanism of DI is that in a large project you may need to potentially create many, many additional interfaces in which their only purpose is to facilitate DI. These additional interfaces add to the complexity of the codebase and IMHO they are coupling your application code to the framerwork. A constructor or setter which accepts references to other objects is very common so this additional overhead is less intrusive than interface injection.

Best,
Eric

By: Ahmad

Ahmad — Tue, 23 Sep 2008 09:18:33 +0000

Hi Eric

thanks for a very nice and useful post.

One comment that i thought of, it doesn’t seem to me that a drawback of the Interface injection is the need to create more Interfaces, since we still need to create those for Setter and Constructor Injection.

By: Shashank Tiwari

Shashank Tiwari — Mon, 22 Sep 2008 20:37:43 +0000

Good post! Covered this post in a featured post on riarevolution. Here is the link : http://riarevolution.com/2008/09/22/ioc-and-dependency-injection-in-flex/

By: Ivan

Ivan — Mon, 22 Sep 2008 16:40:28 +0000

Hi Erick, thanks for the great post…
A while ago I did something similar to your proposal, trying to “inject” a class that was implementing an interface inside a library into another class using a setter.
I had the injection done by another class that loaded a XML file on the fly, specifying the default class to inject (sort of what spring does) and with the use of reflection I was able to load the class dynamically and use all the services exposed by the interface from that implementation…
Since I was using RSL and dynamic linkage I was able to upload my library with a new class implementation, update my XML with that new implementation set as the default and execute the application without having to compile anything else other than my Library…
Seems like Prana takes care of that extra class I created, definitely will pay attention to it…