On Sat, 20 Nov 2010 17:36:50 -0200, Christian Riedel
<cr.ml...@googlemail.com> wrote:
Hi everyone,
Hi!
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 :-))!
Tapestry-IoC is not Tapestry-the-web-framework, the former is used by the
letter and Tapestry-IoC is awesome, so I think it's a good idea. :)
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.
I can't see whey tapestry-hibernate wouldn't work without Tapestry. It
provides Session as per-thread a service, so I guess it should work
out-of-the-box.
What do you think about it?
Go ahead! :)
Could it help Tapestry to find adoption in the Wicket-world?
I don't think so. Both frameworks have similarities (components and pages
treated as objects), but very different approaches.
Or am I getting excommunicated by the community for that blasphemous
chimera? (I could call it *Wickestry* but I don't dare to)
Absolutely not. ;)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org