I think Thiago hit most of your points already. I would like to reiterate that the strength of Tapestry is in the server side implementation and that has everything to do with multi-page vs. single-page framework. Also tapestry IOC is supporting and not a primary component of tapestry. The web framework is the primary.
Having worked with tapestry for almost 2 years now I can honestly say that the biggest hump in learning it was actually tapestry IOC and the fact that doing everything requires knowing which service to inject. I would still prefer a universal API so the IDE can suggest what I have to call instead of trying to figure that what to inject/decorate/advise etc. with an IOC framework that I have not used before. On Aug 12, 2012, at 8:00 AM, Muhammad Gelbana <m.gelb...@gmail.com> wrote: > *@ lukaszkaleta * > Even so I haven't done a thorough investigation and ready but I think bad > performance on Vaadin would be due to the improper wiring of components > with each other. On that other question on stackoverflow, the guy was using > a grid component (as far as I can remember) while he had to use a table > instead which reflected improved performance. This may be the case > sometimes. > > *@ Lenny Primak,* > Probably the subject gave the wrong impression but I wasn't essentially > making a comparison (i.e. vs) between tapestry and Vaadin. ASFAIK Vaadin > doesn't even have any serious server side implementation, it only presents > or collects data from the client and wires it to your services but still, I > could be wrong about that since haven't read deeply about vaadin but > couldn't find any reference to a solid server side framework to build on > (like tapestry) > > I'm mainly raising this discussion because I believe tapestry could make > use of the idea of using a mature UI framework (such as Vaadin or GWT) > instead of reinventing the wheel on that part and rather focus on what it's > REALLY great at, the server side services (IoC for example as Taha > mentioned) > > Or even may be we, tapestry users or some of us, could find this more > suitable to our projects like *lukaszkaleta* mentioned about his project > consisted on Vaadin and google guice as an IoC. (but in our case it would > be tapestry ioc of course) > > On Sun, Aug 12, 2012 at 4:31 AM, Taha Siddiqi <tawus.tapes...@gmail.com>wrote: > >> The best way to learn how to do testing with tapestry is by looking at its >> tests :) >> >> I usually work on the service layer first. For service integration testing >> I build and startup a registry in the setup() and then start testing the >> services. (Look at tapestry-hibernate tests) >> >> For components and pages, I prefer not to have logic in there but if there >> is some logic related to rendering I unit test it. (Look at tapestry-core >> component tests under org.apache.tapestry.corelib.components/base) >> >> and finally and most importantly I use web integration testing using >> Geb(earlier Selenium). >> >> >> >> On Aug 12, 2012, at 7:13 AM, Ray Nicholus wrote: >> >>> Very little logic should exist in your component classes. That's what >>> services are for. You can use selenium to test your client side. Geb >> is a >>> nice tool to investigate. >>> On Aug 11, 2012 7:01 PM, "Angelo C." <angelochen...@gmail.com> wrote: >>> >>>> Hi Taha, >>>> >>>> I agree with almost all except the testability, maybe it's my fault not >>>> knowing how to structure the app to be testable, for now, I test only in >>>> the >>>> service/class level, very difficult to test the app/page level with >> those >>>> IOC things. >>>> >>>> angelo >>>> >>>> >>>> Taha Hafeez wrote >>>>> >>>>> Hi >>>>> >>>>> You are not going to get a fair comparison in a tapestry mailing list >> :). >>>>> Try it on stack-overflow. >>>>> >>>>> IMHO tapestry-jquery has a lot of components and you can easily create >> a >>>>> new one . Also tapestry is a lot more than set of components. The power >>>> of >>>>> class-reloading, class transformations, mixins, testability, inbuilt >> IOC >>>>> etc can't be ignored. >>>>> >>>>> regards >>>>> Taha >>>>> >>>>> On Aug 12, 2012, at 12:14 AM, lukaszkaleta wrote: >>>>> >>>>>> The question is what you need more: >>>>>> 1. RichClient like application on the web - then you can go with >> vaadin, >>>>>> since it has many build in components >>>>>> 2. If you look for good perfomnace in faver of rich components then >>>>>> tapestry >>>>>> is better choice IMHO >>>>>> >>>>>> I used vaadin for administrative application, the performance was not >> so >>>>>> important. >>>>>> Together with Google Guice as IoC it was nice combination. >>>>>> >>>>>> Tapestry has build in own IoC, but integrating Spring is very easy >> too. >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> >>>> >> http://tapestry.1045711.n5.nabble.com/Tapestry5-vs-Vaadin-tp5715273p5715274.html >>>>>> Sent from the Tapestry - User mailing list archive at Nabble.com. >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: users-unsubscribe@.apache >>>>>> For additional commands, e-mail: users-help@.apache >>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscribe@.apache >>>>> For additional commands, e-mail: users-help@.apache >>>>> >>>> >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> >> http://tapestry.1045711.n5.nabble.com/Tapestry5-vs-Vaadin-tp5715273p5715282.html >>>> Sent from the Tapestry - User mailing list archive at Nabble.com. >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>>> For additional commands, e-mail: users-h...@tapestry.apache.org >>>> >>>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > > -- > *Regards,* > *Muhammad Gelbana > Java Developer* --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
