[jbosstools-issues] [JBoss JIRA] (JBIDE-26016) javax.websocket is missing from default classpath entries of WildFly 12 Runtime

[Martin Malina (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-26016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina closed JBIDE-26016.
---------------------------------


I verified that javax.websocket.api is in the default classpath entries for WildFly 12 as well as older wf versions. (devstudio-12.0.0.AM2-v20180528-0716-B2581-installer-standalone.jar)

> javax.websocket is missing from default classpath entries of WildFly 12 Runtime
> -------------------------------------------------------------------------------
>
>                 Key: JBIDE-26016
>                 URL: https://issues.jboss.org/browse/JBIDE-26016
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.5.3.Final
>         Environment: Windows 7, Eclipse Oxygen.3a Release (4.7.3a), WildFly 12.0.0. Final
>            Reporter: Marco Del Percio
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 4.6.0.AM2
>
>         Attachments: javax.websocket.missing.png
>
>
> When creating a new server instance based on WildFly 12 Runtime, the default classpath entries of such runtime do not include javax.websocket.
> The workaround is to manually amend the default classpath entries for that runtime and add the missing module.
> javax.websocket has always been there by default until WildFly 11 Runtime, I don't see why it shouldn't be there with WildFly 12 Runtime



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)