Get parameter with preRenderView

Splash Forums PrettyFaces Users Get parameter with preRenderView

This topic contains 4 replies, has 3 voices, and was last updated by  Lincoln Baxter III 5 years, 11 months ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #18079

    manu206
    Participant

    Hi,

    i have a really annoying problem. My preRenderView method is triggered twice.

    Insert URL: http://localhost:8080/test/parameter

    Url output first time: /test/parameter

    Url output second time: /test/RES_NOT_FOUND

    I don’t know why it triggers preRenderView twice. With disabled prettyfaces everything works fine with http://localhost:8080/test.jsf?parameter=value

    Prettyfaces config:

    ‘<url-mapping>

    <pattern value=”/test/#{parameter}”></pattern>

    <view-id>/test.jsf</view-id>

    <dispatcher>FORWARD</dispatcher>

    </url-mapping>’

    I’m using primefaces 3M4 + Mojarra 2.1.3 + Prettyfaces 3.3.1

    Is there any solution?

    #21662

    Interesting issue. Could you post the relevant parts of your xhtml file and the bean?

    #21663

    I tried to reproduce this but everything works fine in my test. I’m using the same setup (primefaces 3M4 + Mojarra 2.1.3 + Prettyfaces 3.3.1) and deployed the app to Tomcat 7.0.

    Are there any other libraries in your project? And could you post your web.xml?

    #21664

    manu206
    Participant

    Thanks for your reply ;)

    I solved the problem.

    I have some jQuery statements in my body. In this example I try to call a function which highlights primefaces components after validation.

    <h:outputScript>

    setHighlight(‘${highlight}’);

    </h:outputScript>

    After replacing h:outputScript to simple script tag it worked without duplicate calls.

    <script type=”text/javascript”>

    setHighlight(‘${highlight}’);

    </script>

    Very strange behaviour

    Thanks for your help ;)

    #21665

    Awesome! Glad you got this working.

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

You must be logged in to reply to this topic.

Comments are closed.