Chapter 5. Known issues

To view information about known issues in this release of CodeReady Studio, see Known Issues.

The following known issues are highlighted:

  • JBDS-4710: Central page is not showing content properly after page reload.

    To work around this issue, reopen Red Hat central.

  • JBIDE-26118: Unable to create JSF2 composite component from current selected source.
  • JBDS-4818: CRS installer not signed for MacOS.

  • Target platform and installer known issues in CodeReady Studio:

    • JBIDE-27605: Conflicting dependency when updating from BYOE 2020-09 + JBT 4.17.0.Final to JBT 4.18.0.Final.

      To work around this issue, navigate to Help → Install New Software, select the Jbosstools stable update site and select both JAX-RS and JAX-WS features. Both features will be updated.

      Alternatively, select Preferences → Install/Update → Available Software and disable the latest Eclipse release. As a result, Eclipse 2020.12 is installed.

  • OpenShift known issues in CodeReady Studio:

    • JBIDE-27066: Unable to login to OpenShift 4.4.0 cluster using JDK11.

      To work around this issue, use the JDK version 8 or configure Java to use TLSv1.2 as your SSL protocol.

      To configure Java to use TLSv1.2, open the file codereadystudio.ini located in the studio directory inside of the CodeReady Studio installation directory.

      Add the following line under the -vmargs section: 

      -Djdk.tls.client.protocols=TLSv1.2

  • Webservices known issues in CodeReady Studio:

    • JBIDE-27743: Unable to create Web Service client from wsdl definition using Wildfly 22 and Apache CXF 3.3.5+.

      To work around this issue, use Apache Axis or JBossWS instead of CXF runtime to continue your service client definition.
      Alternatively, update and export the order of your source folder so that your source folder appears first. To do so, use the following path: Dyn. Web Project → Properties → Java Build Path → Order.

    • JBIDE-27744: WS Tester does not allow POST request due to low size of DH key.
    • JBIDE-27781: NPE occurs during deletion of Dynamic Web Project with generated web.xml descriptor.
    • JBIDE-27842: WS Tester JAX WS invocation for local wsdl results in error message Provider org.apache.axis2.jaxws.spi.Provider not found.

  • Code Ready Containers known issues in CodeReady Studio:

    • JBIDE-27741: CRC does not start properly and results in error message Unable to execute request to request url https://api.crc.testing:6443/.well-known/oauth-authorization-server.

    • JBIDE-27921: CRC 1.28.0 setup on Windows and MacOS does not provide bin/oc anymore and prevents CRC tooling to start.

      To work around this issue, go to the CRC home folder and create a bin directory.

    • JBIDE-27927: CDK tooling cannot get into Started state even though CDK is started on Windows 10.

  • Fuse Integration Project known issues in CodeReady Studio:

    • FUSETOOLS-3337: Unable to deploy Fuse project with DataTransformation to Fuse on Karaf 7.x runtime.

    • FUSETOOLS-3373: Fuse Integration Project created with an error for Camel version Fuse 7.2 and 7.1.

      To work around this issue, add the following lines to the jakarta.xml.bind-api file to define the jakarta version: 

      <dependency>
<groupId>jakarta.xml.bind</groupId>
<artifactId>jakarta.xml.bind-api</artifactId>
<version>2.3.3</version>
</dependency>

      The latest available version is 2.3.3. For further information on the latest version, see Maven Repository: Jakarta XML Binding API.