Changing JSF prefix to suffix mapping forces me to reapply the mapping on CSS background images

by

and then I see that everything going through FacesServlet has .xhtml appended to it, so that the browser is requesting .png.xhtml files, .css.xhtml file – is this right?

This only applies to resources included by <h:outputStylesheet> and <h:outputScript>. This is not related to the change in the URL mapping. This is related to the change from JSF 1.x to JSF 2.x and the change from <link rel="stylesheet"> and <script> to the aforementioned JSF2 tags.

For your own scripts, stylesheets and other static stuff which is to be served from the public webcontent, you should not manually add the .xhtml extension. You should not need to change anything with regard to existing static resources.

Only for CSS background images and other url() references in CSS files which is to be included using the <h:outputStylesheet> tag (and thus not for <link rel="stylesheet>), you would need to change the url() location to be dynamically resolved by EL. You would need to use the following syntax instead:

body {
    background-image: url("#{resource['libraryname:path/to/image.png']}");
}

Imagine that you have the following /resources folder structure:

WebContent
 |-- META-INF
 |-- resources
 |    `-- default
 |         |-- images
 |         |    `-- background.png
 |         `-- css
 |              `-- style.css
 |-- WEB-INF
 `-- test.xhtml

and that you’re including the style.css in test.xhtml as follows

<h:outputStylesheet library="default" name="css/style.css" />

then you should be defining the background image URL as follows

body {
    background-image: url("#{resource['default:images/background.png']}");
}

Or when you’re relying on the default library, thus you aren’t using the library, then it should rather look like this:

WebContent
 |-- META-INF
 |-- resources
 |    |-- images
 |    |    `-- background.png
 |    `-- css
 |         `-- style.css
 |-- WEB-INF
 `-- test.xhtml

test.xhtml:

<h:outputStylesheet name="css/style.css" />

style.css:

body {
    background-image: url("#{resource['images/background.png']}");
}

As to the securiry constraint, it is not needed when you’re already using the *.xhtml mapping. The security constraint is intended to prevent the enduser from seeing the raw XHTML source code when the FacesServlet is mapped on a pattern other then *.xhtml. The enduser would be able to see the XHTML source code by just removing /faces part from the URL in case of a /faces/* mapping or renaming .jsf to .xhtml in case of a *.jsf mapping. Get rid of the security constraint, it makes in your case things worse as you’re already using a *.xhtml mapping which makes it already impossible to see the raw XHTML source code by hacking the URL.

More Related Contents:

  1. How to use JSF generated HTML element ID with colon “:” in CSS selectors?
  2. How to reference JSF image resource as CSS background image url
  3. JSTL in JSF2 Facelets… makes sense?
  4. JSF returns blank/unparsed page with plain/raw XHTML/XML/EL source instead of rendered HTML output
  5. How do I override default PrimeFaces CSS with custom styles?
  6. How to include another XHTML in XHTML using JSF 2.0 Facelets?
  7. How to reference CSS / JS / image resource in Facelets template?
  8. Why do I need to nest a component with rendered=”#{some}” in another component when I want to ajax-update it?
  9. Is it possible to use JSF+Facelets with HTML 4/5?
  10. Which XHTML files do I need to put in /WEB-INF and which not?
  11. Why Facelets is preferred over JSP as the view definition language from JSF2.0 onwards?
  12. Error parsing XHTML: The content of elements must consist of well-formed character data or markup
  13. Obtaining Facelets templates/files from an external filesystem or database
  14. Packaging Facelets files (templates, includes, composites) in a JAR
  15. Handling a colon in an element ID in a CSS selector [duplicate]
  16. How can I set id of a component/tag inside ui:repeat
  17. How to use Font Awesome from webjars.org with JSF
  18. How to create a custom Facelets tag?
  19. Avoiding duplicate ids when reusing facelets compositions in the same naming container
  20. How to implement a dynamic list with a JSF 2.0 Composite Component?
  21. How to use 3rd party CSS libraries such as Font Awesome with JSF? Browser can’t find font files referenced in the CSS file
  22. Error Parsing /page.xhtml: Error Traced[line: 42] The entity “nbsp” was referenced, but not declared
  23. Why is the getter called so many times by the rendered attribute?
  24. How to align items in a to the right
  25. how to share a jsf error page between multiple wars
  26. How to override stylesheets of PrimeFaces? [duplicate]
  27. Does it matter whether place f:event inside f:metadata or not?
  28. Why Facelets is preferred over JSP as the view definition language from JSF 2.0 onwards?
  29. Styling elements with a dot (.) in the class name
  30. Correct terms and words for sections and parts of selectors

Leave a Comment