Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-78

Red Hat Fuse stack (org.eclipse.che.ls.camel?) causes NPEs when using Quick Fix

XMLWordPrintable

    • Hide
      • Create the workspace from the Red Hat Fuse-stack with the sample project spring-boot-camel
        (docker-image: quay.io/crw/stacks-java)
      • Open IDE, open java file (e.g. Application.java)
      • Go to cursor position 32:27 an add some symbol (e.g. 'r')
      • Try to use the 'Quick Fix' by Menu Commands ( Assistant -> Quick Fix) or keyboard (Alt+Enter)
      Show
      Create the workspace from the Red Hat Fuse -stack with the sample project spring-boot-camel (docker-image: quay.io/crw/stacks-java ) Open IDE, open java file (e.g. Application.java ) Go to cursor position 32:27 an add some symbol (e.g. ' r ') Try to use the ' Quick Fix ' by Menu Commands ( Assistant -> Quick Fix) or keyboard (Alt+Enter)

      When you try to use the 'Quick Fix' in the dev-machine console there is error (java.lang.NullPointerException: null) and the feature does not work.
      And despite that the docker image is used in other Java stacks, this bug is reproduced only on the Red Hat Fuse stack. Might suppose the problem is not in stack, and in the sample project.

        1. Che7-WorkingQuickfix.png
          151 kB
          Aurélien Pupier
        2. crw-78-quickfix-doesnt-work.png
          296 kB
          Nick Boldt
        3. fuse-vs-eap-extra-lang-server.png
          157 kB
          Nick Boldt
        4. rhfuse-editor-quick-fix.png
          474 kB
          Shmaraiev Oleksandr
        5. springboot-vs-fuse-stack_1.png
          73 kB
          Nick Boldt
        6. springboot-vs-fuse-stack_2-commands.png
          103 kB
          Nick Boldt

              nickboldt Nick Boldt
              oshmarai Shmaraiev Oleksandr
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: