This is the most exciting news I've heard in a long time. Introducing T5 IOC as a standard IOC choice for bigger frameworks could be a very important move for Tapestry. We should find out if more can be done in this field, for Spring MVC, JSF and other frameworks that are bigger than T5.
The bad news is: From what I've seen and heard, people that really care about writing nice and clean framework-indepenent IOC-code in their web project are a minority. People simply don't care about separating their business logic from the framework. I asked the creators of the Play framework about IOC-integration at a conference recently, and only got a vague answer about Spring integration. The IOC-integration for Wicket (Spring, Guice) also seems immature. A bit of guessing here, but this is my impression. I'm looking for a new job here in Norway, and the only web framework mentioned apart from Spring MVC is Wicket. So creating a usable and stable integration of T5 IOC would be absolutely brilliant. For me personally, it would make it way easier to bring Tapestry along to my new job as a pure IOC engine. That's a very good start! I'm not a Wicket man, don't know it too much. But I will probably need to learn it sooner or later for clients, so I would like to participate in stabilizing this thing by creating a Wicket project and trying it out! Inge On Sat, Nov 20, 2010 at 11:05 PM, Christian Riedel <cr.ml...@googlemail.com>wrote: > But Howard said, we have to evangelize people - why not by infiltration ;-) > > > Am 20.11.2010 um 22:32 schrieb Igor Drobiazko: > > > We should ban you from the mailing list for it. > > > > No, no just joking. To be honest I don't believe this will help to > improve > > the adoption. I experienced the Wicket users as very religious about > their > > framework and very aggressive towards Tapestry. A lot of them would > rather > > die than using Tapestry. > > > > Cheers > > > > On Sat, Nov 20, 2010 at 8:36 PM, Christian Riedel > > <cr.ml...@googlemail.com>wrote: > > > >> Hi everyone, > >> > >> I started a little project today: I made a module for Wicket so that it > >> uses Tapestry IOC for injection (I'm not joking, seriously :-))! > >> Yesterday I had the idea to do that after I was annoyed again while > using > >> Wicket for one of my projects... I was looking for a way to have fun > with > >> Wicket and since I was struggling with its Spring integration I came up > with > >> that project. It was so absurd to have them both work together, I > thought , > >> instead of competing each other. So I had to give it a try - no way out > :-) > >> > >> Maybe someone would really use it if it's mature enough and migrate a > >> Wicket application over to Tapestry! That'll be awesome! :-) > >> > >> The code is quite simple, it's using reflection to do the injection (I > was > >> inspired by the guice integration). I'm looking for a way to do it > similar > >> to the ClassTransformationWorker. I only implemented @Inject and > >> @InjectService - no hibernate until now. My motivation is to find a > useful > >> frame of features that could be provided (apart from finding a proper > place > >> for the shutdown hook...). I really want to get rid of Spring and > migrate > >> that one application mentioned above to Tapestry one day. That's one > goal at > >> least. > >> > >> What do you think about it? Could it help Tapestry to find adoption in > the > >> Wicket-world? > >> > >> Or am I getting excommunicated by the community for that blasphemous > >> chimera? (I could call it *Wickestry* but I don't dare to) > >> > >> Cheers, > >> Christian > >> > >> > >> [link] https://github.com/criedel/WicketTap5IOC > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > >> For additional commands, e-mail: users-h...@tapestry.apache.org > >> > >> > > > > > > -- > > Best regards, > > > > Igor Drobiazko > > http://tapestry5.de > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >