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
