jsf 2 - XML prolog / instruction not removed from XHTML output -


i'm starting learn javaserver faces (jsf). i'm using glassfish 3+. i've created new jsf project in netbeans , run project. worked fine, upon examining xhtml output, noticed xml declaration left in. messes doctype declaration (which supposed first in document).

enter image description here

is jsf supposed remove xml declaration, or there i've done wrong?

facelets default remove compositions (include files , composite components) , tag files. won't remove master template. remove yourself. shouldn't using xml prolog @ when authoring html.

whether xml prolog removed master template specified in appendix 1.1.1.1 of jsf 2.2 specification describes configuration of <facelets-processing> element in faces-config.xml. xml prolog described "processing instructions". in table, you'll see removed (consumed) when template processed xml or jspx view.

1.1.1.1 facelets-processing element

the <facelets-processing> element used affect processing of facelets vdl files. therefore, setting applies requests reach facelets viewdeclarationlanguage implementation, specified runtime via javax.faces.facelets_view_mappings , javax.faces.default_suffix <context-param> entries. specification defines 3 processing modes facelets files: facelets xhtml syntax, xml view syntax, , facelets jspx syntax. last syntax intended ease migration facelets applications using jsp document syntax (also known jspx syntax). affect on processing of files in each of these 3 modes specified in following table.

valid <process-as> values , implications on processing of facelets. -----------------------------------------------------------------------------------------               <process-as>         <process-as>         <process-as>       <process-as>               html5</process-as>   xhtml</process-as>   xml</process-as>   jspx</process-as>               html 5 (default)     facelets xhtml       xml view           facelets jspx ----------------------------------------------------------------------------------------- xml doctype   simplified        passed through       consumed           consumed               <!doctype html>    xml           passed through       passed through       consumed           consumed declaration   processing    passed through       passed through       consumed           consumed instructions  cdata         passed through       passed through       consumed           consumed section  escaping of   escaped              escaped              escaped            not escaped inline text      xml           passed through       passed through       consumed           consumed comments

in preceding table, “passed through” means content passed through unmodified user agent. “consumed” means content silently consumed on server. note cdata sections, content of cdata section passed through, if start , end tags should consumed. “escaped” means sensivite content in response automatically escaped: & becomes &amp;, example. “not escaped” means such content not escaped.

in other words, when you're authoring html5/xhtml, have remove yourself. better wording actually: you shouldn't including xml prolog in html5 , xhtml pages that's not required; it's required in xml , jspx pages (and facelets automatically remove it).

see also:

unrelated concrete problem, should using <h:outputstylesheet> instead of <link rel="stylesheet"> independent request url.

<h:outputstylesheet name="css/default.css" /> <h:outputstylesheet name="css/csslayout.css" />

see also:


Comments

Post a Comment

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

i'm trying link specific pdf page msoutlook'10 or msword'10, #page=... anchor particularly useful , works fine elsewhere. unfortunately when click [ctr-k] in outlook or winword, links re-formatted assuming unc path. pdf file located on shared drive. using "file:" prefix links open pdf in adobe reader (outside of browser), , "http:" open inside browser. issue seem need open in browser "file:" prefix in order anchor work. know anchors work inside browser. outlook uses windows/explorer default program (based on file extension) seems open in adobe reader neglecting anchor. is aware of solution, link specific page or bookmark of shared-pdf ms outlook and/or winword link? common references: mailermailer.com/...anchor-tags-html-emails campaignmonitor.com/...anchor-links-in-email-newsletters/ stackoverflow.com/...anchor-in-pdf-document
Read more

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

consider code: test = function() { } t = new test(); (var = 0; < 8; i++) { result = t instanceof test; } if change number of iterations 8 9 , loop take 100 times longer complete in latest version of firefox (41.0.1). tested on 2 different pcs , magic limit 8. here jsperf test used: http://jsperf.com/instanceof-8-times-vs-9-times does have idea why might happen? seems specific instanceof . not happen if else object, example check property. note: filed bugzilla bug this. jan de mooij mozilla team has posted details in bugzilla thread . here's simplistic interpretation of highly technical answers: in i < 8 case, firefox smart enough hoist result = t instanceof test; statement out of loop (according tests, doesn't seem omit altogether). in i < 9 case, apparently doesn't optimization . why? reason not clear, related fact 9 iterations threshold above function considered "hot" enough run through jit compiler. i < 8 cas...
Read more

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -

following this guide setup app on digital ocean droplet, not working. site not loading , it's throwing: "gateway time-out". the puma server works, since ps aux | grep puma prints: root 15878 0.0 0.4 376832 2168 ? sl 12:50 0:00 puma 2.13.4 (unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock) [20150930164940] root 15881 0.0 0.7 903676 3692 ? sl 12:50 0:06 puma: cluster worker 0: 15878 [20150930164940] root 24654 0.0 0.1 11748 916 pts/2 s+ 18:00 0:00 grep --color=auto puma my nginx config: user root; worker_processes 1; events { worker_connections 1024; } http { upstream puma { server unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock; } server { listen 80; server_name myapp.com; root /var/www/myapp/current/public; access_log /var/www/myapp/current/log/access.log; error_log /...
Read more