• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

What are the advantages?

 
Ranch Hand
Posts: 198
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What are the advantages of the tapestry framework over struts?
Which IDE's at present can plugin the tapestry to it?
 
Ranch Hand
Posts: 390
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Like some one already mentioned; tapestry is component based while struts is action based.

Tapestry uses a html template to display its view compared to struts that uses jsp - This means you can view or see what the view is going to be like in an html editor for tapestry, while in the case of struts you are going to need a appserver to view what your view is going to look like - actually this is an advantage tapestry has over JSF.
 
Ranch Hand
Posts: 15304
6
Mac OS X IntelliJ IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Anselm Paulinus:
Tapestry uses a html template to display its view compared to struts that uses jsp - This means you can view or see what the view is going to be like in an html editor for tapestry, while in the case of struts you are going to need a appserver to view what your view is going to look like



This isn't entirely true. You are still going to have dynamic data that won't be available in both cases. Both tapestry templates and JSP uses the Expression Languages so you are going to have ${} placeholders. Not to mention JSP's taglibs and Tapestry's XML Namespaces (that server basically the same purpose) are going to render incorrectly.

That said I find it hard to believe that anyone doing serious web application development spends time looking at their pages outside of the app server's container.
 
Tina Ma
Ranch Hand
Posts: 198
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
may be like at very initial scratch stage, when one needs to check if all the components are placed out correctly, it helps. Noone might do that, but its still an added feature.
 
Gregg Bolinger
Ranch Hand
Posts: 15304
6
Mac OS X IntelliJ IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by sreerupa basu:
may be like at very initial scratch stage, when one needs to check if all the components are placed out correctly, it helps. Noone might do that, but its still an added feature.



And yet, just as possible with JSP's as it is with T5 templates.
 
Tina Ma
Ranch Hand
Posts: 198
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
But paulinus mentions, it can be checked without an appserver running!
But when one is building a web application, an appserver is also present....so i guess there should be some stronger advantages or some special cases when using tapestry framework is easier. I am getting really interested in finding out the whole idea of how this Tapestry works.

Which design pattern does this support ....mainly?
 
author
Posts: 99
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Gregg Bolinger:



That said I find it hard to believe that anyone doing serious web application development spends time looking at their pages outside of the app server's container.



Agreed, but still it is much simpler to convert an HTML mock up that you used to inspire your customers into a Tapestry template than into a JSP page. Plus, in Tapestry there is simply no way to mix presentation and code.

But these are details. I would say that if the application is simple, there is no difference which framework you choose. But the more complex the application is and the more applications you create, the better the benefits of Tapestry will be seen as you will have to write much less code and you can easily package repeating functionality into your own libraries of custom components.
 
reply
    Bookmark Topic Watch Topic
  • New Topic