I'm trying to load an applet using JNLP. Things work fine on every browser I've tested, except for Safari (tried on Safari 5.0.3 on OSX Snow Leopard).
This seems a Safari related bug, because even the JNLP applet used for testing in the plugin2 page on Oracle doesn't seem to be working, as Safari tries to load "Ignored.class" instead of looking at JNLP file.
Does anyone know a workaround for this issue?
Ok, so after a lot of tinkering, it seems that the reason for this behavior lies in the plugins installed on Safari (and Firefox 3.6, it seems).
Instead of working with the latest Java Plugin 2 NPAPI, it's using some older plugin. So the real fix is to remove that older plugin from Safari: Go to /Library/Internet Plug-ins and remove JavaPluginCocoa.bundle (also, remove it if you have it on ~/Library/Internet Plug-Ins).
This are the same directions described in this Apple Knowledge Base article, although for different reasons.
When you do this, Safari will use the new Java Plugin 2, and will work exactly as other browsers using the newer plugin (namely, Chrome or Firefox 4, unsure about Opera. For Firefox 3.6 you'll have to do a similar thing, but following the steps in this bug report)
Related
I've installed the GWT plugin in my Eclipse Luna. When I create a simple Web Application Project only for testing and using jre8, when running it and click on the link it shows this on browser, and if I change to jre7 it show this.
I've also found out here that "GWT Development Mode will no longer be available for Chrome sometime in 2014, so we improved alternate ways of debugging. There are improvements to Super Dev Mode, asserts, console logging, and error messages."
Can anyone tell me how to solve this errors if it is possible or what other ways of working with GWT are? Thank you
There are two different solutions you could take :
Downgrade to an older browser like Firefox 24.8.1esr which still supports the GWT Developer Plugin.
Use the Super Devmode, which can be easily accessed in the GWT 2.7 version in Eclipse. More information about the Super Dev Mode can be found here.
DevMode works fine on the latest esr version of Firefox 24, but I use Eclipse 3.7 with jre7_25. Here you can find a solution how to install GWT plugin in Chrome manually (regarding your 1st image).
On the 2nd image I see 404 error which means that the file is not there. Make sure the war path in your Run Configuration is correct (see Arguments tab). In my case I use -war to specify a location to war directory.
P.S. This information may be useful about DevMode.
I am trying to install the GWT Developer plugin for Chrome (Version 34.0.1847.131 m) and I get the following error "This application is not supported on this computer. Installation has been disabled. The following problems are detected:" and "NPAPI plugin is required by this app". Is there a way around this?
I have installed Microsoft Visual C++ 2008 SP1 Redistributable Package as suggested by one answer.
I am also trying to run in Explorer (version 11) and it requires me to download the GWT Developer plugin for Firefox. Which then requires content to be opened in a new window. I then elect to open "gwt-dev-plugin.xpi". When it finishes downloading it requests me to save it (if I open it it just download again). Is there a way around this?
I am running on Windows 8.1.
I am also trying to run in Explorer (version 11) and it requires me to download the GWT Developer plugin for Firefox.
To avoid that, open IE11 dev tools and under the "Emulation" menu change the "Document mode" from "Edge" to "10". The page should refresh and from there you should be able to install the GWT plugin for IE.
Once it's installed you can fall back to the "Edge" document mode.
Worked for me.
But as #apanizo said, I'd use the Super Dev Mode if possible. The dev mode is already not supported anymore in the latest firefox and it is going to be the same for the upcoming Chrome 35. No clue about IE though.
Enable the GWT Developer Plugin in Chrome.
Check for other plugin that is installed on Chrome.
Click on plugins for other systems to get more GWT Developer plugins.
Here is the URL for GWT missing-plugin.
Click on required GWT plugin and simply click on save button as shown below for IE9.
This might be useful for you:
Create shortcut Chrome to desktop.
Right click to shortcut and choose properties.
Click to Compatibility tab
Inside Compatibility mode check "Run this compatibility mode for:" and choose Window 7.
Apply and Ok.
Source: https://code.google.com/p/google-web-toolkit/issues/detail?id=7778
If you want to think Agile, here's what I adopted as a solution:
superDevMode is not practical, it takes forever to compile each time on my i7 with 8Gb of memory.
The solution I adopted is that I'm using FF for developement and I validate everything is fine only after GWT compiling on chrome (once in a while for the pauses).
Seriously I didn't see the point of having dev mode working on all browsers. In addition it runs curiously faster on FF than on Chrome (under windows). For Ubuntu (actually) I had to downgrade my FF to the version 24 to have it work (but since it's only a dev machine it doesn't bother me)
p.s: superDevMode might compile faster if optimized, hoestly I didn't try it: increasing the localWorkers could reduce compile time and make superDevMode a good solution, but I can't tell you; I didn't try that: http://mojo.codehaus.org/gwt-maven-plugin/compile-mojo.html#localWorkers
It seems file chooser dialogs are not working properly with SWT on Mac OSX 64-bit, with Oracle Java 7:
FileDialog dlg = new FileDialog(shell, SWT.OPEN);
dlg.open();
One major problem is that file previews (the right-most pane that appears when selecting a file) does not work: the spinner does not stop, CPU usage increases. Randomly, another issue is that folder contents appear empty.
Everything works fine with the official Apple Java 6 package. I tried several several versions of SWT (4.2.1, 4.2.2, 4.3, the beta 4.4 builds as well).
Is anybody aware of a workaround? Could this be fixed at the SWT level, or is it a Java 7 issue?
I came across this issue also.
It appears to be a direct combination of the following (Java 7, Eclipse 3.7.2, and OSX 10.9)
I found this explanation: https://bugs.eclipse.org/bugs/show_bug.cgi?id=420682 (Bug 420682 - In Indigo, Open File dialog only appears once in OS X Mavericks (10.9) )
I hope this helps you, but the basic message is as follows:
either upgrade to 4.x based RCP bundles, or at least 3.8.x
don't use Java 7 (I don;t recommend that one)
It seems the core of the issue is the -XstartOnFirstThread Java flag. One hack is to avoid using this flag, and implement the associated behavior (ie, starting SWT on the first thread) yourself.
Fortunately, a very helpful Eclipse contributor - Silenio Quarti - has done so, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=389486#c5.
Caveat: To be integrated in a non-Mac IDE, this source needs to be refactored, and all references to org.eclipse.swt.internal.** must be done through reflection.
Until Oracle and/or Apple fix the SDK version 7, this is the best and only workaround I've found thus far.
I created webdriver project with maven. Everything was fine, but one day my tests throw an exception while they running in Firefox. My Firefox version is 11 at this moment.
In my pom file i tried to change versions, but tests still don't work:
-Error communicating with the remote browser. It may have died.
Or
-Cannot perform native interaction: Could not load native events component.
Please, help with this issue.
I would recommend using Firefox 3.6, 9 or 10, because WebDrivers 2.19.0 and 2.20.0 (today's version) are not yet compatible with Firefox 11.
The official changelog says that version 2.19.0 enables native events in FF10. Also, the version 2.15.0 announces support for FF up to and including FF11. Seems that something got wrong there :). Downgrade to FF10 or similar and you should be good.
I upgraded to Selenium WebDriver 2.25.0 and my tests worked again.
I have just downloaded the Newest Google Chrome to test my gwt app... And, of course, in first gwt app running chrome demanded GWT plugin to be installed. So I did... All great but when gwt test app starts it doesn't work as in eclipse Design - Preview or IE8 etc. Instead of panels activation chrome shows me just a blank right frame :( Moreover, since then my FF 5.0 GWT dev plugin started do the same (blank) tricks as if it was replaced with the chrome one :( I think chrome caused all these things... I have already uninstalled chrome but my FF still tricks me with (blank) things... So my question is...
How to uninstall the Chrome GWT plugin totally to be able reinstall all from up to down and not to have GWT dev plugins conflict or something which maybe causes the headache?
My GWT version is 2.3
OS: Windows XP Pro SP3
IE8, FF 5.0.1 (Currently installed Internet Browsers)
All useful comments are appreciated
Might be far fetched, but have you checked that you're compiling against the correct user-agents in the module definition?
EDIT:
The module is the file ending with .gwt.xml and in that file you can specify which user agents to compile javascript for. In my module i'm having this line:
<set-property name="user.agent" value="ie6,ie8,gecko1_8,safari" />
It is quite strange but I have found that the Chrome GWT Dev plugin doesn't support two included SplitLayoutPanels :(
I mean the bound like a...
SplitLayoutPanel A which contains SplitLayoutPanel B
IE 7 supports this kind of code but Chrome and even FF don't :(
That caused the development problem. So I replaced the second SplitLayoutPanel B to HorizontalSplitPanel and finally that solved the problem :)
I hope that can save one's day :)