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

add system property to allow explicit disabling of the visual page in VPE

    XMLWordPrintable

Details

    • Workaround Exists
    • Hide
      Under some operating systems, JBoss Developer Studio can crash when using the Visual Page Editor. This error occurs because of a conflict between WebKit and XULRunner. If you do notice this error occurring (current affected operating systems may include Fedora 64bit and Red Hat Enterprise Linux 64bit), you can add the workaround option -Dorg.jboss.tools.vpe.loadxulrunner=false to jbdevstudio.ini, that will disable XULRunner. When XULRunner is disabled, you will notice the message Could not open the Visual Page Editor: Embedded XULRunner is disabled by the option '-Dorg.jboss.tools.vpe.loadxulrunner=false' is displayed in the visual section of the Visual Page Editor. All other components of the JBoss Developer Studio will continue to work as expected.
      Show
      Under some operating systems, JBoss Developer Studio can crash when using the Visual Page Editor. This error occurs because of a conflict between WebKit and XULRunner. If you do notice this error occurring (current affected operating systems may include Fedora 64bit and Red Hat Enterprise Linux 64bit), you can add the workaround option -Dorg.jboss.tools.vpe.loadxulrunner=false to jbdevstudio.ini, that will disable XULRunner. When XULRunner is disabled, you will notice the message Could not open the Visual Page Editor: Embedded XULRunner is disabled by the option '-Dorg.jboss.tools.vpe.loadxulrunner=false' is displayed in the visual section of the Visual Page Editor. All other components of the JBoss Developer Studio will continue to work as expected.
    • Documented as Known Issue

    Description

      Since we keep having OS's where xulrunner is having problems we should inlcude a way to disable it loading even though we have xul binaries available for it.

      I suggest we look for system property: org.jboss.tools.vpe.loadvisualeditor if it is true (default) then we attempt to load the VPE as usual, but if false then we skip that page just as if the binaries were not available.

      that would allow you do to eclipse -Dorg.jboss.tools.vpe.loadvisualeditor=false

      Things to consider: if this property is set I guess xulrunner initializer should also not do anything ?

      Update:
      The property is named -Dorg.jboss.tools.vpe.loadxulrunner=false

      Attachments

        Issue Links

          Activity

            People

              yradtsevich Yahor Radtsevich (Inactive)
              manderse@redhat.com Max Andersen
              Isaac Rooskov Isaac Rooskov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: