Servlet is Not Requested After Initial Request

[Steve Dyke]

I have the following js that is called several places in my jsp files however the sevrlet only responds on the initial call.

js code

function progress(){
		alert("Calling Progress Bar!");
		$('#progressDisplay').load("/QMSWebApp/PleaseWaitServlet",showProgressDisplay);
		
	}
	function showProgressDisplay(){
		alert("Display Progress Bar!");
		//$('#progressDisplay').css({display: "block", left: "300px", top: "10px"});
		$('#progressDisplay').css({display: "block", 'z-index': '99'});
		
		
	}
                function hideProgressDisplay(){
		//$('#progressDisplay').css({display: "none", left: "-2500px", top: "10px"});
		$('#progressDisplay').css({display: "none", 'z-index': '0'});
				
	}

Servlet code

protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
		System.out.println("Do Get Called PleaseWaitServlet");
		this.doPost(request, response);
	}

	/* (non-Java-doc)
	 * @see javax.servlet.http.HttpServlet#doPost(HttpServletRequest arg0, HttpServletResponse arg1)
	 */
	protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
		
		response.setHeader( "Pragma", "no-cache" );
		response.setHeader( "Cache-Control", "no-cache" );
		response.setDateHeader( "Expires", 0 );
		
		System.out.println("Do Post Called PleaseWaitServlet");
		
		RequestDispatcher disp = getServletContext().getRequestDispatcher("/Layout/PleaseWait.jsp");
		disp.forward(request, response);
	}

[Bear Bibeault]

Have you used a debugger to determine if the load method is actually being called multiple times?

[Steve Dyke]

Bear Bibeault wrote:Have you used a debugger to determine if the load method is actually being called multiple times?

The alert message pops up every time it is just the load that does not fire but on the initial call. It is like the servlet gets cached but I thought the code I have in my servlet would prevent this.

[Bear Bibeault]

First, drop the alerts -- they are not a valid debugging mechanism. Open the JavaScript console and use console.log() to log to the console without interrupting the execution thread.

[Steve Dyke]

Bear Bibeault wrote:First, drop the alerts -- they are not a valid debugging mechanism. Open the JavaScript console and use console.log() to log to the console without interrupting the execution thread.

I am using WebSphere as my development environment. I run in the IE8 browser. Everything in my app run in div tags so the code is difficult to see runing. I have started the app, opened the Developer Tools in IE, clicked the Script option. Where do I go from there?

[Steve Dyke]

Bear Bibeault wrote:First, drop the alerts -- they are not a valid debugging mechanism. Open the JavaScript console and use console.log() to log to the console without interrupting the execution thread.

Never mind. Sorry but I found my mistake. After initialy loading the div tag which had a div tag embeded(every thing worked) I later reloaded the div tag but did not include embeded div tag that held the progress bar.

[Bear Bibeault]

But keep in mind the thing about alerts. Don't use them. They interrupt the execution thread and are a poor way to debug.

[Steve Dyke]

Bear Bibeault wrote:But keep in mind the thing about alerts. Don't use them. They interrupt the execution thread and are a poor way to debug.

Thanks, I still have so much to learn.