]
Max Rydahl Andersen commented on JBIDE-2720:
--------------------------------------------
Since we don't control the actual eclipse binaries used i think there is very little
chance of us patching via dll injection or anything else for that matter. With respect to
getting intel or MS to fix their dll's I wouldn't even know where to start asking
for it - its not like they got a public jira to request such things ;)
btw. if your workflow is just around HTML (not jsf/xhtml) then you should be fine using
our html preview that does not rely on xulrunner. Have you tried that ?
Need 64-bit windows support
---------------------------
Key: JBIDE-2720
URL:
https://issues.jboss.org/browse/JBIDE-2720
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: visual-page-editor-core
Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
Reporter: Samuel Mendenhall
Assignee: Konstantin Marmalyukov
Fix For: 4.2.x
Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log,
buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt,
build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1,
mozconfig2, vpe-win-jdk64.png
If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
We should look into providing a xulrunner for Windows 64-bit.
*Update:*
In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is
provided via experimental update site:
http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
{color:red}*Known problems:*{color}
* XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
*If you get [R6034
error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...]
you may:*
* Try to uninstall Intel OpenCL SDK
* *OR* Disable XULRunner by adding the option
{{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or
{{jbdevstudio.ini}} if you use JBoss Developer Studio)
If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will
very appreciate if you run Process Explorer as described in [this
comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...]
and help us to find conflicting library.