Re: users Digest 21 Nov 2010 10:48:43 -0000 Issue 4334

[Wilson Ikeda <wi...@gmail.com>]

"A lot of them would rather die than using Tapestry."

Maybe, but to be honest before adopting tapestry as my framework of choice i google "java frameworks" and the top result was..."wicket" so i tried it first but it was cumbersome, i was looking for a more easy and fast development framework than struts and didn't find any advantages in switching to wicket... until i find tapestry of course, so the point is newbies like me will try wicket first because of google, but how much of them will try other frameworks? If they got a tip "Hey, there's a tapestry IOC for wicket" maybe they will try to find out what tapestry is, on the other side if the Tapestry IOC for Wicket doesn't work correctly or if it's buggy or incompatibiliteis arise it can be a bad propaganda for tapestry...i'm not saying that it doesn't work, i'm saying that they can change things and maybe break the IOC (a very unprofessional, unethical thing to do) but some trolls come and go here and this is unprofessional too so they can do it and probably will do it.

On Nov 21, 2010, at 7:48 PM, users-digest-help@tapestry.apache.org wrote:

> From: Igor Drobiazko <ig...@gmail.com>
> Date: November 21, 2010 6:32:53 AM GMT+09:00
> To: Tapestry users <us...@tapestry.apache.org>
> Subject: Re: [ANN] Tapestry IOC for Wicket
> 
> 
> 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...@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-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>> 
>> 
> 
> 
> -- 
> Best regards,
> 
> Igor Drobiazko
> http://tapestry5.de