[jbosstools-issues] [JBoss JIRA] (JBIDE-18700) EAP 6.x Configuration shows Servlet 3.1 as a valid choice

[Fred Bricon (JIRA)]

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

Fred Bricon commented on JBIDE-18700:
-------------------------------------

So, I realized the main issue is actually that Web 3.1 is proposed by default for EAP. Servlet 3.1 is part of JavaEE 7 and is not supported by EAP6 (JavaEE 6)
So the proper fix is to remove the 3.1 option from the list of available dynamic web module versions. Default should be 3.0, which works with Java 6. That would fix the original problem (no error should be displayed).

> EAP 6.x Configuration shows Servlet 3.1 as a valid choice
> ---------------------------------------------------------
>
>                 Key: JBIDE-18700
>                 URL: https://issues.jboss.org/browse/JBIDE-18700
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Final
>            Reporter: Fred Bricon
>            Assignee: Rob Stryker
>             Fix For: 4.3.0.Alpha1
>
>
> - Create a new EAP 6.3 server
> - Create a new Dynamic Web Project
> - Select the EAP runtime
> => An error is shown : "Dynamic Web Module 3.1 requires Java 1.7 or newer."
> !http://content.screencast.com/users/fbricon/folders/Jing/media/ee20c272-5761-40ab-8fe8-1004533501c7/00000025.png!
> The EAP 6 Default Configuration should have the Java 1.7 Facet set by default.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)