RF ResourceServlet not working after upgrading from RF 4.3.4 to RF 4.5.1

[ibenjes]

Hi

I am trying to upgrade from RF 4.3.4 to RF 4.5.1.Final but suddenly the packed.js, packed.css and jquery.js files cannot be loaded anymore:

>localhost:8080/MyAPP/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.5.1.Final/PackedCompressed/DEFAULT/packed/packed.css

>localhost:8080/MyAPP/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.5.1.Final/PackedCompressed/packed/packed.js

>localhost:8080/MyAPP/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.5.1.Final/PackedCompressed/org.richfaces/jquery.js

All come back with a 404 error.

The page itself builds fine and I can see this in the logfile:

>RichFaces Core by JBoss by Red Hat, version 4.5.1.Final

With RF 4.3.4 we had 4 jars,

richfaces-components-api-4.3.4.Final.jar

richfaces-core-api-4.3.4.Final.jar

deployed to the main application lib directory

and

richfaces-components-ui-4.3.4.Final.jar

richfaces-core-impl-4.3.4.Final.jar

which were deployed to the /WEB-INF/lib directory of the war.

I now have all 3 deployed to the main lib directory (is that correct?)

The setup is JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8)

Seam 2.3.1.Final

We also deploy Primeface 5.2. The combination RF 4.3.4 and PF 4.0 or RF 4.3.4 and PF 5.2 works fine (we used to have a fix that both load the same jQuery version but I have taken that out, to see whether that was causing the problem but that wasn't the case).

Any ideas what could be wrong here?

This is an extract of our web.xml:

<web-app version="3.0"
 xmlns="http://java.sun.com/xml/ns/javaee"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">

 
 <!--  RichFaces -->
<context-param> <param-name>org.richfaces.queue.global.enabled</param-name> 
<param-value>true</param-value>
</context-param>



   <!-- Suppress spurious stylesheets -->

   <context-param>
      <param-name>org.richfaces.enableControlSkinning</param-name>
      <param-value>false</param-value>
   </context-param>

   <context-param>
      <param-name>org.richfaces.enableControlSkinningClasses</param-name>
      <param-value>false</param-value>
   </context-param>

   <!-- Change load strategy to DEFAULT to disable sending scripts/styles as packs -->

   <context-param>
      <param-name>org.richfaces.resourceOptimization.enabled</param-name>
      <param-value>true</param-value>
   </context-param>

<!-- more custom non-RF related stuff -->
</web-app>

Thanks for your help

[ibenjes]

Any ideas? Any ways I can debug this?

[michpetrov]

Your settings are correct, there's probably a conflict with one of the libraries. From what I've seen Seam doesn't really work with 4.5.x so that might be it.

[ibenjes]

What do you mean Seam doesn't really work with 4.5? Seam 2.3 worked fine with RF 4.3.4 why wouldn't it suddenly work with RF 4.5? Is RF 4.5 not supposed to be backwards compatible?

[michpetrov]

RF 4.5.x is backwards compatible with RF 4.3.x, it doesn't mean it's compatible with Seam (just like it isn't compatible with JSF versions under 2.1.28 for example). Seam is no longer in development and we cannot guarantee it works; based on other reports I don't think does.

[ibenjes]

Sorry but I really don't get this. Last year RF announced that it would not focus on innovation but stability. For everyone that read that blog it means if you want to start with a new project don't use RF because it is at the end of its lifetime and is now only in maintenance mode.

So if RF is mainly still used for older project (and a lot will be based on the old JBoss dream team of Seam+RF) are you now breaking the compatibility for all these projects? If you do maintenance than don't break compatibility with the frameworks RF was used with. I know that Seam isn't actively developed anymore but that doesn't mean every enterprise project stopped using seam straight away. These systems have a long lifetime!

[michpetrov]

We're not breaking the compatibility deliberately. However since Seam is no longer being developed (and no part of RichFaces depends on it) we do not have to actively check if it is still working. If you find a problem then by all means file a JIRA issue, I can take a look at it and try to fix it but for us there is no requirement to maintain the compatibility.