[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-11602 at 12/11/12 7:57 AM:
-----------------------------------------------------------------
Regarding the VJET...
In May of 2012 VJET project was proposed as open source project under the Eclipse Web Tools Platform Project (WTP). As the proposal was accepted it moved to http://eclipse.org/vjet/ in late November.
Advantages:
- It works. It needs just to add its compability to a project to be able to use VJET JavaScript editor, Content Assist and so on.
- Provides [Content Assists| https://www.ebayopensource.org/wiki/display/VJET/Code+Assistance+Features], [Code Search, Syntax and Semantic Checking for JavaScipts|https://www.ebayopensource.org/wiki/display/VJET/Code+Search+F...].
- Provides Type Declarations using VJETDoc (form of JavaScript comment syntax used to add type information to JavaScript source code.
- Provides Execution/Debugging facilities.
- It's integrated into WTP HTML Editor (this means that it's already integrated into JBoss Tools HTML Editor as well)
- It's an Open Source Project under the [Eclipse Web Tools Platform Project (WTP)|http://eclipse.org/vjet/] and it's alive (opposite to JSDT)
- Since it was introduced it became more reliable and stable.
Disadvantages:
- Slowness. It makes Eclipse (and JBT/JBDS) to work significantly slower. The reason is VJET has to compile JavaScripts, build Type info and dependency models as well as to perform Syntax and Semantic checking on the fly.
- Generates too much debug output (but probably it will gone after some tine)
- It still requires to add its capabilities to a project (not a big problem)
- It doesn't solve the Minified jQuery problems as well as some other validation problems even it tries to replace JSDT validation with the own one (I may be mistaken, but I guess it disabled the JSDT Validation when enabled). But I'm sure VJET validation is significantly better that the JSDT one.
- It doesn't solve WTP HTML problems (like that is described in https://issues.jboss.org/browse/JBIDE-3728 Invalid Javascript error - an old Upstream issue (WTP 3.0.3) that still is reproducible today)
Related JSDT [issues list|https://issues.jboss.org/issues/?jql=labels%20in%20(jsdt%2C%20vjet)].
Note: It requires a newer Orbit version than we're using in latest JBDS 6.0/JBT 4.0 Target Platforms.
was (Author: vrubezhny):
Regarding the VJET...
In May of 2012 VJET project was proposed as open source project under the Eclipse Web Tools Platform Project (WTP). As the proposal was accepted it moved to http://eclipse.org/vjet/ in late November.
Advantages:
- It works. It needs just to add its compability to a project to be able to use VJET JavaScript editor, Content Assist and so on.
- Provides Content Assistance, Code Search, Syntax and Semantic Checking for JavaScipts.
- Provides Type Declarations using VJETDoc (form of JavaScript comment syntax used to add type information to JavaScript source code.
- Provides Execution/Debugging facilities.
- It's integrated into WTP HTML Editor (this means that it's already integrated into JBoss Tools HTML Editor as well)
- It's an Open Source Project under the Eclipse Web Tools Platform Project (WTP) and it's alive (opposite to JSDT)
- Since it was introduced it became more reliable and stable.
Disadvantages:
- Slowness. It makes Eclipse (and JBT/JBDS) to work significantly slower. The reason is VJET has to compile JavaScripts, build Type info and dependency models as well as to perform Syntax and Semantic checking on the fly.
- Generates too much debug output (but probably it will gone after some tine)
- It still requires to add its capabilities to a project (not a big problem)
- It doesn't solve the Minified jQuery problems as well as some other validation problems even it tries to replace JSDT validation with the own one (I may be mistaken, but I guess it disabled the JSDT Validation when enabled). But I'm sure VJET validation is significantly better that the JSDT one.
- It doesn't solve WTP HTML problems (like that is described in https://issues.jboss.org/browse/JBIDE-3728 Invalid Javascript error - an old Upstream issue (WTP 3.0.3) that still is reproducible today)
Related JSDT [issues list|https://issues.jboss.org/issues/?jql=labels%20in%20(jsdt%2C%20vjet)].
Note: It requires a newer Orbit version than we're using in latest JBDS 6.0/JBT 4.0 Target Platforms.
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Labels: jsdt, vjet
> Fix For: 4.1.x
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-11602 at 12/11/12 7:46 AM:
-----------------------------------------------------------------
Regarding JSDT (http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg08504.html)
In short: it's more dead than alive, but...
Tonight some discussion have taken a continuation at wtp-dev(a)eclipse.org mailing list.
There is an alternate variant have being developed by John Peberdy <john(a)peberdy.ca>. In short, for the Type Resolution he used "NJSDoc as the data source" which "works by executing code in a modified Rhino runtime and analyzing the resulting structure".
He proposes that his JSDT clone is slightly effective and doesn't require to many resources (such as memory and CPU) for the Type Resolution. Also he plans to:
{quote}
Use JSDoc comments to hint types
Add ability to manually hint the type of a local variable (an example of this in Scheme is here [2])
Built in support for AMD spec and maybe CommonJS modules
Improve performance, eliminate more JDT specific code
{quote}
And finally, he hopes to merge its JSDT clone back to WTP.
It seems this project is interresting for the Eclipse Source Editing and JSDT team:
{quote}
John,
We're looking forward to seeing how well it all works. I'm particularly
interested in how/where/if those manual hints are stored between editor
sessions.
Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing and JSDT
IBM Rational
{quote}
So, some movement may come with JSDT not so far.
was (Author: vrubezhny):
Regarding JSDT.
In short: it's more dead than alive, but...
Tonight some discussion have taken a continuation at wtp-dev(a)eclipse.org mailing list.
There is an alternate variant have being developed by John Peberdy <john(a)peberdy.ca>. In short, for the Type Resolution he used "NJSDoc as the data source" which "works by executing code in a modified Rhino runtime and analyzing the resulting structure".
He proposes that his JSDT clone is slightly effective and doesn't require to many resources (such as memory and CPU) for the Type Resolution. Also he plans to:
{quote}
Use JSDoc comments to hint types
Add ability to manually hint the type of a local variable (an example of this in Scheme is here [2])
Built in support for AMD spec and maybe CommonJS modules
Improve performance, eliminate more JDT specific code
{quote}
And finally, he hopes to merge its JSDT clone back to WTP.
It seems this project is interresting for the Eclipse Source Editing and JSDT team:
{quote}
John,
We're looking forward to seeing how well it all works. I'm particularly
interested in how/where/if those manual hints are stored between editor
sessions.
Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing and JSDT
IBM Rational
{quote}
So, some movement may come with JSDT not so far.
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Labels: jsdt, vjet
> Fix For: 4.1.x
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13272) When using JBDS 6, authentication to a Load Balanced broker fails
by Scott Collier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13272?page=com.atlassian.jira.plugi... ]
Scott Collier updated JBIDE-13272:
----------------------------------
Summary: When using JBDS 6, authentication to a Load Balanced broker fails (was: When using JBDS 6 authentication to a Load Balanced broker fails)
> When using JBDS 6, authentication to a Load Balanced broker fails
> -----------------------------------------------------------------
>
> Key: JBIDE-13272
> URL: https://issues.jboss.org/browse/JBIDE-13272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: LATER
> Environment: 2 Red Hat Linux 6.3 Load balancer (piranha) add-on systems set up in direct routing mode with a virtual server sending traffic to two brokers (real servers). Brokers are running OpenShift Enterprise 1.0. The brokers are set up to do authentication via LDAP (Windows 2008 R2 Active Directory).
> Reporter: Scott Collier
> Assignee: Andre Dietisheim
>
> When using jbds 6, Authenticating to a load balanced broker (VIP) does not work. It worked in JBDS 5.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-11602 at 12/11/12 7:40 AM:
-----------------------------------------------------------------
Regarding the VJET...
In May of 2012 VJET project was proposed as open source project under the Eclipse Web Tools Platform Project (WTP). As the proposal was accepted it moved to http://eclipse.org/vjet/ in late November.
Advantages:
- It works. It needs just to add its compability to a project to be able to use VJET JavaScript editor, Content Assist and so on.
- Provides Content Assistance, Code Search, Syntax and Semantic Checking for JavaScipts.
- Provides Type Declarations using VJETDoc (form of JavaScript comment syntax used to add type information to JavaScript source code.
- Provides Execution/Debugging facilities.
- It's integrated into WTP HTML Editor (this means that it's already integrated into JBoss Tools HTML Editor as well)
- It's an Open Source Project under the Eclipse Web Tools Platform Project (WTP) and it's alive (opposite to JSDT)
- Since it was introduced it became more reliable and stable.
Disadvantages:
- Slowness. It makes Eclipse (and JBT/JBDS) to work significantly slower. The reason is VJET has to compile JavaScripts, build Type info and dependency models as well as to perform Syntax and Semantic checking on the fly.
- Generates too much debug output (but probably it will gone after some tine)
- It still requires to add its capabilities to a project (not a big problem)
- It doesn't solve the Minified jQuery problems as well as some other validation problems even it tries to replace JSDT validation with the own one (I may be mistaken, but I guess it disabled the JSDT Validation when enabled). But I'm sure VJET validation is significantly better that the JSDT one.
- It doesn't solve WTP HTML problems (like that is described in https://issues.jboss.org/browse/JBIDE-3728 Invalid Javascript error - an old Upstream issue (WTP 3.0.3) that still is reproducible today)
Related JSDT [issues list|https://issues.jboss.org/issues/?jql=labels%20in%20(jsdt%2C%20vjet)].
Note: It requires a newer Orbit version than we're using in latest JBDS 6.0/JBT 4.0 Target Platforms.
was (Author: vrubezhny):
Regarding the VJET...
In May of 2012 VJET project was proposed as open source project under the Eclipse Web Tools Platform Project (WTP). As the proposal was accepted it moved to http://eclipse.org/vjet/ in late November.
Advantages:
- It works. It needs just to add its compability to a project to be able to use VJET JavaScript editor, Content Assist and so on.
- Provides Content Assistance, Code Search, Syntax and Semantic Checking for JavaScipts.
- Provides Type Declarations using VJETDoc (form of JavaScript comment syntax used to add type information to JavaScript source code.
- Provides Execution/Debugging facilities.
- It's integrated into WTP HTML Editor (this means that it's already integrated into JBoss Tools HTML Editor as well)
- It's an Open Source Project under the Eclipse Web Tools Platform Project (WTP) and it's alive (opposite to JSDT)
- Since it was introduced it became more reliable and stable.
Disadvantages:
- Slowness. It makes Eclipse (and JBT/JBDS) to work significantly slower. The reason is VJET has to compile JavaScripts, build Type info and dependency models as well as to perform Syntax and Semantic checking on the fly.
- Generates too much debug output (but probably it will gone after some tine)
- It still requires to add its capabilities to a project (not a big problem)
- It doesn't solve the Minified jQuery problems as well as some other validation problems even it tries to replace JSDT validation with the own one (I may be mistaken, but I guess it disabled the JSDT Validation when enabled). But I'm sure VJET validation is significantly better that the JSDT one.
- It doesn't solve WTP HTML problems (like that is described in https://issues.jboss.org/browse/JBIDE-3728 Invalid Javascript error - an old Upstream issue (WTP 3.0.3) that still is reproducible today)
Note: It requires a newer Orbit version than we're using in latest JBDS 6.0/JBT 4.0 Target Platforms.
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Labels: jsdt, vjet
> Fix For: 4.1.x
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13272) When using JBDS 6 authentication to a Load Balanced broker fails
by Scott Collier (JIRA)
Scott Collier created JBIDE-13272:
-------------------------------------
Summary: When using JBDS 6 authentication to a Load Balanced broker fails
Key: JBIDE-13272
URL: https://issues.jboss.org/browse/JBIDE-13272
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: LATER
Environment: 2 Red Hat Linux 6.3 Load balancer (piranha) add-on systems set up in direct routing mode with a virtual server sending traffic to two brokers (real servers). Brokers are running OpenShift Enterprise 1.0. The brokers are set up to do authentication via LDAP (Windows 2008 R2 Active Directory).
Reporter: Scott Collier
Assignee: Andre Dietisheim
When using jbds 6, Authenticating to a load balanced broker (VIP) does not work. It worked in JBDS 5.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBDS-2430) Path to java hardcoded in JBDS
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-2430?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-2430:
---------------------------------
Assignee: Denis Golovin
> Path to java hardcoded in JBDS
> ------------------------------
>
> Key: JBDS-2430
> URL: https://issues.jboss.org/browse/JBDS-2430
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.CR1, 6.0.0.GA
> Reporter: Robert Balent
> Assignee: Denis Golovin
>
> After installation of JBDS, it doesn't use java specified in $JAVA_HOME or in $PATH but tries to run with java hardcoded in JBDS configuration file.
> Problem occurs and JBDS don't even start in situation that you want to run JBDS with different java (in different directory) than was present at installation time.
> It would be the best to use java specified in $JAVA_HOME or present on $PATH and avoid this problem.
> Workaround:
> 1. Install java to the same directory as the previous java
> or
> 2. Manually edit jbdevstudio.ini and change path to the java
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBDS-2430) Path to java hardcoded in JBDS
by Robert Balent (JIRA)
Robert Balent created JBDS-2430:
-----------------------------------
Summary: Path to java hardcoded in JBDS
Key: JBDS-2430
URL: https://issues.jboss.org/browse/JBDS-2430
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.CR1, 6.0.0.GA
Reporter: Robert Balent
After installation of JBDS, it doesn't use java specified in $JAVA_HOME or in $PATH but tries to run with java hardcoded in JBDS configuration file.
Problem occurs and JBDS don't even start in situation that you want to run JBDS with different java (in different directory) than was present at installation time.
It would be the best to use java specified in $JAVA_HOME or present on $PATH and avoid this problem.
Workaround:
1. Install java to the same directory as the previous java
or
2. Manually edit jbdevstudio.ini and change path to the java
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13271) BrowserSim: simulator is closing unexpectedly while changing skin
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13271?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich updated JBIDE-13271:
-------------------------------------
Description:
On some web pages BrowserSim is closing with the following stack trace while changing skin (see steps to reproduce):
{code}
Exception in thread "main" org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4361)
at org.eclipse.swt.SWT.error(SWT.java:4276)
at org.eclipse.swt.SWT.error(SWT.java:4247)
at org.eclipse.swt.widgets.Widget.error(Widget.java:468)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340)
at org.eclipse.swt.widgets.Control.setVisible(Control.java:3725)
at org.jboss.tools.vpe.browsersim.ui.skin.ios.AppleIPhone3ResizableSkin.
progressChanged(AppleIPhone3ResizableSkin.java:247)
at org.jboss.tools.vpe.browsersim.ui.BrowserSim$3.changed(BrowserSim.jav
a:251)
at org.eclipse.swt.browser.WebResourceLoadDelegate.identifierForInitialR
equest(WebResourceLoadDelegate.java:225)
at org.eclipse.swt.browser.WebResourceLoadDelegate$1.method3(WebResource
LoadDelegate.java:45)
at org.eclipse.swt.internal.ole.win32.COMObject.callback3(COMObject.java
:92)
at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:650)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2822)
at org.eclipse.swt.widgets.Widget.wmSetFocus(Widget.java:2417)
at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:5152)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4598)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
at org.eclipse.swt.internal.win32.OS.VtblCall(Native Method)
at org.eclipse.swt.internal.webkit.IWebView.setHostWindow(IWebView.java:
76)
at org.eclipse.swt.browser.WebKit.onDispose(WebKit.java:1064)
at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:646)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
at org.eclipse.swt.widgets.Widget.release(Widget.java:808)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:167)
at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java:
790)
at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:1290)
at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
at org.eclipse.swt.widgets.Widget.dispose(Widget.java:446)
at org.eclipse.swt.widgets.Decorations.dispose(Decorations.java:448)
at org.eclipse.swt.widgets.Shell.dispose(Shell.java:715)
at org.jboss.tools.vpe.browsersim.ui.BrowserSim.setSelectedDevice(Browse
rSim.java:673)
at org.jboss.tools.vpe.browsersim.ui.BrowserSim$11$1.update(BrowserSim.j
ava:433)
at java.util.Observable.notifyObservers(Unknown Source)
at java.util.Observable.notifyObservers(Unknown Source)
at org.jboss.tools.vpe.browsersim.ui.BrowserSim$22.widgetSelected(Browse
rSim.java:651)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:
248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
at org.jboss.tools.vpe.browsersim.ui.BrowserSim.main(BrowserSim.java:156
)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.swtjar.SWTLoader.main(SWTLoader.java:38)
{code}
was:
BrowserSim is closing with the following stack trace:
{code}
Exception in thread "main" org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4361)
at org.eclipse.swt.SWT.error(SWT.java:4276)
at org.eclipse.swt.SWT.error(SWT.java:4247)
at org.eclipse.swt.widgets.Widget.error(Widget.java:468)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340)
at org.eclipse.swt.widgets.Control.setVisible(Control.java:3725)
at org.jboss.tools.vpe.browsersim.ui.skin.ios.AppleIPhone3ResizableSkin.
progressChanged(AppleIPhone3ResizableSkin.java:247)
at org.jboss.tools.vpe.browsersim.ui.BrowserSim$3.changed(BrowserSim.jav
a:251)
at org.eclipse.swt.browser.WebResourceLoadDelegate.identifierForInitialR
equest(WebResourceLoadDelegate.java:225)
at org.eclipse.swt.browser.WebResourceLoadDelegate$1.method3(WebResource
LoadDelegate.java:45)
at org.eclipse.swt.internal.ole.win32.COMObject.callback3(COMObject.java
:92)
at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:650)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2822)
at org.eclipse.swt.widgets.Widget.wmSetFocus(Widget.java:2417)
at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:5152)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4598)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
at org.eclipse.swt.internal.win32.OS.VtblCall(Native Method)
at org.eclipse.swt.internal.webkit.IWebView.setHostWindow(IWebView.java:
76)
at org.eclipse.swt.browser.WebKit.onDispose(WebKit.java:1064)
at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:646)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
at org.eclipse.swt.widgets.Widget.release(Widget.java:808)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:167)
at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java:
790)
at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:1290)
at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
at org.eclipse.swt.widgets.Widget.dispose(Widget.java:446)
at org.eclipse.swt.widgets.Decorations.dispose(Decorations.java:448)
at org.eclipse.swt.widgets.Shell.dispose(Shell.java:715)
at org.jboss.tools.vpe.browsersim.ui.BrowserSim.setSelectedDevice(Browse
rSim.java:673)
at org.jboss.tools.vpe.browsersim.ui.BrowserSim$11$1.update(BrowserSim.j
ava:433)
at java.util.Observable.notifyObservers(Unknown Source)
at java.util.Observable.notifyObservers(Unknown Source)
at org.jboss.tools.vpe.browsersim.ui.BrowserSim$22.widgetSelected(Browse
rSim.java:651)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:
248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
at org.jboss.tools.vpe.browsersim.ui.BrowserSim.main(BrowserSim.java:156
)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.swtjar.SWTLoader.main(SWTLoader.java:38)
{code}
> BrowserSim: simulator is closing unexpectedly while changing skin
> -----------------------------------------------------------------
>
> Key: JBIDE-13271
> URL: https://issues.jboss.org/browse/JBIDE-13271
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.0.0.CR1
> Environment: Windows 7
> Reporter: Yahor Radtsevich
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.0.1, 4.1.0.Alpha1
>
>
> On some web pages BrowserSim is closing with the following stack trace while changing skin (see steps to reproduce):
> {code}
> Exception in thread "main" org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4361)
> at org.eclipse.swt.SWT.error(SWT.java:4276)
> at org.eclipse.swt.SWT.error(SWT.java:4247)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:468)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340)
> at org.eclipse.swt.widgets.Control.setVisible(Control.java:3725)
> at org.jboss.tools.vpe.browsersim.ui.skin.ios.AppleIPhone3ResizableSkin.
> progressChanged(AppleIPhone3ResizableSkin.java:247)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim$3.changed(BrowserSim.jav
> a:251)
> at org.eclipse.swt.browser.WebResourceLoadDelegate.identifierForInitialR
> equest(WebResourceLoadDelegate.java:225)
> at org.eclipse.swt.browser.WebResourceLoadDelegate$1.method3(WebResource
> LoadDelegate.java:45)
> at org.eclipse.swt.internal.ole.win32.COMObject.callback3(COMObject.java
> :92)
> at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
> at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:650)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
> at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2822)
> at org.eclipse.swt.widgets.Widget.wmSetFocus(Widget.java:2417)
> at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:5152)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:4598)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
> at org.eclipse.swt.internal.win32.OS.VtblCall(Native Method)
> at org.eclipse.swt.internal.webkit.IWebView.setHostWindow(IWebView.java:
> 76)
> at org.eclipse.swt.browser.WebKit.onDispose(WebKit.java:1064)
> at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:646)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:808)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:167)
> at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java:
> 790)
> at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:1290)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:446)
> at org.eclipse.swt.widgets.Decorations.dispose(Decorations.java:448)
> at org.eclipse.swt.widgets.Shell.dispose(Shell.java:715)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim.setSelectedDevice(Browse
> rSim.java:673)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim$11$1.update(BrowserSim.j
> ava:433)
> at java.util.Observable.notifyObservers(Unknown Source)
> at java.util.Observable.notifyObservers(Unknown Source)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim$22.widgetSelected(Browse
> rSim.java:651)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:
> 248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim.main(BrowserSim.java:156
> )
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.swtjar.SWTLoader.main(SWTLoader.java:38)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months