Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-636) was last changed on 08-Jan-2014 21:09 by Harry Metske  

This page was created on 05-Sep-2005 00:27 by 203.160.236.214

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 1 removed 5 lines
JSF
JSF pages can't be previewed using a standard web browser. To preview a JSF page, you either need to use a JSF design tool, or to deploy the application for real.
JSP is the primary view technology for JSF, but not the only one.
Tapestry
Tapestry templates don't need to be HTML. Tapestry supports any markup, provided that the Tapestry tags themselves are well-formed XML, in the sense that the opening tag must be well-formed and have a corresponding well-formed closing tag. Tapestry templates are implemented in the markup language of their target environment, which would typically be HTML or WML for wireless applications. Tapestry templates can be previewed without being deployed onto a Servlet container.
At line 7 removed 4 lines
The fact that JSF tags don't look like HTML makes it harder to learn to use them initially. Not that many Java programmers I know enjoy editing HTML, but at least they are generally comfortable doing it.
The purported benefit of the JSF abstraction is greater flexibility in targeting different devices with the same template markup The cost, however, is a loss of control; your template no longer precisely expresses the output. There is also more to learn, as you need to learn a new tag library, and how this maps to HTML. Over time, the compactness of the JSF format may help you to edit your templates more quickly, although this advantage will be less relevant for users of JSF design tools.
For me the costs of the JSF approach outweigh the advantages. The same template will rarely be used for different devices except in the simplest cases. Although JSF design tools make constructing and previewing JSF templates easier, they are no direct substitute for the mature HTML design tools currently used by web designers. The JSF approach also places more reliance on Java developers for layout design, because most HTML page designers will be uncomfortable using JSF tools.
Version Date Modified Size Author Changes ... Change note
636 08-Jan-2014 21:09 3.325 kB Harry Metske to previous pageviewplugin added
635 02-Oct-2013 21:50 3.305 kB Harry Metske to previous | to last changed incubator link
634 17-May-2013 19:36 3.427 kB Harry Metske to previous | to last add hint to http://incubator.apache.org/jspwiki/
633 10-Jun-2012 10:43 3.309 kB Janne Jalkanen to previous | to last JSPWikiFAQ456876 ==> JSPWikiFAQ
632 07-Jun-2012 07:11 3.315 kB kejinpu to previous | to last JSPWikiFAQ ==> JSPWikiFAQ456876
631 31-Dec-2011 22:11 3.309 kB Janne Jalkanen to previous | to last
630 23-Sep-2010 12:20 3.327 kB Janne Jalkanen to previous | to last Project Tattooine ==> OneMinuteWiki
629 13-Sep-2010 13:08 3.313 kB Michael e Whyte to previous | to last OneMinuteWiki ==> Project Tattooine
628 27-Jul-2010 15:29 3.309 kB 孙兵 to previous | to last ContributedTemplates ==> ContributedTemplate
627 24-Apr-2010 17:17 3.31 kB Florian Holeczek to previous | to last restored version
626 14-Mar-2010 10:20 3.307 kB naser to previous | to last JSPWikiDocumentation ==> 1.3.6.1.5.5.7.3.2
625 08-Jan-2009 21:15 3.31 kB Janne Jalkanen to previous | to last Corrected license info
624 19-Mar-2008 17:36 3.333 kB JanneJalkanen to previous | to last
623 19-Mar-2008 17:02 0.002 kB Giraffe to previous | to last restored
622 13-Mar-2008 16:19 3.333 kB JanneJalkanen to previous | to last
621 13-Mar-2008 14:58 3.347 kB David Au to previous | to last restored
« This page (revision-636) was last changed on 08-Jan-2014 21:09 by Harry Metske