I have an applet code. That i added to one of my web-application, when i click tab called Enrollment, applet will load and java console will open. it is happening.
And when i click other tab this java console has close. and again if i click Enrollment tab again new Java console has open.
How to do it please help me regarding this.
How to close java console in mac when page get navigates to other page.?
The console disappearing is subject to decisions by the JVM. Typically it will be left on-screen as long as the JVM runs, and that is significantly later than when the user navigates away from the page.
The console can be configured (by the user or their system administrator) to not show at all. Anything beyond visible/not visible is not open to our control and you should not worry about, it is just wasting time.
My website is made through java and Google web toolkit
When i click on button chrome sometimes becomes unresponsive and i have to kill the page ultimately.
It never happens on firefox and IE.
Is it some cache problem or plugin problem or something else.
I would firstly start looking at your server logs to verify that this is a client based problem rather than bad parameters.
Then verify that HTML/JS is correctly formed and has no errors.
Lastly I suggest to you to use Chrome Developer Tool (Right click) and to choose the profiling tab to collect JS CPU Profiling.
So as the title suggests, when launching my HTML suite with a custom firefox profile (also with multiwindow), the server is launching two tabs, both trying to execute the test, targetting the same single window the actions are being carried out in. If I close one of the selenium tabs, the test will then complete successfully.
The custom profile is a profile created in firefox 19.0.2 and I am now running it in 20.0
Now If I update up the custom profile to coincide with the latest version of firefox, this fixes the tab issue when launching the test...however my question is....
Does anybody know the cause of this behaviour?
Many thanks,
Joe
I think Firefox opens the second tab because the current milestone of the browser software does not match the value of the setting browser.startup.homepage_override.mstone in prefs.js: The browser tries to show sort of a successful-update-page in a new tab.
According to https://bugzilla.mozilla.org/show_bug.cgi?id=102313
you can suppress this behaviour by manually setting browser.startup.homepage_override.mstone to ignore. For me, this single change in prefs.js did the trick.
halfbit
I have 2 JApplet jars, jar A and jar B. Initially jar A is executed, it does some operations and downloads files to PC that B needs for its operations. When A is finished it executes B. The above works perfectly in the latest versions of Firefox and Safari, but not in IE9. In IE9
A is never shown executing in the browser, instead I get a blank screen for couple of seconds and I am forwarded to B. Also A doesn't perform its operations. Is there anything in IE9 I should be aware of, maybe a security feature or something that could be causing this?
Update:
I have just checked this in previous versions of IE and in those versions it works fine.
It may be related to the security settings or third-party software.
First option:
*Click on Tools, then Internet Options.
*Click on the Security tab at the top of the Internet Options window.
*Click on the Custom Level button.
*Scroll down the settings window, and near the bottom you will find an option labelled "Scripting of Java applets".
*Set this to "Enable".
*Click on okay.
Second option: some software like spybot search and blablablah can block unsigned applets. Check that out disabling complements (addins?).
OK, maybe I'm dumb/blind, but in the docs it says "rebuild and restart the server." But I don't see a button to do this anywhere. Or from any contextual menu. And I can't find anything in their docs explaining how to do it. If I just try to start the app again, it gets angry because I already have App Engine running on the needed port.
Only solution I've found is to restart Eclipse... any other ideas? A screenshot of a button would help if possible. :)
In eclipse, there is a view that contains your Console. If you click on that, you will see the STDOUT and STDERR output of your running application. In the upper right, there should be a red box that will terminate the currently running program.
I have a different and possibly more productive solution for you. Like with most web development environments you probably want to change your source code and have Google Appengine server reload the new code for you.
You need some version of the traditional "touch" unix command (if you work on windows you can download a version from here).
Then go to you project properties, Builders and add a new build step as a "Program". Under "Location" enter the path to your "touch" command ("D:\bin\UnxUtils\usr\local\wbin\touch.exe" for example - on Posix systems just "touch" should be enough since it's already in your PATH) and in "Arguments" put something like "${project_loc}/war/WEB-INF/appengine-web.xml".
Also go to the "Build Options" tab and check "During auto builds".
"touch" will update the timestamp in you appengine-web.xml. When the App Engine server detects changes to you appengine-web.xml it will reload the app automatically. The load process is very fast so it can be done whenever you change any file in your project (which normally triggers the auto-build in Eclipse) - you can tweak the builder to only run when you change certain types of files.
I might add that the "little red box" is not always visible. It drove me crazy reading that same instruction but not seeing the terminate button until I discovered that the Console windows has "layers" that you can select from using the drop-down button on the far right of the controls for the Console view. You just need to go "back" to the console screen that says the server is running and you will see the little red terminate button.
The previous answer wasn't cutting the cheese for me. Upon first starting App Engine, the red square would be available above the text entry area. If I then clicked the run button again, then red square would go away and the console for the previous launch would be replaced by the console for the new launch. To manually stop the App Engine server, you can kill it from the terminal:
http://geekbrigade.wordpress.com/2009/02/26/how-to-find-and-kill-a-process-that-is-using-a-particular-port-in-ubuntu/
In short, "sudo netstat -lpn |grep :8888" and kill the service by process ID.
Strangely, adding Google Web Toolkit to the project made my App Engine launch show up in the Development Mode pane, where it could be easily be killed or restarted.
Just Click on Debug perspective (should be on upper right panel), select the instance of web application on Debug panel (if you don't show it, you could enable by menu Window->show view->Debug) and click on red box of view menu.
The best I've found is to setup the keyboard shortcuts for the console's terminate button, and the run/debug start/restart command. By default, you can enable Command-F2 to terminate, and Command-F11 to restart, its fairly painless. Make sure to enable the full debug menu group (click on main toolbar -> customize, etc)
If you include the gwt SDK in your project, the gwt development mode box contains a reload server button that will work just fine.