On the one hand, I found it clever. I was trying to avoid bytecode
transformation inside IOC and Rod's solution doesn't address spreading @Bean
definitions across multiple "modules" (classes).  That could be done as
well, but gets much trickier.  T5IOC is somewhat more verbose, but a lot
more powerful and descriptive.

On 12/7/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:

Yeah, you know what they say... "imitation is one of the best forms of
flattery". This was inevitable.

Many have tried to do the same with Tapestry as well. (they tried and
failed ?  no - they tried and died .. - wise bene gesserit )

On 12/7/06, Massimo Lusetti <[EMAIL PROTECTED] > wrote:
>
http://blog.interface21.com/main/2006/11/28/a-java-configuration-option-for-spring/
>
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

Reply via email to