[ https://issues.jboss.org/browse/JBDS-1499?page=com.atlassian.jira.plugin.... ] Andrew Ross updated JBDS-1499: ------------------------------ Description: 3.2. Visual Editor doesn't start and "XPCOM error -2147467259" appears "This error shows that you have problems with your buildin XULRunner plugin.To resolve the issue,please: " "try xulrunner.exe -version or ./xulrunner -version command and you will see what is needed for XULRunner to work " COMMENT: How does finding the xulrunner version fix this problem? Is there a minimum version required? Version: JBoss_Developer_Studio-Migration_Guide-4.0-web-en-US-4.0.0-3.el5 was: 3.2. Visual Editor doesn't start and "XPCOM error -2147467259" appears "This error shows that you have problems with your buildin XULRunner plugin.To resolve the issue,please: " "try xulrunner.exe -version or ./xulrunner -version command and you will see what is needed for XULRunner to work " COMMENT: How does finding the xulrunner version fix this problem? Is there a minimum version? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-137?page=com.atlassian.jira.plug... ] Isaac Rooskov commented on TOOLSDOC-137: ---------------------------------------- I was unable to see where this text is: http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html-single/... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-137?page=com.atlassian.jira.plug... ] Isaac Rooskov resolved TOOLSDOC-137. ------------------------------------ Resolution: Done Thanks for that info Nick, I have found the text (commented out it seems) in the guide, and have updated it for future releases where customers may be migrating and see this issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-137?page=com.atlassian.jira.plug... ] Isaac Rooskov commented on TOOLSDOC-137: ---------------------------------------- There is no migration guide for 4.1, only for x.0 releases. for 4.y releases there is the update guide. So the migration guide is at: http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html-single/... But the migration guide has been updated for JBDS 5.0. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-137?page=com.atlassian.jira.plug... ] Len DiMaggio commented on TOOLSDOC-137: --------------------------------------- Isaac, where is this documented for the 3.3.0/5.0 users? I'm thinking that we need a simple, and consistent description of this error in the user docs and on https://devstudio.jboss.com/earlyaccess/ Maybe something like: {color:blue} The Visual Page Editor (VPE) does not run on 64-bit Windows or Mac platforms. While the source editor does work, visual editing & preview do not. The cause of the problem is that the x86 org.mozilla.xulrunner plugin is not present. The error message that you'll see in these situations looks like this: "Could not open the Visual Page Editor: Bundle org.mozilla.xulrunner.x86 is not found" To use the visual editing and preview features of the VPE on 64-bit Windows or Mac platforms, you have to use the 32-bit version of JBDS with a 32-bit JDK. {color} What do you think? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-137?page=com.atlassian.jira.plug... ] Len DiMaggio edited comment on TOOLSDOC-137 at 3/29/12 12:42 PM: ----------------------------------------------------------------- Isaac, where is this documented for the 3.3.0/5.0 users? I'm thinking that we need a simple, and consistent description of this error in the user docs and on https://devstudio.jboss.com/earlyaccess/ Maybe something like: {color:blue} The Visual Page Editor (VPE) does not run on 64-bit Windows or Mac platforms. While the source editor does work, visual editing & preview do not. The cause of the problem is that the x86 org.mozilla.xulrunner plugin is not present. The error message that you'll see in these situations looks like this: "Could not open the Visual Page Editor: Bundle org.mozilla.xulrunner.x86 is not found" or "Could not open the Visual Page Editor: Current platform is not supported" To use the visual editing and preview features of the VPE on 64-bit Windows or Mac platforms, you have to use the 32-bit version of JBDS with a 32-bit JDK. {color} What do you think? was (Author: ldimaggio): Isaac, where is this documented for the 3.3.0/5.0 users? I'm thinking that we need a simple, and consistent description of this error in the user docs and on https://devstudio.jboss.com/earlyaccess/ Maybe something like: {color:blue} The Visual Page Editor (VPE) does not run on 64-bit Windows or Mac platforms. While the source editor does work, visual editing & preview do not. The cause of the problem is that the x86 org.mozilla.xulrunner plugin is not present. The error message that you'll see in these situations looks like this: "Could not open the Visual Page Editor: Bundle org.mozilla.xulrunner.x86 is not found" or "Could not open the Visual Page Editor: Current platform is not supported" To use the visual editing and preview features of the VPE on 64-bit Windows or Mac platforms, you have to use the 32-bit version of JBDS with a 32-bit JDK. {color} What do you think? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-137?page=com.atlassian.jira.plug... ] Isaac Rooskov updated TOOLSDOC-137: ----------------------------------- Fix Version/s: Future (was: 3.3.0.Final) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira