On Thu, Mar 13, 2014 at 9:33 AM, burghard.britzke < b...@charmides.in-berlin.de> wrote:
> may be restarting the context would even be sufficient? May be the > FacesServlet has an issue which implementation are you using? which > version? which version of PrimeFaces? > > earlier, in the thread, he provided the following: Chrome console output: > Resource interpreted as Stylesheet but transferred with MIME type > text/plain: " > http://spdata-apps.net/cliente/javax.faces.resource/theme.css.jsf?ln=primefaces-redmond ". > login.jsf:3 > Resource interpreted as Script but transferred with MIME type text/plain: " > http://spdata-apps.net/cliente/javax.faces.resource/primefaces.js.jsf?ln=primefaces&v=4.0.9 ". > login.jsf:3 > Resource interpreted as Image but transferred with MIME type text/plain: " > http://spdata-apps.net/cliente/javax.faces.resource/loading26.gif.jsf?ln=image ". > login.jsf:22 > GET > http://spdata-apps.net/cliente/javax.faces.resource/primefaces.css.jsf?ln=primefaces&v=4.0.9net::ERR_INVALID_CHUNKED_ENCODING login.jsf:3 primefaces&v=4.0.9 PrimeFaces Elite 4.0.9 Since I usually scour PrimeFaces forum topics, this is the first person that I have heard/seen using tomcat 8.0.x with PrimeFaces.
