Hi Marek, Please post a link to your article once it is published. My native language is Belarusian, but can read Polish just a little bit (but better don't try to reply in Polish :-)).
As for Tapestry vs. pure servlets, the gap is so huge that there is not much to compare. Basically, servlet API in regards to Tapestry is simply a low level protocol layer, providing the API to the underlying HTTP, but no presentation handling techniques, or page navigation (there is no concept of a page in servlets to begin with). So servlets and Tapestry are rather complimentary to each other: servlets provide transport layer (so to speak), and Tapestry provides high level application API. JSP, on the other hand, is a "competing" technology, since it attempts to provide a presentation layer on top of servlets, just like Tapestry does. At this the similarities end... I guess you can read some more on Tapestry home page about the differences, but the main conceptual difference is that Tapestry provides a way to dynamically bind your model and controller classes to the HTML template (providing standard ways to handle those models and controllers), while JSP allows to write Java code directly in the template, mixing logic and presentation (a big no-no in any kind of GUI design). Andrus Adamchik http://objectstyle.org/cayenne/ > Hello > > I'm going to write an article about Tapestry (and Cayenne) for Polish > Linux magazine - so I'd like to ask if you have any suggestions about > what I should write to encourage people to give Tapestry a shot. I am > especially interested in its advantages over servlets (yeah, I know > Tapestry application is a servlet, too :) and JSP. > > TIA > -- > Marek Janukowicz > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
