Uploaded image for project: 'JSFUnit'
  1. JSFUnit
  2. JSFUNIT-267

Extension mapped to the FacesServlet will be changed.

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Out of Date
    • Affects Version/s: JSFUnit.1.3.0.Final
    • Fix Version/s: JSFUnit.2.0.0.Final
    • Component/s: Core
    • Labels:
    • Environment:

      Windows 7 x64 Enterprise, Glassfish 3.0.1 & JBoss AS 6, Maven 3, JSF 2.0 (Mojarra 2.0.2 with PrimeFaces 2.0.2, Facelets)

    • Steps to Reproduce:
      Hide

      Add the JSFUnit libraries to your project (no difference with maven or not) - run/deploy your application.

      Show
      Add the JSFUnit libraries to your project (no difference with maven or not) - run/deploy your application.

      Description

      After adding JSFUnit 1.3.0 libraries and after deployment on the appllication server (Glassfish and JBoss AS 6) the applilcation is no more accessible. The "xhtml" extension is changed to "jsfunit".

      Example: in the faces-config.xml:
      ...
      <welcome-file>index.xhtml</welcome-file>
      ...
      Appropriate URL for this configuration is: $hostname:port$/$contextpath$

      After adding of JSFUnit the URL has following structure: $hostname:port$/$contextpath$/index.jsfunit

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                ssilvert Stan Silvert
                Reporter:
                dimarzio Dmitriy Neretin
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: