This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 322559 - Widget is disposed on Run On Server
Summary: Widget is disposed on Run On Server
Status: CLOSED WORKSFORME
Alias: None
Product: WTP ServerTools
Classification: WebTools
Component: wst.server (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows Vista
: P4 minor (vote)
Target Milestone: ---   Edit
Assignee: Angel Vera CLA
QA Contact: Angel Vera CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-12 13:02 EDT by Kaloyan Raev CLA
Modified: 2011-02-17 14:14 EST (History)
0 users

See Also:

Attachments
exception (4.21 KB, text/plain)
2010-08-12 13:02 EDT, Kaloyan Raev CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kaloyan Raev CLA 2010-08-12 13:02:54 EDT 
Created attachment 176484 [details]
exception

I got a "Widget is disposed" error dialog pop up when executing the Run On Server action. 

See attached the log I found in the Error Log. 

This is in WTP 3.2.2. It is hard to reproduce and does not do any functional harm.
Comment 1 Angel Vera CLA 2011-02-16 14:06:16 EST 
is there more information that you can give me in terms of how to recreate the problem? It sounds that you have seen this problem a few times, but it is hard to recreate. Can you provide some steps or more information as to precisely when the error happens? 

When you say that it didn't have any functional problem, I assume that you were able to continue with the wizard buttons and selecting the server were you wanted to run your artifact.
Comment 2 Kaloyan Raev CLA 2011-02-17 11:20:35 EST 
Angel, to be honest, I saw this only once. I don't remember the exact steps to reproduce: after working with the IDE, I've just seen it logged in the Error Log. 

I haven't seen error since then. 

I submitted this bug just as a hint for you - just in case the stack trace can point something obvious in the source code. 

If it is not possible to do anything more on this bug, it's OK for me to close it as not reproducible.
Comment 3 Kaloyan Raev CLA 2011-02-17 11:21:47 EST 
And yes, I didn't observe any functional problem - everything went fine, it was just the exception logged.
Comment 4 Angel Vera CLA 2011-02-17 14:14:48 EST 
Kaloyan, Thanks for the info and the report. I did looked at the code but didn't see anything obvious that could be fixed. I will close it for now and revisit if other similars things come along.