Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-26016

javax.websocket is missing from default classpath entries of WildFly 12 Runtime

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 4.6.0.AM2
    • 4.5.3.Final
    • server
    • None
    • devex #149 May 2018
    • Hide

      Create a new Server, assign WildFly 12 Runtime, create a new web project and add the server runtime library to the classpath. Now create a new class as a websocket endpoint and you'll see it won't compile because javax.websocket is missing in your runtime.
      See attachment as proof

      Show
      Create a new Server, assign WildFly 12 Runtime, create a new web project and add the server runtime library to the classpath. Now create a new class as a websocket endpoint and you'll see it won't compile because javax.websocket is missing in your runtime. See attachment as proof

      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

        1. javax.websocket.missing.png
          javax.websocket.missing.png
          139 kB

              rob.stryker Rob Stryker (Inactive)
              marco.delpercio_jira Marco Del Percio (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: