HttpServletRequst argument was null

Splash Forums PrettyFaces Users HttpServletRequst argument was null

This topic contains 5 replies, has 2 voices, and was last updated by  lucasmurata 6 years, 5 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #17922

    lucasmurata
    Participant

    Hi guys,

    I am trying run my application on GF 3.1 / MS Server 2008 and throw exception:

    HttpServletRequest argument was null

    I saw this mensage on this code of prettyface:

    /**

    * Must create instance through the initialize() method

    */

    protected PrettyContext(final HttpServletRequest request)

    {

    Assert.notNull(request, “HttpServletRequest argument was null”);

    config = (PrettyConfig) request.getAttribute(CONFIG_KEY);

    if (config == null)

    {

    config = new PrettyConfig();

    }……

    ….

    This application is running fine in other computer.

    #20898

    What version of PrettyFaces are you using? Please make sure that you use the most recent version 3.2.1!

    If updating PrettyFaces doesn’t fix the problem please post the complete stacktrace. This will help to identify the problem.

    #20899

    lucasmurata
    Participant

    Hi, thanks for reply.

    I use most recent version.

    This is complete stacktrace:

    WebModule[/controle-ponto]PWC1321: Error invoking requestInitialized method on ServletRequestListener com.ocpsoft.pretty.faces.config.PrettyConfigListener java.lang.NullPointerException at com.sun.faces.application.ServletContextSensitiveSingletonStore.<init>(ServletContextSensitiveSingletonStore.java:83) at com.sun.faces.application.ApplicationFactoryImpl.getApplication(ApplicationFactoryImpl.java:92) at com.ocpsoft.pretty.faces.util.FacesFactory.getApplication(FacesFactory.java:31) at com.ocpsoft.pretty.faces.config.PrettyConfigListener.requestInitialized(PrettyConfigListener.java:34) at org.apache.catalina.core.StandardContext.fireRequestInitializedEvent(StandardContext.java:4551) at org.apache.catalina.core.StandardHostValve.preInvoke(StandardHostValve.java:626) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:662)

    And seem that some problem here:

    http://java.net/jira/browse/GLASSFISH-15615

    #20900

    lucasmurata
    Participant

    I saw this post: http://ocpsoft.com/support/topic/null-pointer-exception

    I think that this is some problem

    #20901

    Yes, this is a known problem of Mojarra shipped with the Glassfish version you are using.

    Please see this comment on the corresponding issue for a workaround:

    http://code.google.com/p/prettyfaces/issues/detail?id=90#c11

    #20902

    lucasmurata
    Participant

    solved

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.

Comments are closed.