Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3507

REGRESSION: JSP servlet cannot be mapped to different extensions

    XMLWordPrintable

    Details

    • Steps to Reproduce:
      Hide

      Please find attached a minimal Eclipse project that demonstrates the issue. To reproduce:

      1. Deploy example on JBoss 7.1.1.Final
      2. Hit either index.html or test.jsp. Both evaluate the JSP expression '${1+1}' and display '2'
      3. Deploy same example to WildFly 8.1.0.Final
      4. Now only test.jsp works, not index.html

      Show
      Please find attached a minimal Eclipse project that demonstrates the issue. To reproduce: 1. Deploy example on JBoss 7.1.1.Final 2. Hit either index.html or test.jsp. Both evaluate the JSP expression '${1+1}' and display '2' 3. Deploy same example to WildFly 8.1.0.Final 4. Now only test.jsp works, not index.html
    • Affects:
      Compatibility/Configuration
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Use only .jsp (or probably .jspx) extensions for your JSPs.

      Show
      Use only .jsp (or probably .jspx) extensions for your JSPs.

      Description

      When migrating an app from JBoss 7.1.1.Final to WildFly 8.1.0.Final, one can no longer remap the default JSP servlet to different extensions.

      This is useful when you want some lightweight server-side processing of, say, JavaScript or CSS files.

        Attachments

          Activity

            People

            Assignee:
            ehugonnet Emmanuel Hugonnet
            Reporter:
            kennardconsulting Richard Kennard (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: