You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Muhammad Gelbana <m....@gmail.com> on 2012/08/11 20:30:31 UTC

Tapestry5 vs Vaadin

So is there any Vaadin users already using tapestry5 too and could give me
a comparison based on his experience ?

I've never used Vaadin but what I can say about it after I visited it's
website is that it's much more UI component rich when compared to tapestry
but it has no IoC support. Of course the lack of UI components in t5 can be
mitigated by using external libraries\frameworks but I'm comparing based on
the OTB features that requires no efforts to import.

I see it as:

Vaadin + IoC = Tapestry5 + GWT (But still Vaadin will have more UI
components OTB)

What do you think ?

-- 
*Regards,*
*Muhammad Gelbana
Java Developer*

Re: Tapestry5 vs Vaadin

Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Mon, 13 Aug 2012 10:54:26 -0300, Muhammad Gelbana <m....@gmail.com>  
wrote:

> I probably am. But I think tapestry's *major* contribution is into the
> client part. I highly expect that this is wrong so please correct me if I
> am. What difference does it make if tapestry is a multi-page framework  
> or a single-page one ?

Being multipage or single page makes a huge difference in which projects  
it's better suited. IMHO, single page approaches are best suited to  
webapps that want to have a desktop-like look and feel and behavior. One  
example would be webmail. For other kinds of webapps, I think multipage  
approaches work best. And you can still do single page webapps in  
multipage frameworks.

> I totally agree. But I also hope I dive deep enough into tapestry to be
> able to do such things easily without showstoppers appearing at any  
> point.

Which showstoppers have you met so far?

> I am developing a web application, ALL ALONE (small company), along with
> windows services (Tapestry IoC and Apache Daemon) and some 3rd line  
> support from time to time and it's really hard to have time to go  
> through tapestry code or the docs

You'll need to go through the documentation of anything you use anyway . .  
.

> Tapestry helps a lot but sometimes I just get stuck with trivial (mostly  
> client-side related, components and tml) things that wouldn't take few  
> minutes withing servlets\js.

That's what I call learning something. Care to provide actual examples?  
Otherwise, you fall in the "I can do X in Y way faster than in Z just  
because I already know Y well and I have learned Z yet".

> Obviously I've used the wrong words again, I mean the integration part,
> like configuration files or whatever. Of course including a jar into my
> classpath shouldn't be a problem.

So your argument about components provided by Tapestry out-of-the-box  
don't apply here. ;)

-- 
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Tapestry5 vs Vaadin

Posted by Muhammad Gelbana <m....@gmail.com>.
>
> Wow, you've just said that Tapestry, which is a web framework, should drop
> the web framework (which is multipage), replace it with Vaadin/GWT (which
> are single page) and focus on the IoC part only. I'm sorry, but I think
> you're at least very confused about the above opinion


I probably am. But I think tapestry's *major* contribution is into the
client part. I highly expect that this is wrong so please correct me if I
am. What difference does it make if tapestry is a multi-page framework or a
single-page one ?

In Tapestry, writing a component is a very trivial thing to do. In
> addition, you're using HTML directly, which isn't the case of Vaadin/GWT,
> so you can very easily and quickly get some JavaScript
> component/widget/whatever from jQuery UI, Scriptaculous or other projects
> and turn it into a component when that's not provided by some project like
> Tapestry-jQuery or ChennileKit.


I totally agree. But I also hope I dive deep enough into tapestry to be
able to do such things easily without showstoppers appearing at any point.
I am developing a web application, ALL ALONE (small company), along with
windows services (Tapestry IoC and Apache Daemon) and some 3rd line support
from time to time and it's really hard to have time to go through tapestry
code or the docs so I'm mostly just trying to get things done. Tapestry
helps a lot but sometimes I just get stuck with trivial (mostly client-side
related, components and tml) things that wouldn't take few minutes withing
servlets\js.

How much effort is needed to get some third-party package like
> tapestry-jquery to work in Tapestry? Just add it to the classpath. If use
> use some dependency management tool like Maven, Ivy or Gradle, just add the
> dependency to the configuration and the tool will do it for you. If not,
> download the JAR and configure your project to include it in your
> classpath. It couldn't be easier or faster.


