Databases
StackOverflow2013
Postsdbo
PO
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The <code>StockPriceServlet</code> should be extending <code>RemoteServiceServlet</code>, which is just for RPC calls, and thus does not support <code>GET</code>. Don't direct your browser to that url, instead use the html files that are provided in the app. The actual url should be shown on the Dev Mode console. On the <a href="https://developers.google.com/web-toolkit/doc/latest/tutorial/gettingstarted" rel="nofollow">https://developers.google.com/web-toolkit/doc/latest/tutorial/gettingstarted</a> tutorial, this is described in step 2 on <a href="https://developers.google.com/web-toolkit/doc/latest/tutorial/create" rel="nofollow">https://developers.google.com/web-toolkit/doc/latest/tutorial/create</a> - the url will be <code>http://localhost:8888/StockWatcher.html</code> or, more likely if using dev mode, <code>http://localhost:8888/StockWatcher.html?gwt.codesvr=localhost:9997</code>. From the web.xml, you don't even need to list the html file itself:</p> <pre><code> &lt;!-- Default page to serve --&gt; &lt;welcome-file-list&gt; &lt;welcome-file&gt;StockWatcher.html&lt;/welcome-file&gt; &lt;/welcome-file-list&gt; </code></pre> <p><code>http://localhost:8888/?gwt.codesvr=localhost:9997</code> should suffice.</p> <p>Servlets aren't always intended to serve up html, and this is one of those cases - the express purpose of this type of servlet is to be a way for the GWT client to interact with Java methods on the server, by passing objects back and forth. Check out <a href="https://developers.google.com/web-toolkit/doc/latest/tutorial/RPC" rel="nofollow">https://developers.google.com/web-toolkit/doc/latest/tutorial/RPC</a> for more details on how this servlet is intended to be used - only from within client code.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload