当javax.faces.PROJECT_STAGE为Production时，未定义mojarra

Question

Today I got the exception "mojarra is not defined".

I stumbled in the following questions: This , this and this .

Neither of those solver my issue.

After some debugging I fixed the issue by changing javax.faces.PROJECT_STAGE param in web.xml from:

<param-value>Production</param-value>

to:

<param-value>Development</param-value>

It fixed the issue, but what should I do when putting my project in production? Should I leave the param on development?

Answer 1

My component calls mojarra.ab(this,event,'valueChange',0,'menu-form:pagina-select') in development mode the jsf.js is mojarra, but when in production mode it seems to be a minified version of my faces, small extract of the beginning of the jsf.js in production mode: if(!window.myfaces){var myfaces=new function(){};window.myfaces=myfaces;}, even though my component still call mojarra.ab(...). I'll double check my server configuration

You've apparently experimented with both Mojarra and MyFaces and the MyFaces version of jsf.js is hanging in an agressive cache somewhere in the network pipeline. Clear at least the browser's and, if any, also the proxy's cache.

That it works in development stage is because the URL of the jsf.js contains an additional query string unique to Mojarra (it would return a non-minified version to ease debugging).

Answer 2

i ran into same trouble these days and i figured out, that it was caused by my extendend omnifaces resourcehandler.

public class VersionableResourceHandler extends DefaultResourceHandler {
  //...
  @Override
  public Resource decorateResource(Resource resource) {
    if (resource == null) {
        return resource;
    }
    return new RemappedResource(resource, resource.getRequestPath() + "?v=1_2_1");
  }
}

with

<param-value>Development</param-value>

the generated output with my appended version-string will be:

 <script type="text/javascript" src="/javax.faces.resource/jsf.js?ln=javax.faces&amp;stage=Development%3Fv=1_2_1"/>

with

<param-value>Production</param-value>

generated output looks like:

<script type="text/javascript" src="/javax.faces.resource/jsf.js?ln=javax.faces%3Fv=1_2_1"/>

which is invalid because of the second "?", so "?v=1_2_1" had to be replaced by "&v=1_2_1".

Answer 3

I had exactly the same issue, it was a conflict between JSF and PrimeFace. (If you are using primeface)

I previously use <h:commandLink actionListener="#controller.upadte"> and the solution is to use <p:commandLink actionListener="#controller.upadte">

I hope this solution works for you.