Obviously I've used the wrong words again, I mean the integration part,
like configuration files or whatever. Of course including a jar into my
classpath shouldn't be a problem.

On Mon, Aug 13, 2012 at 2:43 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:

> On Sat, 11 Aug 2012 15:30:31 -0300, Muhammad Gelbana <m....@gmail.com>
> wrote:
>
>  I've never used Vaadin but what I can say about it after I visited it's
>> website is that it's much more UI component rich when compared to
>> tapestry but it has no IoC support. Of course the lack of UI components in
>> t5 can be mitigated by using external libraries\frameworks but I'm
>> comparing based on the OTB features
>>
>
> From Tapestry side:
> * Using HTML, CSS and JavaScript directly.
> * Live class reloading
> * You can change almost anything in the framework without needing to touch
> its source: service override, advice, decoration.
> * It's very easy and quick and painless to write new components. In GWT
> and Vaadin, creating your own component which uses JavaScript is actually
> discouraged: see the bottom of https://developers.google.com/**
> web-toolkit/doc/latest/**DevGuideUiCustomWidgets<https://developers.google.com/web-toolkit/doc/latest/DevGuideUiCustomWidgets>.
> My argument here is that there's no framework that will provide you 100% of
> your component needs, so you'll eventually need to write your own and
> you'll hope you have chosen a framework that makes it easy.
> * Very high source code quality and test code coverage.
> * You can use client-side-focused frameworks like GWT on the top of
> Tapestry if you want or need. Someone has already done GWT on Tapestry.
> Google it.
>
> And don't forget that Vaadin is basically GWT plus some server-side stuff.
>
>
>  that requires no efforts to import.
>>
>
> How much effort is needed to get some third-party package like
> tapestry-jquery to work in Tapestry? Just add it to the classpath. If use
> use some dependency management tool like Maven, Ivy or Gradle, just add the
> dependency to the configuration and the tool will do it for you. If not,
> download the JAR and configure your project to include it in your
> classpath. It couldn't be easier or faster.
>
>
> --
> Thiago H. de Paula Figueiredo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
*Regards,*
*Muhammad Gelbana
Java Developer*

Re: Tapestry5 vs Vaadin

Posted by Onno Scheffers <on...@piraya.nl>.
> That's why I said 'basically'. ;) I claim no knowledge in Vaadin besides
> reading its website.
>

I also said 'basically' :)

I'm currently working on my first Vaadin project, so I am in no way an
expert. I do really like it though and I plan to also use it for an
administrative section of an existing Tapestry application. That part of
the application only has a couple of users with modern browsers and they
required advanced controls. That is much easier and quicker to create using
Vaadin.



> Could you provide a short description of Vaadin's server-side stuff for
> people who are used to Tapestry? I'd love to read that. :)
>

That's just it. It isn't just the server-side stuff that is impressive in
Vaadin. You made it sound like everything on the client is provided by GWT
and Vaadin only adds some server-logic to it. This is not true.  They
created a lot of impressive stuff on both the client and the server.

Communication between client and server and most of the rich client stuff
is not provided out of the box by GWT, but was custom-built by the Vaadin
team using GWT. That way a developer doesn't have to worry about
client-server communication or GWT-specific stuff. You just create an
application, add components to it, add listeners to those components and
respond to events.

You can basically create an application as if you were creating a
single-user client application.

Each user-session gets its own application instance which is stored on the
session and keeps running while the session is alive. If the user interacts
with a component, the listener on the component is triggered on the server.
All your code actually runs on the server, which makes things both easy and
secure and the components are updated automatically on the client.
The Vaadin team has created the entire infrastructure to make all of this
possible, implemented an extensive (server-side) application API and
provided many rich client components for you to use (which requires both
server-side and client-side work).

Just take a look at their calculator example, which only uses a simple
label-component and a couple of buttons:
Code:
http://demo.vaadin.com/docs/example-source/com/vaadin/demo/Calc.java.html
Demo: http://demo.vaadin.com/Calc

No HTML templates, no Javascript. Just plain old Java. If you didn't know
about Vaadin, you probably wouldn't guess the code was running on a server.




> Tapestry == Javassist plus some server-side stuff? I'm not following you.
> Javassist is used server-side in Tapestry and its being completely replaced
> by Plastic (which is built on top of ASM).
>

Yeah, exactly. Tapestry is not just Javassist. A lot of stuff has been
added and most of it was server-side stuff. Just like Vaadin is not just
GWT with some server-stuff.
Even though the server-bits are pretty nice, an enormous amount of effort
has gone into the client part. The entire reason for using GWT is that so
much of the development effort would be on the client, but all of it is
custom work by the Vaadin team. Up until version 7, Vaadin didn't even come
with GWT, you had to install it yourself if you wanted to develop custom
components.

I know you guys are replacing Javassist with ASM, but that doesn't change
the point I was trying to make:
- Vaadin provides a lot of magic for you on both the client and the server
and for part of it they use GWT but the user hardly notices. They could
have used another framework instead, but they had good reasons to pick GWT.
- Tapestry also provides a lot of magic for you and uses Javassist for part
of that magic and the user hardly notices. Tapestry could have used
something else but Howard had a good reason to choose Javassist at that
time (he actually wrote a blog defending its choice).


- Onno

Re: Tapestry5 vs Vaadin

Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Mon, 13 Aug 2012 16:07:39 -0300, Onno Scheffers <on...@piraya.nl> wrote:

>> And don't forget that Vaadin is basically GWT plus some server-side  
>> stuff.
>
> That's like saying Tapestry is basically Javassist plus some server-side
> stuff.

That's why I said 'basically'. ;) I claim no knowledge in Vaadin besides  
reading its website. Could you provide a short description of Vaadin's  
server-side stuff for people who are used to Tapestry? I'd love to read  
that. :)

Tapestry == Javassist plus some server-side stuff? I'm not following you.  
Javassist is used server-side in Tapestry and its being completely  
replaced by Plastic (which is built on top of ASM).

-- 
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Tapestry5 vs Vaadin

Posted by Onno Scheffers <on...@piraya.nl>.
> And don't forget that Vaadin is basically GWT plus some server-side stuff.


That's like saying Tapestry is basically Javassist plus some server-side
stuff. Vaadin is a very mature framework that has been in development for
many years and they built most of their client implementation and rich
client components using GWT. As a developer using Vaadin, you only have to
deal with GWT if you write your own rich client components otherwise you
don't even know it's there.

Both frameworks have their place. If you want to create rich client
applications, Vaadin is a very good choice. Vaadin creates an application
instance per user session and all components are kept on the session as
they are being used. Actions on the client invoke an AJAX request, which
can be handled by your components on the server, simply by attaching
listeners to your components. This way you only have to focus on your
server-side Java code. Client elements are updated on the client or you can
replace panels in response to user-actions instead of refetching an entire
page (hence the single-page name). This approach makes it heavy on the
server, but easy to develop for, as long as the default set of components
is enough for you. Documentation is also very good and having a central
location for plugins/components is great.

There are many projects that still require multi-page applications though,
so you have bookmarkable pages that are easily indexed by search-engines
and can work without Javascript (which is a requirement for many government
projects over here). Typically you only need to instantiate Objects to
create the response and there is no need to store much information on the
session making it easier to scale up. Tapestry is a very good choice for
these types of projects and it helps that there is now a EAP available of a
good Tapestry book :)

- Onno

Re: Tapestry5 vs Vaadin

Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Sat, 11 Aug 2012 15:30:31 -0300, Muhammad Gelbana <m....@gmail.com>  
wrote:

> I've never used Vaadin but what I can say about it after I visited it's
> website is that it's much more UI component rich when compared to  
> tapestry but it has no IoC support. Of course the lack of UI components  
> in t5 can be mitigated by using external libraries\frameworks but I'm  
> comparing based on the OTB features

 From Tapestry side:
* Using HTML, CSS and JavaScript directly.
* Live class reloading
* You can change almost anything in the framework without needing to touch  
its source: service override, advice, decoration.
* It's very easy and quick and painless to write new components. In GWT  
and Vaadin, creating your own component which uses JavaScript is actually  
discouraged: see the bottom of  
https://developers.google.com/web-toolkit/doc/latest/DevGuideUiCustomWidgets.  
My argument here is that there's no framework that will provide you 100%  
of your component needs, so you'll eventually need to write your own and  
you'll hope you have chosen a framework that makes it easy.
* Very high source code quality and test code coverage.
* You can use client-side-focused frameworks like GWT on the top of  
Tapestry if you want or need. Someone has already done GWT on Tapestry.  
Google it.

And don't forget that Vaadin is basically GWT plus some server-side stuff.

> that requires no efforts to import.

How much effort is needed to get some third-party package like  
tapestry-jquery to work in Tapestry? Just add it to the classpath. If use  
use some dependency management tool like Maven, Ivy or Gradle, just add  
the dependency to the configuration and the tool will do it for you. If  
not, download the JAR and configure your project to include it in your  
classpath. It couldn't be easier or faster.

-- 
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Tapestry5 vs Vaadin

Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Sun, 12 Aug 2012 10:00:53 -0300, Muhammad Gelbana <m....@gmail.com>  
wrote:

> 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)

Wow, you've just said that Tapestry, which is a web framework, should drop  
the web framework (which is multipage), replace it with Vaadin/GWT (which  
are single page) and focus on the IoC part only. I'm sorry, but I think  
you're at least very confused about the above opinion.

In addition, as it was already mentioned in this thread, you're focusing  
too much on a single bullet point (number of ready to use client-side  
components) and forgetting about the big picture. Vaadin and GWT have to  
provide lots of built-in components because they're hard and  
time-consuming to write (at least when compared to Tapestry). In other  
words, your *not* supposed to write your own components in 95% of the  
situations (numbers made up by me, of course).

In Tapestry, writing a component is a very trivial thing to do. In  
addition, you're using HTML directly, which isn't the case of Vaadin/GWT,  
so you can very easily and quickly get some JavaScript  
component/widget/whatever from jQuery UI, Scriptaculous or other projects  
and turn it into a component when that's not provided by some project like  
Tapestry-jQuery or ChennileKit.

> 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)

Now you've said something I agree: there's no silver bullet. No solution  
will be the best for all problems (nor any framework for all kinds of  
webapps). There are projects in which Vaadin/GWT will be a better choice  
than Tapestry and vice-versa.

-- 
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Tapestry5 vs Vaadin

Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Mon, 13 Aug 2012 16:39:24 -0300, Lenny Primak <lp...@hope.nyc.ny.us>  
wrote:

> I will actually put that on my list of things to do. The only problem I  
> have with this approach is that this will always be in catch-up mode ala  
> mono and .net

With the difference that the Tapestry public API grows slow . . .

-- 
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Tapestry5 vs Vaadin

Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
I will actually put that on my list of things to do. The only problem I have with this approach is that this will always be in catch-up mode ala mono and .net


On Aug 13, 2012, at 2:25 PM, "Thiago H de Paula Figueiredo" <th...@gmail.com> wrote:

> On Mon, 13 Aug 2012 16:03:24 -0300, Lenny Primak <lp...@hope.nyc.ny.us> wrote:
> 
> For the service discovery part, why don't you create a service that provides getters for these services that are usually used and make it an open-source project? It would be nice to see something like that.
> 
> -- 
> Thiago H. de Paula Figueiredo
> 
> ---------------------------------------------------------------------
> 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: Tapestry5 vs Vaadin

Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Mon, 13 Aug 2012 16:03:24 -0300, Lenny Primak <lp...@hope.nyc.ny.us>  
wrote:

> Also tapestry IOC is supporting and not a primary component of tapestry.
> The web framework is the primary.

Yep, but Tapestry-IoC is amazing on its own too. :)

> 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.

For the service discovery part, why don't you create a service that  
provides getters for these services that are usually used and make it an  
open-source project? It would be nice to see something like that.

-- 
Thiago H. de Paula Figueiredo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Tapestry5 vs Vaadin

Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
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....@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 <ta...@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." <an...@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-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
>> 
>> 
> 
> 
> -- 
> *Regards,*
> *Muhammad Gelbana
> Java Developer*

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Tapestry5 vs Vaadin

Posted by Muhammad Gelbana <m....@gmail.com>.
*@ 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 <ta...@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." <an...@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-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
>
>


-- 
*Regards,*
*Muhammad Gelbana
Java Developer*

Re: Tapestry5 vs Vaadin

Posted by Taha Siddiqi <ta...@gmail.com>.
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." <an...@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-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: Tapestry5 vs Vaadin

Posted by Ray Nicholus <rn...@widen.com>.
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." <an...@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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>

Re: Tapestry5 vs Vaadin

Posted by "Angelo C." <an...@gmail.com>.
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Tapestry5 vs Vaadin

Posted by Taha Siddiqi <ta...@gmail.com>.
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@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: Tapestry5 vs Vaadin

Posted by lukaszkaleta <lu...@gmail.com>.
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@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Tapestry5 vs Vaadin

Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
I think you are fixated on the number of components that are available in vaadin too much. Vaadin and GWT in general have to have their own components for everything because everything is built n JavaScript. Tapestry can get away with using plain HTML for both things so it's not really a valid comparison.
Saying that vaadin and GWT in general do have nice components that are richer than some of the tapestry ones. 

Personally I like to stick with the simpler approach on the client, I.e. tapestry. When I need one of those fancy components that are available on vaadin, GWT or smartgwt, I just use those on the tapestry page using the multiple available integration libraries. 

Both of these solution are vastly different and there is not a real direct simple comparison that you are trying to make. Each one is applicable for different circumstances. 
Good thing is that you can integrate vaadin or GWT components into tapestry pages. 



On Aug 11, 2012, at 2:30 PM, Muhammad Gelbana <m....@gmail.com> wrote:

> So is there any Vaadin users already using tapestry5 too and could give me
> a comparison based on his experience ?
> 
> I've never used Vaadin but what I can say about it after I visited it's
> website is that it's much more UI component rich when compared to tapestry
> but it has no IoC support. Of course the lack of UI components in t5 can be
> mitigated by using external libraries\frameworks but I'm comparing based on
> the OTB features that requires no efforts to import.
> 
> I see it as:
> 
> Vaadin + IoC = Tapestry5 + GWT (But still Vaadin will have more UI
> components OTB)
> 
> What do you think ?
> 
> -- 
> *Regards,*
> *Muhammad Gelbana
> Java Developer*

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Tapestry5 vs Vaadin

Posted by trsvax <tr...@gmail.com>.
I added a comment to your issue.

I think you want something like this 

public interface DAO {
	
	@Binder(implementation=CartDAOImpl.class)
	public CartDAO cart();
	...
	@Binder(implementation=ItemDAOImpl.class)
	public ItemDAO item();
}

In your AppModule
binder.bind(DAO.class, new LibraryBuilder(DAO.class,binder)).eagerLoad();

public class LibraryBuilder<T> implements ServiceBuilder {
	private final Class[] interfaces;
	
	public LibraryBuilder(Class<T> clazz, ServiceBinder binder) {
		interfaces = new Class[] { clazz };
		for ( Method m : clazz.getDeclaredMethods() ) {
			Binder args = m.getAnnotation(Binder.class);
			binder.bind(m.getReturnType(),args.implementation());
		}
	}

	@Override
	public Object buildService(ServiceResources resources) {
		return Proxy.newProxyInstance(interfaces[0].getClassLoader(), interfaces,
new Service(resources));
	}
	
	public class Service implements InvocationHandler {
		private final ServiceResources resources;

		public Service(ServiceResources resources) {
			this.resources = resources;
		}

		@Override
		public Object invoke(Object proxy, Method method, Object[] args)
				throws Throwable {
			Class<?> serviceInterface = method.getReturnType();
			return resources.getService(serviceInterface);
		}
		
	}
}



--
View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry5-vs-Vaadin-tp5715273p5715381.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org