You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Christian Riedel <cr...@googlemail.com> on 2010/11/20 20:36:50 UTC
[ANN] Tapestry IOC for Wicket
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
Re: [ANN] Tapestry IOC for Wicket
Posted by Taha Hafeez <ta...@gmail.com>.
On Tue, Nov 23, 2010 at 5:16 PM, Christian Riedel
<cr...@googlemail.com>wrote:
> It's just a pitty that you can't override so much so easily in Wicket :)
>
Yes, I agree but then it is not a problem of Wicket it is more of an
advantage of IOC over inheritance.
regards
Taha
>
> Am 23.11.2010 um 12:39 schrieb Thiago H. de Paula Figueiredo:
>
> > On Tue, 23 Nov 2010 02:45:49 -0200, Taha Hafeez <
> tawus.tapestry@gmail.com> wrote:
> >
> >> Hi,
> >
> > Hi!
> >
> >> Correct me if i am wrong but wicket and tapestry are based on different
> >> philosophies. Tapestry IOC is the recognition by tapestry that there are
> >> certain services that are presentation services and require an exclusive
> >> support in the presentation layer.
> >
> > I don't know what you mean by presentation service and exclusive support.
> All Tapestry-the-web-framework services are ordinary Tapestry-IoC services,
> not being treated differently than any other.
> >
> > You don't think of using IoC inside a Web framework until you see it and
> then you realize how good the idea is. Just take a look at how easy is to
> override almost anything in Tapestry. ;)
> >
> > --
> > 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-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: [ANN] Tapestry IOC for Wicket
Posted by Christian Riedel <cr...@googlemail.com>.
It's just a pitty that you can't override so much so easily in Wicket :)
Am 23.11.2010 um 12:39 schrieb Thiago H. de Paula Figueiredo:
> On Tue, 23 Nov 2010 02:45:49 -0200, Taha Hafeez <ta...@gmail.com> wrote:
>
>> Hi,
>
> Hi!
>
>> Correct me if i am wrong but wicket and tapestry are based on different
>> philosophies. Tapestry IOC is the recognition by tapestry that there are
>> certain services that are presentation services and require an exclusive
>> support in the presentation layer.
>
> I don't know what you mean by presentation service and exclusive support. All Tapestry-the-web-framework services are ordinary Tapestry-IoC services, not being treated differently than any other.
>
> You don't think of using IoC inside a Web framework until you see it and then you realize how good the idea is. Just take a look at how easy is to override almost anything in Tapestry. ;)
>
> --
> 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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
Posted by Taha Hafeez <ta...@gmail.com>.
On Tue, Nov 23, 2010 at 5:09 PM, Thiago H. de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Tue, 23 Nov 2010 02:45:49 -0200, Taha Hafeez <ta...@gmail.com>
> wrote:
>
> Hi,
>>
>
> Hi!
>
> Correct me if i am wrong but wicket and tapestry are based on different
>> philosophies. Tapestry IOC is the recognition by tapestry that there are
>> certain services that are presentation services and require an exclusive
>> support in the presentation layer.
>>
>
> I don't know what you mean by presentation service and exclusive support.
> All Tapestry-the-web-framework services are ordinary Tapestry-IoC services,
> not being treated differently than any other.
>
>
Excuse my English but I used this term to separate services pertaining to
presentation layer (That is what you also say in the next line)... A number
of frameworks don't see the need of these services as they implement these
in other ways. 'Exclusive' as tapestry has its own IOC.
> You don't think of using IoC inside a Web framework until you see it and
> then you realize how good the idea is. Just take a look at how easy is to
> override almost anything in Tapestry. ;)
>
>
>
I absolutely agree but as I said Wicket has a different philosophy which
also means there are people who don't agree with it. I do and that is why I
am opting for it but there are people who prefer other ways :)
> --
> 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
>
regards
Taha
Re: [ANN] Tapestry IOC for Wicket
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Tue, 23 Nov 2010 02:45:49 -0200, Taha Hafeez <ta...@gmail.com>
wrote:
> Hi,
Hi!
> Correct me if i am wrong but wicket and tapestry are based on different
> philosophies. Tapestry IOC is the recognition by tapestry that there are
> certain services that are presentation services and require an exclusive
> support in the presentation layer.
I don't know what you mean by presentation service and exclusive support.
All Tapestry-the-web-framework services are ordinary Tapestry-IoC
services, not being treated differently than any other.
You don't think of using IoC inside a Web framework until you see it and
then you realize how good the idea is. Just take a look at how easy is to
override almost anything in Tapestry. ;)
--
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
Posted by Taha Hafeez <ta...@gmail.com>.
Hi,
Correct me if i am wrong but wicket and tapestry are based on different
philosophies. Tapestry IOC is the recognition by tapestry that there are
certain services that are presentation services and require an exclusive
support in the presentation layer. That does not mean that tapestry IOC
cannot be used in other layers but the mere inclusion of an IOC into
tapestry web-framework broadly speaks of the recognition. Also tapestry's
internal design is based on IOC (it avoids inheritance as much as possible.)
and that is what tapestry promotes.
Wicket, on the other hand, is more close to swing. It is more about
inheritance than ioc. Rather there is no use of IOC in the internals. It is
pure and pure inheritance. These is no concept of presentation services,
everything is inheritance. The difference between these two frameworks is
clearer when one looks into the implementation of jasper report support
implementation for the two frameworks.
When one embraces a framework, the philosophy comes with it and as a wicket
user I don't see any need for Tapestry IOC in my presentation layer and even
if there is I have spring & guice. Alternatively as a tapestry user I find
little need for inheritance when I have the pleasure of injecting services,
environmental etc.
Now I am more of a tapestry user but still when i think as a wicket user i
find these services as not part of its philosophy..
I hope I have brought some of the wicket user's point of view into picture.
regards
Taha
On Mon, Nov 22, 2010 at 8:56 PM, Christian Riedel
<cr...@googlemail.com>wrote:
>
> >
> >> 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.
>
> The web-frameworks have different approaches, yes, but Wicket has no own
> IOC module. What I see is that a Wicket user has the choice between Spring
> and Guice for DI.
>
> People do mostly evaluate both, Tapestry and Wicket, don't they? So in the
> future they could see a third DI provider, which is fortunately part of one
> of the frameworks they are just evaluating...
> I find that being a psychological advantage to have a Tapestry (IOC)
> integration for Wicket (and possibly other frameworks, too). You could read
> it as "Tapestry is so advanced you can use it everywhere" or "Development
> with Tapestry means to have no need for more web frameworks...". I mean we
> have to advertise it a little more :-) It's such a huge advantage to have
> that perfectly fitting IOC framework shipped with the web-framework.
>
> The basic integration was actually very very simple. Much simpler than
> Spring's or Guice's. It's just missing @CommitAfter support for hibernate
> and better approach of injecting the values into fields - not by reflection.
> On the other hand, Spring and Guice are doing the same, so this could become
> a unique feature if I find some byte-code-manipulating solution!
>
> And I also think an integration for play! or other frameworks could be
> pretty much the same effort. Tapestry is so easy to use :-)
>
> Well, I'll continue with that experiment!
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: [ANN] Tapestry IOC for Wicket
Posted by Christian Riedel <cr...@googlemail.com>.
>
>> 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.
The web-frameworks have different approaches, yes, but Wicket has no own IOC module. What I see is that a Wicket user has the choice between Spring and Guice for DI.
People do mostly evaluate both, Tapestry and Wicket, don't they? So in the future they could see a third DI provider, which is fortunately part of one of the frameworks they are just evaluating...
I find that being a psychological advantage to have a Tapestry (IOC) integration for Wicket (and possibly other frameworks, too). You could read it as "Tapestry is so advanced you can use it everywhere" or "Development with Tapestry means to have no need for more web frameworks...". I mean we have to advertise it a little more :-) It's such a huge advantage to have that perfectly fitting IOC framework shipped with the web-framework.
The basic integration was actually very very simple. Much simpler than Spring's or Guice's. It's just missing @CommitAfter support for hibernate and better approach of injecting the values into fields - not by reflection. On the other hand, Spring and Guice are doing the same, so this could become a unique feature if I find some byte-code-manipulating solution!
And I also think an integration for play! or other frameworks could be pretty much the same effort. Tapestry is so easy to use :-)
Well, I'll continue with that experiment!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Sat, 20 Nov 2010 17:36:50 -0200, Christian Riedel
<cr...@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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
Posted by Christian Riedel <cr...@googlemail.com>.
just uploaded a readme with instructions so you can test it :-)
Am 21.11.2010 um 11:48 schrieb Inge Solvoll:
> 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...@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...@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
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
Posted by Igor Drobiazko <ig...@gmail.com>.
This is on my list for 5.3. I already started working on it but will commit
it after 5.2 is final.
I don't intend to pass the official TCK as there are too many differences.
Just using JSR-330 annotations in Tapestry pages, components and service is
fine.
On Sun, Nov 21, 2010 at 9:48 PM, Werner Keil <we...@gmail.com> wrote:
> For this bigger move, T5 IOC should really adopt to JSR 330 annotations
> where those are included, or has it already happened for sure with 5.2?
>
--
Best regards,
Igor Drobiazko
http://tapestry5.de
Re: [ANN] Tapestry IOC for Wicket
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Sun, 21 Nov 2010 18:48:16 -0200, Werner Keil <we...@gmail.com>
wrote:
> For this bigger move, T5 IOC should really adopt to JSR 330 annotations
> where those are included,
I think there's a JIRA for that.
> or has it already happened for sure with 5.2?
Not yet.
--
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
Posted by Werner Keil <we...@gmail.com>.
For this bigger move, T5 IOC should really adopt to JSR 330 annotations
where those are included, or has it already happened for sure with 5.2?
Re: [ANN] Tapestry IOC for Wicket
Posted by Inge Solvoll <in...@gmail.com>.
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...@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...@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
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: [ANN] Tapestry IOC for Wicket
Posted by Christian Riedel <cr...@googlemail.com>.
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...@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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [ANN] Tapestry IOC for Wicket
Posted by Igor Drobiazko <ig...@gmail.com>.
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