I have been having an issue with my project setup running in --
noServer since 1.6.? that I'm hoping you could help me with. I am
getting the error
"17:01:38.826 [ERROR] [dashboard] Unable to find 'dashboard.gwt.xml'
on your classpath; could be a typo, or maybe you forgot to include a
classpath entry for source?"
with the following module:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 1.7.1//
EN" "
http://google-web-toolkit.googlecode.com/svn/tags/1.7.1/distro-
source/core/src/gwt-module.dtd">
<module rename-to="dashboard">
<entry-point class='com.example.dashboard.client.Dashboard'/>
<inherits name="com.google.gwt.user.User" />
<inherits name="com.google.gwt.visualization.Visualization" />
<inherits name="com.google.gwt.http.HTTP"/>
<inherits name="com.google.gwt.maps.GoogleMaps" />
<stylesheet src="common.css"/>
</module>
Using the following dashboard.html:
<html>
<head>
<title>Dashboard</title>
</head>
<body style="margin: 0;">
<!-- OPTIONAL: include this if you want history support -->
<iframe src="javascript:''" id="__gwt_historyFrame"
style="width: 0; height: 0; border: 0"></iframe>
<script type="text/javascript" language="javascript"
src="dashboard.nocache.js"></script>
</body>
</html>
On Dec 4, 3:13 pm, Chris Ramsdale <
cramsd...@google.com> wrote:
> Jan,
>
> It looks like you found an issue on our side. Given your project settings,
> the GPE is attempting to load GwtShell with the -style arg which has been
> removed.
>
> We have a fix in place for the 2.0 launch and in the meantime, if you want
> to continue using the RC2 plugin and SDK, you can do the following:
>
> 1. Uncheck the "Use Google Web Toolkit" setting within your project
> properties
> 2. Add a war/WEB-INF directory structure to your app
> 3. Add a web.xml to the WEB-INF directory with the following contents:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE web-app
> PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
> "
http://java.sun.com/dtd/web-app_2_3.dtd">
>
> <web-app>
> </web-app>
>
> 4. Check the "Use Google Web Toolkit" settings within your project
> properties
>
> This workaround will trigger the plugin to launch DevMode (instead of
> GwtShell) without the -style arg.
>
> - Chris
>
> On Thu, Dec 3, 2009 at 7:07 AM, Jan Ehrhardt <
jan.ehrha...@googlemail.com>wrote:
>
> > The idea was, to prevent the existences of 'war/*' in my GWT project. With
> > the current stable version of the plugin and GWT 1.7.1 everything works
> > well.
> > So the problem is, that my GWT project does not have any server code and no
> > host page or anything else. The current version works the following way:
>
> > - GWT (Web App launch configuration) app is launched in hosted mode
> > without the build in server.
> > - Instead of a host page in the same project, the host page comes from
> > an independent server.
> > - The hosted browser loads the host page (from the specified URL),
> > detects the existence of a GWT module (included as JavaScript) and replaces
> > the JavaScript with the Java Code from the classpath.
>
> > The interesting point is, that the text field to specify the URL is removed
> > from the GWT tab in the web app launch configuration (plugin version for GWT
> > 2.0 RC2). So the question is, how can I point the OOPHM to my host page's
> > URL (on any server)?
>
> > At least some words on what I'm currently doing in Eclipse 3.5 with the
> > released version of the plugin and GWT 1.7.1:
> > I've got a plain Java project and make a GWT project out of it by right
> > click on the project -> Google -> WebToolkit Settings. In these GWT settings
> > I check 'Use Google Web Toolkit' and then OK. This makes my Java project a
> > GWT project. I create a new Web App launch configuration for this project,
> > disable 'Run build in server' and on the GWT tab I insert my host pages URL
> > (
http://localhost:8080/my-app-which-runs-totaly-independent-on-a-tomcat).
> > That's it. It works.
> > Interestingly it's not required to specify any GWT module in any
> > configuration so far. The presence of the module's XML configuration on the
> > classpath and the presence of a previously compiled version of the module in
> > the loaded HTML page is enough to tell hosted browser, what to do. The GWT
> > Eclipse plugin doesn't even recognize the XML file since the included module
> > isn't shown in any settings or configuration interface. But it works.
>
> > Regards
> > Jan Ehrhardt
>
> > On Tue, Dec 1, 2009 at 5:03 PM, Chris Ramsdale <
cramsd...@google.com>wrote:
>
> >> Based on the fact that the plugin is attempting to launch GWTShell, it may
> >> not recognize your app as a "web app". This is typically the case when it
> >> doesn't find a war/WEB-INF/web.xml file in the project root. Can you confirm
> >> that this directory structure is in place? Also, what version of GWT and GPE
> >> were you using to previously build your application?
>
> >> On Tue, Dec 1, 2009 at 1:56 AM, Jan Ehrhardt <
jan.ehrha...@googlemail.com
> >>> On Mon, Nov 30, 2009 at 4:07 PM, Chris Ramsdale <
cramsd...@google.com>wrote:
>
> >>>> As a follow-up, are you using Web App Launch configurations or regular
> >>>> Java launch configurations? Also would you mind checking which version of
> >>>> the Google Eclipse Plugin you have installed? You can do this via
> >>>> Help->Install New Software and clicking on the "already installed" link in
> >>>> the lower right hand corner.
>
> >>>> On Mon, Nov 30, 2009 at 9:00 AM, Chris Ramsdale <
cramsd...@google.com>wrote:
>
> >>>>> Jan,
>
> >>>>> The -style argument has been removed when running in "development" mode
> >>>>> (formerly "hosted" mode). It is now configurable via the UI or an Ant
> >>>>> property when you compile your code. The UI settings are available by right
> >>>>> clicking on the project name, selecting Google->GWT Compile. From the
> >>>>> resulting view you will see options for "Log level" and "Output style". In
> >>>>> order to set the output style via Ant, add the following to your build.xml
> >>>>> file under the "gwtc" target:
>
> >>>>> <arg value="-style"/>
> >>>>> <arg value="PRETTY"/>
>
> >>>>> What other error are you seeing when specifying the "codeServerPort"?
>
> >>>>> On Mon, Nov 30, 2009 at 5:59 AM, Jan Ehrhardt <
> >>>>>
jan.ehrha...@googlemail.com> wrote:
>
> >>>>>> Hi,
>
> >>>>>> I'm currently looking how our existing project can be updated to GWT
> >>>>>> 2.0 when it's released, but I'm running into some trouble.
>
> >>>>>> We use Eclipse with the Google plugin and currently we've got one web
> >>>>>> project, which will be started as a web project running on an Eclipse server
> >>>>>> runtime. This runtime can be a Tomcat or a WebSphere. We've got another
> >>>>>> project, which contains the GWT stuff. Our GWT launch configuration is done
> >>>>>> with the following properties:
>
> >>>>>> - Run internal server is deselected
> >>>>>> - The GWT URL is pointed to '
http://localhost:8080/our-app'
> >>>>>>
google-web-tool...@googlegroups.com<
google-web-toolkit%2Bunsu...@googlegroups.com>
> >>>>>> .
> >>>>
google-web-tool...@googlegroups.com<
google-web-toolkit%2Bunsu...@googlegroups.com>
> >>>> .
> >>> To unsubscribe from this group, send email to
> >>>
google-web-tool...@googlegroups.com<
google-web-toolkit%2Bunsu...@googlegroups.com>
> >>> .
> ...
>
> read more »