[jboss-jira] [JBoss JIRA] (WFLY-3507) REGRESSION: JSP servlet cannot be mapped to different extensions

[Richard Kennard (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977196#comment-12977196 ] 

Richard Kennard commented on WFLY-3507:
---------------------------------------

So the old mapping (<servlet-name>jsp</servlet-name>) approach doesn't work in the dev build, but the new (<jsp-config>) approach does. Is this considered a bug, or was the old approach always considered non-standard and the new approach is the 'official' way it should now be done?

> REGRESSION: JSP servlet cannot be mapped to different extensions
> ----------------------------------------------------------------
>
>                 Key: WFLY-3507
>                 URL: https://issues.jboss.org/browse/WFLY-3507
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Undertow)
>    Affects Versions: 8.1.0.Final
>            Reporter: Richard Kennard
>            Assignee: Emmanuel Hugonnet
>         Attachments: jsp-mapping.zip
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)