4 Replies Latest reply on Oct 29, 2013 6:19 AM by Hardy Massen

    RF 4.3.4: Configuring ResourceServlet in Servlet 3.0

    Hardy Massen Novice



      in the RF DeveloperGuide http://docs.jboss.org/richfaces/latest_4_3_X/Developer_Guide/en-US/pdf/Developer_Guide.pdf one can read, that the ResourceServlet is automatically registered with Servlet 3.0.


      We use JBoss EAP 6.1.1, JSF 2.1 and RF 4.3.4, so Servlet 3.0 is available. Every setting we have found is pointing to servlet 3.0.



      If we don't use RF Resource optimization (org.richfaces.resourceOptimization.enabled = false) we get a HTTP 500 error:

      HTTP 500 GET skinning.ecss.xhtml?db=eAHjW!XqPQAE!QKS




      If we use RF Resource optimization (org.richfaces.resourceOptimization.enabled = true) and don't configure the ResourceServlet explicitly, we get


      HTTP 404 Errors for skinning.css, jquery.js and packed.js

      Requests are like this one: http:localhost:8080/ourApp/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.3.4.Final/PackedCompressed/DEFAULT/skinning.css" />


      So it seems, that the ResourceServlet is not registered/not working.



      If we register the ResourceServlet explicitly...



      <servlet-name>Resource Servlet</servlet-name>





      <servlet-name>Resource Servlet</servlet-name>




      ...everything works fine.


      So, my 2 questions are:

      - Why do we get the HTTP 500-error described at point 1) while getting skinning.ecss.xhtml?db=eAHjW!XqPQAE!QKS?

      - Why do we have to register the ResourceServlet explicitly?



      Hardy Massen