Typo or intentional mistake?

[Borut Bolčina <bo...@gmail.com>]

Hello,

can't help myself to let all know. On pages 10 and 11 of the "Beggining
JBoss Seam From Novice to Professional" there is a paragraph about Tapestry:

Tapestry is another web framework that has been around for a long time. The
major recent upgrade of Tapestry 4 is powerful. One of its biggest
advantages is that, contrary to JSF and most other web frameworks, your
Tapestry classes have no knowledge that they are part of a web state because
your controller classes (pages in Tapestry) have no knowledge of the request
or the session. However, unlike Seam, these pages are not POJOs but they
implement the IPage interface. Another advantage of Seam is the use of
Object-Graph Navigation Language (OGNL) for its presentation tier. This
allows HTML and Java developers to create HTML pages that can be translated
to dynamic code when run in the application server, but if viewed with a
standard web browser outside the application server, the pages will still be
viewable. This is not normal behavior for most web application servers. A
Seam-Tapestry combination would be great. Unfortunately, there is no plan to
build one at this time.

Notice what it says about "Another advantage of Seam..."

English is not my first language, but isn't that a mistake?

Regards,
Borut

Re: Typo or intentional mistake?

[Nick Westgate <ni...@key-planning.co.jp>]

A tragic mistake! The only paragraph about Tapestry and they get it wrong!

Cheers,
Nick.


Borut Bolčina wrote:
> Hello,
> 
> can't help myself to let all know. On pages 10 and 11 of the "Beggining
> JBoss Seam From Novice to Professional" there is a paragraph about Tapestry:
> 
> Tapestry is another web framework that has been around for a long time. The
> major recent upgrade of Tapestry 4 is powerful. One of its biggest
> advantages is that, contrary to JSF and most other web frameworks, your
> Tapestry classes have no knowledge that they are part of a web state because
> your controller classes (pages in Tapestry) have no knowledge of the request
> or the session. However, unlike Seam, these pages are not POJOs but they
> implement the IPage interface. Another advantage of Seam is the use of
> Object-Graph Navigation Language (OGNL) for its presentation tier. This
> allows HTML and Java developers to create HTML pages that can be translated
> to dynamic code when run in the application server, but if viewed with a
> standard web browser outside the application server, the pages will still be
> viewable. This is not normal behavior for most web application servers. A
> Seam-Tapestry combination would be great. Unfortunately, there is no plan to
> build one at this time.
> 
> Notice what it says about "Another advantage of Seam..."
> 
> English is not my first language, but isn't that a mistake?
> 
> Regards,
> Borut
> 

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