Reproduce bug#: 149933

STEPS TO REPRODUCE BUG#: 149933
Description: "Remember my decision" doesn't work for "Disable breakpoints" option in Run On Server dialog


1. Make sure the Java EE perspective is opened.


2. Add a new Tomcat server


3. Create a new Dynamic Project


4. Add a new JSP file


5. Add this line: <% out.println("Hello."); %> to the JSP and set a break point beside it


6. Start Server in Debug mode


7. Right-click on the JSP file and select "Run On Server"


8. Click Finish on the Run On Server Dialog


9. Select option: Disable Breakpoints and Continue and check on Remember my decision


10. Repeat step 7 and 8


RESULT:
The Run On Server Dialog appears again which is not expected since already checked on "Remember My Decision"




=> Expecting the JSP run with breakpoints disables

Reproducing Bug#: 244862

Follow up with Tehereh's discoveries, the bug is reproduced successfully:

CASE 1: Deleting a server project doesn't call stop server

Step1: Create a server project





Step2: Start the server



Step3: Delete the server project



Step4: Create a new server project (Repeat step 1)


Step5: Start the new server



Step6: BUG OCCURS



CONCLUSION:
Deleting a server project should call stop server.

CASE 2: Closing a server project doesn't call stop server

Step 1: Create a new server project
(please check CASE1:step1)

Step 2: Start the server
(please check CASE1:step2)

Step 3: Close the server project



Step 4: Create a new server project
(please check CASE1:Step1

Step 5: Start the new server



Step 6: BUG OCCURS




CONCLUSION:
Closing a server project should call stop server

Dropping bug# 236976

After my presentation last week, it seems that there are different opinions of what is the best way to fix this bug. As this bug involve with the presentation (interface), it would be difficult to change (fix) it without curtain surveys from users and it would take a lot more time to do survey than fixing the bug itself.

I'll look for another bug and will keep working on Tehereh'bug as the same time.

Bug#236976: UI improvement for Server Editor Page

Reproduce:
UI for timeouts could be improved.
The current timeout GUI on the server editor allows the user to input the
timeout in seconds. It has a hover help to translate the value to mins and
seconds. However, most user will not notice and do not expect that hover help
function to show that.

A minor UI improvement is to show text box for seconds, and auto translate and
display min:sec as a text on the label for the timeout text field.

NEW UI PROPOSAL:

BEFORE:


AFTER:

Bug 264203 is fixed by Larry Issacs

Larry posted his patch on bug zilla. I tested his patch and the bug is fixed. Although, he mentioned that he hasn't tested the patch on "publish after servers" scenarios and I'm not sure what does that term means to test it for him. Anyway, I posted a question regarding "publish after server" on newsgroup and will test these scenarios when I got a chance. Let hunt for another bug then.

Detail on patch: https://bugs.eclipse.org/bugs/attachment.cgi?id=132132

Working on bug 264203

Thanks to Tehereh, After reading her blog I tried again and this bug does exist. Though, the way to reproduce is clearer now: So the scenario is like this:

1. Add new server (Stop state)
2. Add a dynamic web app.
3. Add a jsp file.
4. right-click on jsp and choose “Run on server”.
5. Server starts.
6. Browser get launched
==> NO BUG

7. Stop the server and close the browser
8. right-click on the jsp and choose “Run on server” again
9. Browser doesn’t get launched.
==> BUG

——————————————-
10. Delete server
11. Add new server (Stop state)
12. right-click on jsp file and choose “Run on server” again
13. Browser get launched
==> NO BUG

So basically, After the first time "Run on Server" with no bug. If we stop the server and try to "Run On Server" again. The bug occurs.

I'll be working on this bug then.

Screenshots:
First time "RUN ON SERVER" => NO BUG



The time after the first time "RUN ON SERVER" => BUG

Reproduce Bug 264203

Bug 264203:
Steps To Reproduce from BugZilla:
1. Create a server (I tried tomcat 5.5 and the j2ee preview server)
2. Add a simple JSP file to the webcontent folder of a dynamic web project
3. Add the web project to the server.
4. Make sure the server is stopped
5. Right click on the JSP and select "run on server"
6. The server starts, but the web browser does not get launched.


MY REPRODUCE :
1. Create a server (I tried with both Tomcat 5.5 and 6.0)
2. Add Web Project
3. Add JSP file
4. Run on Server
5. Server starts, web browser get launched => No bug

Conclusion:
This bug is fixed for lastest build 3.1M6. I tried with both Tomcat 5.5 and 6.0. Notify and confirm this on Bugzilla

Some screenshots for reproduce steps: