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

NPE when renaming runtime and then rightclicking on server before saving server editor

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 3.3.0.CR1
    • 3.3.0.Beta3
    • server
    • None
    • Hide

      1. Add a server runtime and server (e.g. use JBT runtime detection to add AS 7.1.1)
      2. Double click the server in server view to open the server editor
      3. Click Runtime Environment and change the runtime name, Finish
      4. Right-click the server in server view - you will get a NPE in the log - FAIL

      When you then change the server editor with the renamed runtime, it will work correctly.

      Alternatively, you can rename the runtime from Preferences -> Server -> Runtime Environments. In this case you might not even realize that some servers will be affected and then you can hit the NPE again.

      Show
      1. Add a server runtime and server (e.g. use JBT runtime detection to add AS 7.1.1) 2. Double click the server in server view to open the server editor 3. Click Runtime Environment and change the runtime name, Finish 4. Right-click the server in server view - you will get a NPE in the log - FAIL When you then change the server editor with the renamed runtime, it will work correctly. Alternatively, you can rename the runtime from Preferences -> Server -> Runtime Environments. In this case you might not even realize that some servers will be affected and then you can hit the NPE again.

      When you rename a runtime but the server doesn't know about the change yet and you right-click on the server in server view, you will get a NPE.

      Perhaps the affected servers can be notified when the runtime is renamed and their runtime settings can be modified automatically? Or at least the error should be comprehensive and say what's wrong.

            rob.stryker Rob Stryker (Inactive)
            exd-mmalina Martin Malina
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: