Author: [email protected]
Date: Fri Mar  6 08:22:07 2009
New Revision: 4949

Modified:
    releases/1.6/distro-source/core/src/doc/helpInfo/webAppClassPath.html

Log:
Minor wording and formatting tweaks.



Modified:  
releases/1.6/distro-source/core/src/doc/helpInfo/webAppClassPath.html
==============================================================================
--- releases/1.6/distro-source/core/src/doc/helpInfo/webAppClassPath.html       
 
(original)
+++ releases/1.6/distro-source/core/src/doc/helpInfo/webAppClassPath.html       
 
Fri Mar  6 08:22:07 2009
@@ -7,18 +7,18 @@

  <h1>Web App Classpath Problem</h1>

-<p>You were directed to this doc because your server code needed a class or
-resource that was not found on <i>web app classpath</i>, but <b>was</b>  
found
+<p>You were directed to this help topic because your server code needed a  
class or
+resource that was not found on the <i>web app classpath</i>, but  
<b>was</b> found
  on the <i>system classpath</i>. The <i>system classpath</i> is the  
classpath
  you specify when launching the Java VM to run hosted mode.  The <i>web app
-classpath</i> is different-- it consists of classes that live in your web
+classpath</i> is different &mdash; it consists of classes that live in  
your web
  application's <i>war directory</i>.  All server classes and dependencies  
should
-to be placed in your war directory-- libraries (jars) should be placed in
-<code>war/WEB-INF/lib/</code>; classes that don't live in jars should be  
placed
-in <code>war/WEB-INF/classes/</code>.
+to be placed in your war directory: libraries (jars) should be placed in
+<nobr><code>war/WEB-INF/lib/</code></nobr> and classes that don't live in
+jars should be placed in <nobr><code>war/WEB-INF/classes/</code></nobr>.

  <p>GWT hosted mode helpfully works around this problem by mapping these  
outside
-resources into your web app classpath.  A warning is issued because  
failing to
+resources into your web app classpath.  This warning reminds you that  
failing to
  address the issue can lead to problems when you actually deploy your web  
app to
  a real server.</p>

@@ -26,13 +26,14 @@

  <ul>
  <li>The most common reason to encounter this problem with a new project is
-trying to load <code>com.google.gwt.user.client.rpc.RemoteService</code>.  
The
+using RPC, which tries to load
+<nobr><code>com.google.gwt.user.client.rpc.RemoteService</code></nobr>. The
  solution to is copy <code>gwt-servlet.jar</code> from the GWT install  
directory
-into your web app's <code>war/WEB-INF/lib/</code> directory.</li>
+into your web app's <nobr><code>war/WEB-INF/lib/</code></nobr>  
directory.</li>
  <li>If you have a good reason for not following the recommended  
configuration,
  you can suppress warning by setting the Java system property
-<code>gwt.nowarn.webapp.classpath</code>.  Specify
-<code>-Dgwt.nowarn.webapp.classpath</code> as a JVM argument when launching
-hosted mode.
+<nobr><code>gwt.nowarn.webapp.classpath</code></nobr>.  Specify
+<nobr><code>-Dgwt.nowarn.webapp.classpath</code></nobr> as a JVM argument  
when
+launching hosted mode.
  </li>
  </ul>

--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---

Reply via email to