Difference between revisions of "WTP-bug227760"
(→Project News) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
[http://zenit.senecac.on.ca/wiki/index.php/User:Lyang42 Le Yang] | [http://zenit.senecac.on.ca/wiki/index.php/User:Lyang42 Le Yang] | ||
| + | |||
[http://zenit.senecac.on.ca/wiki/index.php/User:Khanh.Vu Khanh Vu] | [http://zenit.senecac.on.ca/wiki/index.php/User:Khanh.Vu Khanh Vu] | ||
| + | |||
| + | [http://zenit.senecac.on.ca/wiki/index.php/User:Pliu Peter Liu] | ||
== Project Details == | == Project Details == | ||
| Line 22: | Line 25: | ||
== Project News == | == Project News == | ||
| − | Originally, trying to link these two very different packages, was difficult. However, Le Yang created a solution for a very similar blog, which was detailed [http://wb-os.blogspot.com/2009/04/fixed-bug-240698-part-i.html here]. The method being called in the "StartAction.java" class is being replicated in the pre-launch class when start a server. This is the reason why the dialogue is prompted twice. Following the proposed solution seems to work the same for this bug. | + | Originally, trying to link these two very different packages, was difficult. However, Le Yang created a solution for a very similar blog, which was detailed [http://wb-os.blogspot.com/2009/04/fixed-bug-240698-part-i.html here]. The method being called in the "StartAction.java" class is being replicated in the pre-launch class when start a server. This is the reason why the dialogue is prompted twice. Following the proposed solution seems to work the same for this bug.The solution included removal a saveResource method, which was not required, since this is called by a different method later. The removal of this code should not affect anything else since the code that is being called upon only relates to saving open editors. There is no other particular importance of this code. Another condition was added "getLaunch().getSourceLocator() != null" in the startImpl method in the Server.java class, as this was able to catch the exception thrown when the cancel option was selected. |
| + | |||
| + | A fix & patch was created. More details on blog: [http://opensourceproject.wordpress.com/ http://opensourceproject.wordpress.com] | ||
Latest revision as of 11:17, 9 April 2009
Contents
Project Name
Eclipse Bug #227760.
Project Description
Eclipse Bug #227760 is a normal classification bug, that deals with WTP Server tools. The basic problem of the bug, is that the save dialogue is replication twice when a user clicks "No", when starting a server. Basically, if someone tries to start a server in eclipse, and there is an unsaved file in the work area, it prompts the user to save the file before running the server. If the user selects either "yes" or "cancel", normal behaviour occurs, but if the user selects "no", the exact save dialogue is repeated. If the user selects "no" again the second time, then normal behaviour resumes.
Project Leader(s)
Project Contributor(s)
Project Details
The save resource dialogue is called upon twice: once in the StartAction.java file in the "org.eclipse.wst.server.ui.internal.view.servers” package, and in the SaveScopeResourceHandler.java file in the "org.eclipse.debug.internal.ui" package. For more details on these, please check out the blog regarding this bug.
Project News
Originally, trying to link these two very different packages, was difficult. However, Le Yang created a solution for a very similar blog, which was detailed here. The method being called in the "StartAction.java" class is being replicated in the pre-launch class when start a server. This is the reason why the dialogue is prompted twice. Following the proposed solution seems to work the same for this bug.The solution included removal a saveResource method, which was not required, since this is called by a different method later. The removal of this code should not affect anything else since the code that is being called upon only relates to saving open editors. There is no other particular importance of this code. Another condition was added "getLaunch().getSourceLocator() != null" in the startImpl method in the Server.java class, as this was able to catch the exception thrown when the cancel option was selected.
A fix & patch was created. More details on blog: http://opensourceproject.wordpress.com
