Comments on: Event Driven Architecture in Pico

By: Tieying Liu

Tieying Liu — Sat, 13 Sep 2003 06:57:00 +0000

I have just made this great thingy mutiple interfaces friendly. Now this loosk to be a very promising candidate for Object composition and AOP.

By: Chris Stevenson

Chris Stevenson — Fri, 12 Sep 2003 02:57:00 +0000

You’re right of course - I have corrected it here: http://cgi.skizz.plus.com/blog/dev/archives/000151.html#000151

By: Mike Porter

Mike Porter — Thu, 11 Sep 2003 21:43:00 +0000

This is cool…
But I am having one problem making a mental connection with your example.
How does the public Boy(Kissable kissable) {…} constructor ever get called?
I am using PicoContainer Beta1 and I usually use the registerComponent(classInterface, classImpl) methods… I understand how pico does its magic to call the correct constructor using the ‘greedy’ algorith for constructors. However in your example, you are doing a new Boy() thus bypassing the container.getComponent(classInterface) call… where I think pico must do its constructor magic.
How is your constructor getting called?