Case
i'm trying to write a GWTTestCase for a certain class, used as a presenter for a history-browsing toolbar component i'm building.
Problem
one (or more) of the scripts apparently not being loaded for the jUnit testing environment. it all works fine when running the application (development mode), but when i try to run the test case, the application (web server as well as user agent) fails to load, and the following exception arouses (stacktrace is shortened for simplicity):
com.gargoylesoftware.htmlunit.ScriptException: Wrapped com.gargoylesoftware.htmlunit.ScriptException: Exception invoking jsxFunction_write at com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$HtmlUnitContextAction.run(JavaScriptEngine.java:601) at net.sourceforge.htmlunit.corejs.javascript.Context.call(Context.java:537) at net.sourceforge.htmlunit.corejs.javascript.ContextFactory.call(ContextFactory.java:538) at com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine.execute(JavaScriptEngine.java:499) at com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$HtmlUnitContextAction.run(JavaScriptEngine.java:595) ... 41 more
...
Caused by: com.gargoylesoftware.htmlunit.ScriptException: Wrapped com.gargoylesoftware.htmlunit.ScriptException: ReferenceError: "Raphael" is not defined. (http://192.168.10.32:3692/com.gigaspaces.admin.webui.Gs_webui.JUnit/dracula/dracula_graffle.js#18) (http://192.168.10.32:3692/com.gigaspaces.admin.webui.Gs_webui.JUnit/com.gigaspaces.admin.webui.Gs_webui.JUnit.nocache.js#16) at com.gargoylesoftware.htmlunit.javascript.JavaScriptEngine$HtmlUnitContextAction.run(JavaScriptEngine.java:601)
Relevant sources
here is the (ridiculously simple) GWTTestCase used:
public class HistoryBrowserTest extends GWTTestCase {
#Override
public String getModuleName() {
return "com.gigaspaces.admin.webui.Gs_webui";
}
public void testHistoryBrowser() {
assertTrue(true);
}
}
Dependencies / context information
jUnit 4.10 is used as an external jar - and referenced successfully by the classpath and the .gwt.xml file is inheriting jUnit from GWT (<inherits name="com.google.gwt.junit.JUnit" />) the jUnit module is no longer inherited as the GWT team instructs not to - extending GWTTestCase will inherit it automatically.
i am using Raphael-GWT as a separate module. this module is also referenced in the main module's .gwt.xml file, and running fine under all other circumstances (development / production mode).
What have i tried
simplifying the case, e.g. stripping down the test case as seen above.
verifying inherited modules in the deployment descriptors.
varying jUnit's version, i.e. running both under V3 or V4, and manually compiled on each change.
looked up on google, as well as here on stackoverflow, with no avail.
More relevant information
Raphael lib is being used for a GWT wrapper i wrote for Dracula (a JS graph visualization library) so dracula_graffle.js originates there. enclosed is the .gwt.xml file source for a reference:
<module rename-to="gs_webui">
<inherits name="com.google.gwt.user.User" />
<!-- Other module inherits -->
<inherits name="com.extjs.gxt.ui.GXT" />
<inherits name="org.highchartsgwt.HighCharts" />
<inherits name="gwtupload.GWTUpload" />
<inherits name="com.hydro4ge.raphaelgwt.RaphaelGWT" />
<inherits name="com.gigaspaces.gauge.Gs_gauges" />
<inherits name="com.gigaspaces.graphs.Gs_graphs" />
<inherits name="com.gigaspaces.svgcomponents.Gs_svg_components" />
<inherits name="com.javaconstructors.colorpalette.Color_palette" />
<inherits name="com.gigaspaces.jquerywidgets.Gs_jquery_widgets" />
<inherits name="com.gigaspaces.codemirror_gwt.CodeMirror_GWT"/>
<inherits name="com.google.gwt.i18n.I18N"/>
<inherits name="com.google.gwt.query.Query" />
<!-- I18N stuff, log configurations, and so forth... -->
<entry-point class="com.gigaspaces.admin.webui.client.Gs_webui" />
<!-- further source folder inherits... -->
</module>
How is Raphael loaded? It could be that the js file is never being pulled in to the html page being run in htmlunit.
Caused by: com.gargoylesoftware.htmlunit.ScriptException: Wrapped com.gargoylesoftware.htmlunit.ScriptException: ReferenceError: "Raphael" is not defined. (http://192.168.10.32:3692/com.gigaspaces.admin.webui.Gs_webui.JUnit/dracula/dracula_graffle.js#18) (http://192.168.10.32:3692/com.gigaspaces.admin.webui.Gs_webui.JUnit/com.gigaspaces.admin.webui.Gs_webui.JUnit.nocache.js#16)
This file doesn't appear to be used by RaphaelGWT, as it is not listed in their module file (seen here http://code.google.com/p/raphaelgwt/source/browse/trunk/src/com/hydro4ge/raphaelgwt/RaphaelGWT.gwt.xml).
This seems to be the source of your error - dracula_graffle.js (either line 18, or this is the 18th file loaded) cannot find the symbol Raphael, and since it is somehow required by your module, the app (in this case test) can't load without it. My quick guess is that it is either an HtmlUnit issue (HtmlUnit is what the gwt test cases run in, and only simulates a real browser) - you might try running this same test in a real browser, see http://code.google.com/webtoolkit/doc/latest/DevGuideTesting.html#Manual_Mode for more info. If that fails, then perhaps your app normally loads into an html page where some JS files have already been loaded, so this doesnt happen - those need to be loaded when testing the app as well, either using ScriptInjector in a setup method, or by adding them to your module file.
(After edits, comments)
Since the error occurred in manual mode as well, there isn't an error with htmlunit, but with dependencies in your code. From what appears to be a copy of dracula_graffle.js at http://code.google.com/p/synoptic/source/browse/synopticgwt/war/dracula_graffle.js?spec=svn2164f4b075bb0ed77f7b008bd113e04831196fec&r=2164f4b075bb0ed77f7b008bd113e04831196fec, line 18 is the first reference to Raphael, which should have defined when the raphael js file was loaded, which implies that it wasn't.
Running in manual mode with Firebug or the like running should show you an error in the console. Based on this, I think it is safe to say that something is different about the test case than the standard entrypoint+html page. The question is, what is different.
Are there any JS files, or script tags that run when the html page loads? GWTTestCases always run with just a very simple html page, and only load scripts defined in the module that you actually name in your .gwt.xml file. Are there any setup functions that are run as part of the entrypoint? Have you tried making a new, very simple html page, and writing a new, very simple EntryPoint for the module and using that instead? In the course of testing these things, I believe you will find some difference that is important in how your app works from how your test works.
If there isn't... the next annoying step is to run in manual mode again, with your app compiled in production model (see the same link, it should give details on how that might be done). Set firebug (or whatever tool you prefer) to stop on exceptions in Js, or simple set a breakpoint on line 18, when Raphael is used for the first time in dracula_graffle.js to see what scripts have loaded, and why Raphael isn't yet defined.
Related
In my GWT 2.8 based project Eclipse 2020-03 shows me lots of error message under Markers -> Language Servers
I am sure that these are not errors. For some reason, Eclipse cannot interpret ui.xml files correctly. The application compiles and runs fine:
My eclipse wide settings for XML validation are as follows:
There are not project-specific settings for this
Here is an extract (not the complete source!!!) of one example of a something.ui.xml file. The project contains lots of those files:
<!DOCTYPE ui:UiBinder SYSTEM "http://dl.google.com/gwt/DTD/xhtml.ent">
<ui:UiBinder
xmlns:ui="urn:ui:com.google.gwt.uibinder"
xmlns:g="urn:import:com.google.gwt.user.client.ui"
xmlns:b="urn:import:org.gwtbootstrap3.client.ui"
xmlns:a="urn:import:com.myapp.client.widgets"
ui:generateFormat="com.google.gwt.i18n.rebind.format.PropertiesFormat"
ui:generateKeys="com.google.gwt.i18n.server.keygen.MD5KeyGenerator"
ui:generateLocales="default" >
<ui:with type="com.myapp.resources.text.CommonMessages" field="msgs" />
<ui:with type="com.myapp.resources.text.SummaryMessages" field="sMsgs" />
<b:Modal closable="true" fade="true" dataBackdrop="STATIC" dataKeyboard="true"
b:id="dialog"
ui:field="dialog">
<b:ModalHeader title="{sMsgs.transferOwnership}" />
<b:ModalBody>
<g:HTML><ui:text from="{sMsgs.transferOwnershipDescription}"/></g:HTML>
<b:ListBox
ui:field="userListBox"
multipleSelect="false"
width="100%"
/>
<b:Alert type="DANGER" ui:field="participantWarning">
<b:Icon type="WARNING"/>
<g:HTML><ui:text from="{sMsgs.transferOwnershipNotParticipantWarning}" /></g:HTML>
</b:Alert>
</b:ModalBody>
<b:ModalFooter>
These are the error messages:
Mouseover on the error always shows:
although it is declared above:
[...]
xmlns:b="urn:import:org.gwtbootstrap3.client.ui"
[...]
Import: The application compiles and runs fine. So I just want to suppress those error messages (show in error) as they are not really error messages. :-)
These resources might be helpful:
Why are there multiple Angular language server tabs in my Eclipse console
You can disable this validation by unchecking the box at Eclipse -> Preferences -> Language Servers -> XML.
I had the same problem (Eclipse 2020-06).
Disabling XML Language Server for XML content type worked for me:
By "must be declared", it means declared in a Document Type Definition (DTD) or XML Schema, also known as "grammar".
The line you quoted:
xmlns:b="urn:import:org.gwtbootstrap3.client.ui"
It says there's a namespace "b", but this line has no other meaning. It doesn't, for instance, declare which elements (like Alert) are valid in that namespace.
If you are not worried about validating your XML, and only wish to turn off the error messages, I would suggest you change your options:
No grammar specified: Warning → Ignore
This will stop Eclipse trying to validate the XML against a grammar, but should still show errors for malformed XML (tags closed twice etc.). You can configure this option on a per-project basis, if you prefer.
The alternative would be to provide a DTD or Schema and reference it in the XML. You will probably have to write such a grammar yourself unless gwtbootstrap3 provides one (which I don't think it does).
To clear existing validation errors, you may have to manually delete them.
Keep getting CSP errors: "Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self'"
The problem is probably due to HTML files generated by GWT which contain inline JS.
UPD: Changing to manifest version 1 helped, but this is a temporary workaroud, as Chrome 21 complains that it will no longer be supported.
UPD2: <add-linker name="xsiframe" /> does not help either
GWT 2.5.1 has finally fixed this problem. The release notes documenting this are here:
https://developers.google.com/web-toolkit/release-notes#Release_Notes_2_5_1
and they state that:
"Apps built with DirectInstallLinker should work in a page where inline scripts are forbidden (e.g. a Chrome extension)"
This means that it is now possible to use DirectInstallLinker to link your Chrome packaged app in a manner that satisfies the new security requirements of manifest version 2 regarding inline scripts. That is, by using DirectInstallLinker to link your app with GWT 2.5.1 selected as your GWT version, GWT will not place any script elements inline in its generated Javascript, and thus the new manifest version 2 requirement that there be no inline scripts will not be violated.
I have found that SingleScriptLinker also seems to work for my own app; however, Issue 7685 warns against using the SingleScriptLinker because "This generates a $doc.write line which is forbidden in packaged apps." I am using DirectInstallLinker myself.
Here is the Javadoc for DirectInstallLinker:
http://google-web-toolkit.googlecode.com/svn/javadoc/2.5/com/google/gwt/core/linker/DirectInstallLinker.html
To use this linker, you can include the following in your *.gwt.xml file:
<define-linker name="dil" class="com.google.gwt.core.linker.DirectInstallLinker"/>
<add-linker name="dil" />
(dil can be replaced by anything you choose, so long as there are no dashes or other illegal characters).
You will need to select GWT 2.5.1 as your version of GWT. If you're using an older version of GWT in an out-of-date version of Eclipse such as Ganymede (as I was), you'll have to upgrade to at least Helios and then import your project to your new Eclipse environment. The archive URLs for the Google Plugin for Eclipse that can be used for the latest three Eclipse versions can be found here:
https://developers.google.com/eclipse/docs/download
With the above in place, you should be able to set
"manifest_version": 2
in your manifest.json file and not experience any errors due to GWT-generated inline Javascript. This should allow your Chrome Web app to be acceptable to the Chrome Web Store (which now requires manifest version 2 for any new apps or for updates to present apps), so long as there are no other issues.
EDIT: new GWT bug reported: http://code.google.com/p/google-web-toolkit/issues/detail?id=7685, see also http://gwt-code-reviews.appspot.com/1838803/ which is related to this bug
In other words, it looks like, when fixed, you'll simply have to use the DirectInstallLinker (<add-linker name='direct_install'/>).
In the mean time, IIUC, you'd have to extend DirectInstallLinker and:
override getJsInstallLocation to return a copy a installLocaltionIframe.js without the $wnd part
override getModulePrefix to prepend var $wnd = $wnd || window.parent; to what's generated by super.getModulePrefix
I don't know CSP enough to give a complete answer, but the xsiframe linker is "customizable": create a class that extends com.google.gwt.core.linker.CrossSiteIframeLinker and overrides the appropriate methods, then use with a <define-linker> and <add-linker> in your *.gwt.xml.
For instance, getJsInstallLocation defaults to com/google/gwt/core/ext/linker/impl/installLocationIframe.js but there's a com/google/gwt/core/ext/linker/impl/installLocationMainWindows.js alternate implementation.
Similarly (and probably more importantly), getJsInstallScript defaults to com/google/gwt/core/ext/linker/impl/installScriptEarlyDownload.js but there's also a com/google/gwt/core/ext/linker/impl/installScriptDirect.js alternate implementation.
See http://code.google.com/p/google-web-toolkit/source/browse/trunk/dev/core/src/com/google/gwt/core/linker/CrossSiteIframeLinker.java#204, http://code.google.com/p/google-web-toolkit/source/browse/trunk/dev/core/src/com/google/gwt/core/ext/linker/impl/ and http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/core/Core.gwt.xml
Thanks to Thomas Broyer's advice. I created this GWT Linker. Now my GWT application runs perfectly as an Chrome Application (Tested on Chrome 32 and GWT 2.5.1).
public class CSPCompatibleLinker extends DirectInstallLinker {
#Override
protected String getJsInstallLocation(LinkerContext context) {
return "com/google/gwt/core/ext/linker/impl/installLocationMainWindow.js";
}
}
Dont forget to declare the Linker into your*.gwt.xml file:
<define-linker name="csp" class="com.sfeir.linker.CSPCompatibleLinker"/>
<add-linker name="csp" />
Manifest version 2 does not allow inline scripts. You need to make sure all scripts are linked instead and no JavaScript in HTML elements.
I have a litte web app which works properly when deployed to the App Engine in Eclipse.
However, I get an error when I want to deploy my app to my Tomcat server.
I copied the content of my war folder directly to the default ROOT folder of Tomcat.
Then I run my app on an external server inside Eclipse.
Everything works fine to that point - the app is loaded straight from the browser's cache.
Here comes the problem:
The google chrome development console says "Uncaught ReferenceError: function is not defined" when I click on some features of my app that are realized through JSNI on GWT side.
I understand that the error comes from a JS caller inside external JS code. The caller invokes a GWT client-side method/function (that's why it is not defined in the ext. JS code).
Any suggestions on how to solve this problem?
Do you have any extra modules that require external js files? Some modules require the js files to be included in the war and included in your root .html file. It could be the case that you are using a library that doesn't have the base js functions.
You can add this to your .gwt.xml file to turn on the stack trace.
<set-property name="compiler.stackMode" value="emulated"/>
<set-configuration-property name="compiler.emulatedStack.recordLineNumbers" value="true"/>
<set-configuration-property name="compiler.emulatedStack.recordFileNames" value="true"/>
You could also try the setUncaughtException handler to see exceptions that are being thrown in production mode. With the emulated stack trace turned on you should be able to get a backtrace that has line numbers for your code. It is not as good as development mode but very useful for debugging.
GWT.setUncaughtExceptionHandler(new GWT.UncaughtExceptionHandler()) {
#Override
public void onUncaughtException(Throwable cause) {
logger.log(Level.SEVERE, "OOPS", cause);
}
}
Note Make sure your logger is configured to use something you can access. Like firebug or remote logging servlet.
I currently use tomcat 7 in production and development mode using eclipse. You can configure a tomcat instance of the server in eclipse and use the "Run as WebApplication on External Server". This will allow you to see the exception in development mode.
Also make sure you don't have the ?gwt.codesvr=127.0.0.1:9997 if you are in production mode. This will cause problems too unless you have the development code server running.
As far as I know the "user.agent" property in the Google Web Toolkit .gwt.xml file specifies the targets for the Java to Java Script translation. Because the hosted mode still runs Java and not Javascript I don't understand why google chrome complains that the "user.agent" value is not set correctly. Even more strange, it keeps complaining even if I add "safari" to it with <set-property name="user.agent" value="gecko1_8,safari" />.
What can I do here?
I use GWT version 2.3.0 and GXT version 2.2.5.
DevMode does not compile to JavaScript but still has to honor deferred binding rules, and many of them are based on the user.agent property, so it must be correctly set.
The user.agent property value is determined by some script snippet generated in the so-called selection script (the *.nocache.js file), and the content of this script can depend on the set-propertys you have in your GWT module(s).
For instance, if you compile a GWT module with <set-property name="user.agent" value="gecko1_8" />, the user.agent property will be hard-coded to the gecko1_8 value in the *.nocache.js.
If you later run DevMode, unless it thinks it has to overwrite the existing *.nocache.js, it'll use it; so running the app using Chrome when the *.nocache.js was generated for gecko1_8 only will cause an error similar to:
com.google.gwt.core.client.JavaScriptException: (TypeError): Property 'user.agent' of object is not a function
In case you compiled for several browsers, but then run DevMode with a module only for gecko1_8, then the DevMode will use the property provider found in the *.nocache.js to determine the actual user agent being used (woul dbe safari for Chrome), and will compare it with the one determined from the module (hard-coded here to gecko1_8), and will then warn you that they don't match (and as such that you app might dysfunction: the code will use DOMImplMozilla for instance, whereas DOMImplSafari should have been used in Chrome).
So, to fix this, either delete the *.nocache.js file so DevMode will have to generate a new one, or recompile your app with a module whose user.agent values match the browser you'll use in DevMode.
I remove the inherit of standard the from my module and replaced for:
<inherits name='com.google.gwt.user.theme.clean.Clean'/>
But my project still includes the standar theme, and after the clean:
<link rel="stylesheet" href="http://127.0.0.1:8888/formulariorequerimientos3/gwt/clean/clean.css">
<link rel="stylesheet" href="http://127.0.0.1:8888/formulariorequerimientos3/gwt/standard/standard.css">
So the styles are mixed and I see the horrible dialogbox of standard theme, please help!
Probably caching issue. Shut down you dev IDE and server serving the app .It's should really be in hosted mode.Clear browsers cache. Shut down your machine and restart. You will not have to do this all the time but sometimes caches get stuck. Also make sure there are not error in IDE and and check sever log as well (meaning logs from hosted mode server) to see any errors being thrown.
Check your War\Webapp if you see clean/clean.css then delete clean folder altogather. Also suggest Project->clean if you are using eclipse.
The problem is that I wa including a module (one of UI utils) that inherits standard theme, so I replaced for clean