Win a copy of Beginning Java 17 Fundamentals: Object-Oriented Programming in Java 17 this week in the Java in General forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

Chrome JSF Actions Problem

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

I have a problem using JSF <CommandLink> actions in Chrome Navigator. It works perfectly in Firefox and IE.



When i redirect to a .jspx page using a navigation-rule i get in Chrome and Safari this error:

¬°Oh no!
'An error produced showing the webpage. To continue ...'

This is my:

faces-config.xml
------------------



web.xml:
----------



Can anyone help me?

Thanks!!
 
fernando aguilera
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I got the solution!

You must put the contentType in the <f:view> tag in each .jspx page you have.



Chrome needs to know this information.

If warning appears, don't worry, it works correctly
 
Greenhorn
Posts: 2
Netbeans IDE Firefox Browser
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Excellent! I was trying to figure out why Chrome was giving me an error re: xml in my document when using JSF templating. Putting <f:view contentType="text/html" /> fixed that problem. Thanks!
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic