Re: Validating ClientBundles ?

[Keith Platfoot]

Hi Carlos,

Thanks for reporting this issue.  This is definitely a bug, although I'm
having trouble reproducing it locally.  Would it be possible for you to zip
and send the projects that are crashing your Eclipse installation upon
import, so I can debug the problem?  Also, what version of Eclipse and
operating system are you using?

Thanks,

Keith

On Tue, Dec 22, 2009 at 12:07 PM, Carlos Aguayo wrote:

> Hi,
>
> After upgrading the Eclipse plugin to GWT 2.0, whenever I import my
> Eclipse projects, Eclipse crashes. After importing the projects, I see
> multiple multiple (~12) jobs spawned called "Validating
> ClientBundles", then it either shows a warning saying that it ran out
> of memory or just closes.
>
> When inspecting the Eclipse log, I found this:
> 
> !ENTRY org.eclipse.core.jobs 4 2 2009-12-22 11:07:17.178
> !MESSAGE An internal error occurred during: "Refreshing workspace".
> !STACK 0
> java.lang.OutOfMemoryError: unable to create new native thread
>at java.lang.Thread.start0(Native Method)
>at java.lang.Thread.start(Thread.java:597)
>at org.eclipse.core.internal.jobs.WorkerPool.jobQueued
> (WorkerPool.java:145)
>at
> org.eclipse.core.internal.jobs.JobManager.schedule(JobManager.java:
> 1001)
>at org.eclipse.core.internal.jobs.InternalJob.schedule
> (InternalJob.java:391)
>at org.eclipse.core.runtime.jobs.Job.schedule(Job.java:435)
>at
> com.google.gdt.eclipse.core.BuilderUtilities.revalidateCompilationUnits
> (BuilderUtilities.java:170)
>at
> com.google.gwt.eclipse.core.clientbundle.ClientBundleResourceChangeListener
> $1.visit(ClientBundleResourceChangeListener.java:154)
>at org.eclipse.core.internal.events.ResourceDelta.accept
> (ResourceDelta.java:68)
>at org.eclipse.core.internal.events.ResourceDelta.accept
> (ResourceDelta.java:79)
>at org.eclipse.core.internal.events.ResourceDelta.accept
> (ResourceDelta.java:79)
>at org.eclipse.core.internal.events.ResourceDelta.accept
> (ResourceDelta.java:79)
>at org.eclipse.core.internal.events.ResourceDelta.accept
> (ResourceDelta.java:79)
>at org.eclipse.core.internal.events.ResourceDelta.accept
> (ResourceDelta.java:79)
>at org.eclipse.core.internal.events.ResourceDelta.accept
> (ResourceDelta.java:79)
>at org.eclipse.core.internal.events.ResourceDelta.accept
> (ResourceDelta.java:79)
>at org.eclipse.core.internal.events.ResourceDelta.accept
> (ResourceDelta.java:48)
>at
>
> com.google.gwt.eclipse.core.clientbundle.ClientBundleResourceChangeListener.visitResourceDelta
> (ClientBundleResourceChangeListener.java:124)
>at
>
> com.google.gwt.eclipse.core.clientbundle.ClientBundleResourceChangeListener.resourceChanged
> (ClientBundleResourceChangeListener.java:116)
>at org.eclipse.core.internal.events.NotificationManager$2.run
> (NotificationManager.java:291)
>at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>at org.eclipse.core.internal.events.NotificationManager.notify
> (NotificationManager.java:285)
>at
> org.eclipse.core.internal.events.NotificationManager.broadcastChanges
> (NotificationManager.java:149)
>at org.eclipse.core.internal.resources.Workspace.broadcastPostChange
> (Workspace.java:313)
>at org.eclipse.core.internal.resources.Workspace.endOperation
> (Workspace.java:1022)
>at org.eclipse.core.internal.resources.InternalWorkspaceJob.run
> (InternalWorkspaceJob.java:45)
>at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> ===
> These are my JVM settings in eclipse.ini:
>
> --launcher.XXMaxPermSize
> 256m
> -Xms256m
> -Xmx1024m
> -Xss1024k
>
> Is there a way to turn off this validation upon importing the project.
> Am I missing something or is this a bug?
>
> Thanks,
> Carlos
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
-- 

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-tool...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Standards mode requirement for GWT 2.0

[Keith Platfoot]

That's correct: the new layout system does require standards mode.  See
http://code.google.com/webtoolkit/doc/latest/DevGuideUiPanels.html#Standards

Keith

On Wed, Jan 6, 2010 at 6:36 AM, Thomas Broyer  wrote:

>
>
> On Jan 6, 2:48 am, N G  wrote:
> > Does DockLayoutPanel and SplitLayoutPanel require the page to be in
> > standards mode? Does this also apply to the RootLayoutPanel?
>
> AFAICT this applies to all the "LayoutPanel"s.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
>
-- 

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-tool...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Google eclipse plugin terms question

[Keith Platfoot]

Hi Fred,

The Google Plugin for Eclipse has not yet been open sourced, but we intend
to do so in the future.

Is the source necessary to create a m2eclipse project configurator?

Keith

On Wed, Jan 6, 2010 at 6:27 AM, Fred  wrote:

> Hi,
>
> if (and it's a big if) I were about to create a m2eclipse project
> configurator for Google Eclipse Plugin, it seems I'd have to ask
> google first (http://code.google.com/eclipse/terms.html §9.1).
> Do you know if accessing the plugin source code would be possible?
>
> regards,
>
> Fred Bricon
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
>
-- 

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-tool...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT 2.0 Eclipse Plugin Not Working

[Keith Platfoot]

Hi John,

When you try to debug the app in Eclipse, what is the debug process command
line?  You can find this by right-clicking the java process in the Debug
view in the Debug perspective, and selecting Properties.  Also, there might
be something useful in your workspace error log (/.metadata/.log), so if you can send that it may be helpful in
diagnosing the problem.

To answer your last question, no, the Google Eclipse Plugin includes an
embedded Development Mode log view that is used instead of the standard Java
console you'd see if you launched dev mode from the command line.  The
embedded view should appear automatically when you debug a Web App project.
 However, since you mentioned Jetty does not appear to be starting, I
suspect the problem is not with the view.

Let's start by inspecting your debug process args and error log, and go from
there.

Keith

On Wed, Jan 6, 2010 at 3:36 PM, Hethcox  wrote:

> FWIW I created a new project with 2.0 and it works fine.
>
> On Jan 6, 2:16 pm, Hethcox  wrote:
> > Hi,
> > I'm attempting to get my project working in GWT 2.0 under Eclipse 3.5
> > on Windows XP. The project was previously running under 1.7.
> > Everything is working except jetty under Eclipse. (I separately
> > compile and deploy the app to JBoss and it works fine). When I attempt
> > to debug the app under Eclipse (Debug As->Web Application) I get
> > nothing. It just sits there. Sometimes some text appears at startup in
> > the console, but it disappears immediately. There is no process bound
> > to the relevant port so I don't think jetty is starting.
> >
> > I assume I'm supposed to get the same console that appears when you
> > run DevMode under java. Is that correct? Any thoughts?
> >
> > Cheers,
> > John
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
>
-- 

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-tool...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

Maven users survey

[Keith Platfoot]

Hi folks,

For the next release of the Google Plugin for Eclipse, we're planning on
making a few tweaks to make life easier for Maven users. That's right: we've
seen the stars on the issue tracker, and have decided it's time to act. I
would say, "we feel your pain", but the problem is, we don't. Which is to
say, nobody on the plugin team actually uses Maven (everybody around here
uses Ant). However, I've been researching Maven to determine exactly what
changes we should make to allow it to work more seamlessly with the Google
Eclipse Plugin. I've read the relevant issues and groups postings, so I
think I have a rough idea of what needs to happen. However, before we go and
make any changes, I wanted to ask for the community's advice.  So, here are
some questions for you.

What is the typical workflow of a GWT developer using Maven?

I've installed Maven and the gwt-maven-plugin 1.2-SNAPSHOT and managed to
create a GWT 2.0 app with the provided archetype. After some tweaking, I'm
able to GWT compile, debug with Eclipse (though not via our Web App launch
configuration), create a WAR, etc. However, I'm more interested in how you all
are doing things. For example:

How do you...


   - Create a new project?
   - Perform GWT compiles?
   - Debug with Eclipse?
   - Run your tests?
   - Create a WAR for deployment?

What specific pain points do Maven users run into when using the Google
plugin?

I know one major obstacle is that our plugin currently treats the war
directory as both an input (e.g. static resources, WEB-INF/lib,
WEB-INF/web.xml) and output (WEB-INF/classes, GWT artifacts like nocache.js
and hosted.html) . Maven convention, however, says that /src/main/webapp
should be input only, which means that hosted mode (or development mode, in
GWT 2.0) needs to run from a staging directory (e.g. gwt:run creates a /war
folder on demand). This mismatch results in the plugin creating spurious
validation errors and breaks our Web App launch configuration.

Another incompatibility is that Maven projects depend on the GWT Jars in the
Maven repo, whereas our plugin expects to always find a GWT SDK library on
the classpath.

Are my descriptions of these pain points accurate?  If so, one possible
solution would be for the plugin to allow the definition of an input war
directory (e.g. src/main/webapp) separate from a launch-time staging
directory, and for us to relax the requirement that all GWT projects must
have a GWT SDK library.  So tell me: would these changes adequately reduce
the friction between Maven and the Google plugin?

Also, are there other problems Maven users are running into when using the
plugin?

Thanks in advance for all feedback,

Keith, on behalf of the Google Plugin for Eclipse team
-- 

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-tool...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Eclipse, hosted mode, maven dependencies

[Keith Platfoot]

Hi Milan,

Currently, there are some known incompatibilities between Maven and the
Google Eclipse plugin, including the WEB-INF/lib issue you ran into.
 However, we are planning on improving things with the next release, and
have just posted a survey on the groups (Maven users
survey)
to elicit feedback from the community.  Please take a look and reply with
your suggestions.

Until we ship the next version, one solution for debugging in Eclipse is to
forget about the Web App launch configurations, and instead use the
gwt-maven-plugin's gwt:debug goal, and then attach to the debug process with
a Remote Java Application launch configuration in Eclipse.

Keith

On Wed, Jan 13, 2010 at 5:14 AM, 米兰  wrote:

> Hi,
>
> we've started adapting gwt in our company as our new GUI layer and we
> have some issues, especially in development mode. I would also refer
> to this thread(http://groups.google.com/group/google-web-toolkit/
> browse_thread/thread/f505610b3bc1ca17/dfe298d08e8bca13?
> lnk=gst&q=eclipse+hosted+mode+maven#dfe298d08e8bca13), but I am not
> quite satisfied with answers, there must be some solution! I hope ;).
>
> The case is we have a quite big project with several independent
> modules, We use maven 2 as our build/deployment tool, with all
> dependencies at place etc. Our development tool is eclipse(with maven2
> and gwt plugins installed). When implementing gwt, we set up a new GUI
> project using maven with all gwt plugins, maven-gwt plugins and that
> stuff.
> But we have problems when running our app in hosted mode in eclipse.
> It looks like gwt doesn't accept fact our 50+ libraries(our modules
> plus dependencies)  are not placed in war/WEB-INF/lib. Our non GWT
> modules changes quite often(at least version number, that is common
> for whole app) - especially our business layer that we rebuild right
> now. So placing them statically there is not the smartest solution -
> that is up to maven to tackle it.
> Our environment in eclipse looks correct with all maven dependencies,
> we are able to build, project, but when we run it, we get
> ClassNotFoundException, since libraries are not in war/WEB-INF/lib
> (this is not the case of development mode as I said, there we already
> have solution). Oh we also use Spring for DI, and that one really
> suffers a lot without llibraries.
>
> The even stranger fact is, that some of libraries(our base modules)
> are loaded automatically
>
> (Server class 'xx.x.CustomCollection' could not be found in the
> web app, but was found on the system classpath,[WARN] Adding classpath
> entry 'file:/home/milan/.m2/repository/xx/xx/CustomModule/2.01.0-
> b4/CustomModule-2.01.0-b4.jar' to the web app classpath for this
> session).
> And here I'm really puzzled, since CustomCollection is not used at all
> in our GWT app, but CustomModule-2.01.0-b4.jar is defined as maven
> dependency in pom. Strange fact is, there some other custom modules,
> that are also in the same pom file, but are not loaded automatically
> this way, even I refer to them and use classes(interfaces) from them
> in my GWT code.
>
> So problems summarized:
> 1. maven dependencies not used in hosted mode : GUI team has to copy
> manually all built libraries from local repository to war/WEB-INF/lib
> - very tiresome in length
> 2. some dependencies are added to web classpath some not, I couldn't
> find out why
>
> I checked whole eclipse, tried all possible configurations, I found
> some solutions, that might work, but not completely
> 1. add libraries to Run Configuration/.../ClassPath/BootstrapEntries :
> works, but what have we gained?
> 2. use maven tasks "gwt:eclipse gwt:compile gwt:run" : better, I just
> miss task for cleaning war/WEB-INF/lib directory before each running,
> then it would plausible solution - even I don't like running
> gwt:eclipse, not sure what it does beside copying maven dependencies
> to war/WEB-INF/lib
> 3. we can create task for deleting and copying necessary libraries to/
> from WEB-INF/lib : is this the only way?
>
>
>
> Sorry for longer post, but I am quite desperate.
>
> So any tips here? Experience? Can anyone help how to set up gwt
> project with maven correctly in eclipse?
>
>
> thanks,
>
> milan
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
>
-- 

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-tool...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.

Fo

Re: Eclipse plugin for GWT 1.7

[Keith Platfoot]

Hi Sanjay,

The latest version of the plugin (1.2) is still backwards-compatible with
GWT 1.7.1.  You can find the update site URL on the plugin's Quick Start
page:

http://code.google.com/eclipse/docs/getting_started.html

Keith

On Wed, Jan 13, 2010 at 2:15 AM, Sanjay  wrote:

> Is there a location where I can get the eclipse plugin for GWT 1.7. I
> just happened to delete it from eclipse in the process of upgrading to
> 2.0.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
>
-- 

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-tool...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Eclipse plugin for GWT 1.7

[Keith Platfoot]

Hi Sanjay,

Actually, the Eclipse plugin and GWT are on separate release cycles and do
not have the same version number.  So, it is possible to use the latest
Eclipse plugin (which is version 1.2) with any of the recent versions of GWT
(2.0, 1.7, 1.6).  When you install from the update site, just be sure to
uncheck the optional GWT 2.0 component if you don't want to use it.

Hope this helps.  Let me know if I've misunderstood something.

Keith

On Thu, Jan 14, 2010 at 12:41 PM, Sanjay  wrote:

> Hi Keith,
>
> I am actually looking for eclipse plugin of 1.7 for some other reason.
> With GWT 2.0 I see some issues while accessing through wireless
> network or for that matter VPN from my home. It's extremely slow,
> hence more then functionality I want to revert to make my development
> faster. I always use browser from different PC (Win) and my
> development in on Linux.
>
> Thanks,
> Sanjay
>
> On Jan 13, 8:55 am, Keith Platfoot  wrote:
> > Hi Sanjay,
> >
> > The latest version of the plugin (1.2) is still backwards-compatible with
> > GWT 1.7.1.  You can find the update site URL on the plugin's Quick Start
> > page:
> >
> > http://code.google.com/eclipse/docs/getting_started.html
> >
> > KeithOn Wed, Jan 13, 2010 at 2:15 AM, Sanjay 
> wrote:
> > > Is there a location where I can get the eclipse plugin for GWT 1.7. I
> > > just happened to delete it from eclipse in the process of upgrading to
> > > 2.0.
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google Web Toolkit" group.
> > > To post to this group, send email to
> google-web-tool...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-web-toolkit+unsubscr...@googlegroups.com
> 
> >
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
>
-- 

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-tool...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Eclipse plugin for GWT 1.7

[Keith Platfoot]

No problem.  If you would prefer to use the version of the 1.1 version of
the Google Plugin for Eclipse that was current when GWT 1.7.1 was released,
it's available for download as a zip file (not installable through Eclipse's
update mechanism, however).  See my post from last month:

http://groups.google.com/group/google-web-toolkit/msg/e6b9c9aaace3dbb7?hl=en

Keith

On Tue, Jan 19, 2010 at 1:40 PM, Sanjay  wrote:

>
> Hi Kieth,
>
> First thanks for your follow ups.
>
> I actually want to defer my decesion to upgrade to GWT 1.2 plugin for
> future. Is there a way to update to previous versions of plugin with
> hosted mode browser feature?
>
> With 1.2 which has new archetecture (with client side plugin) is
> extreamly slow in one of my network envirnoments, For now I have made
> temporary changes to get work done.
>
> Thanks,
> Sanjay
>
>
>
> On Jan 14, 11:58 am, Keith Platfoot  wrote:
> > Hi Sanjay,
> >
> > Actually, the Eclipse plugin and GWT are on separate release cycles and
> do
> > not have the same version number.  So, it is possible to use the latest
> > Eclipse plugin (which is version 1.2) with any of the recent versions of
> GWT
> > (2.0, 1.7, 1.6).  When you install from the update site, just be sure to
> > uncheck the optional GWT 2.0 component if you don't want to use it.
> >
> > Hope this helps.  Let me know if I've misunderstood something.
> >
> > Keith
> >
> >
> >
> > On Thu, Jan 14, 2010 at 12:41 PM, Sanjay  wrote:
> > > Hi Keith,
> >
> > > I am actually looking for eclipse plugin of 1.7 for some other reason.
> > > With GWT 2.0 I see some issues while accessing through wireless
> > > network or for that matter VPN from my home. It's extremely slow,
> > > hence more then functionality I want to revert to make my development
> > > faster. I always use browser from different PC (Win) and my
> > > development in on Linux.
> >
> > > Thanks,
> > > Sanjay
> >
> > > On Jan 13, 8:55 am, Keith Platfoot  wrote:
> > > > Hi Sanjay,
> >
> > > > The latest version of the plugin (1.2) is still backwards-compatible
> with
> > > > GWT 1.7.1.  You can find the update site URL on the plugin's Quick
> Start
> > > > page:
> >
> > > >http://code.google.com/eclipse/docs/getting_started.html
> >
> > > > KeithOn Wed, Jan 13, 2010 at 2:15 AM, Sanjay  >
> > > wrote:
> > > > > Is there a location where I can get the eclipse plugin for GWT 1.7.
> I
> > > > > just happened to delete it from eclipse in the process of upgrading
> to
> > > > > 2.0.
> >
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > > Groups
> > > > > "Google Web Toolkit" group.
> > > > > To post to this group, send email to
> > > google-web-tool...@googlegroups.com.
> > > > > To unsubscribe from this group, send email to
> > > > > google-web-toolkit+unsubscr...@googlegroups.com
> 
> > > 
> 
> >
> > > > > .
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/google-web-toolkit?hl=en.
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google Web Toolkit" group.
> > > To post to this group, send email to
> google-web-tool...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-web-toolkit+unsubscr...@googlegroups.com
> 
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-web-toolkit?hl=en.- Hide quoted
> text -
> >
> > - Show quoted text -
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
>
-- 

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-tool...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT 2.0 - Eclipse Plugin - Maven: 404 running in DevMode

[Keith Platfoot]

Hi Jim,

I believe the solution here is to just add a -startupUrl parameter to your
Java launch configuration.  In the absence of that parameter, DevMode tries
to guess which HTML host page you want to open, but I don't think it
searches subdirectories.  You can instead tell it exactly which page to open
with an argument like: *-startupUrl /subdir/page.html*

Regarding the "Web Application" launch configuration: there are currently
some incompatibilities between the Google Plugin for Eclipse and typical
Maven usage, so you're probably better off for now continuing to use a
regular Java launch.  However, we're planning on addressing this issue in
the next release of the plugin, so stay tuned.

Keith

On Mon, Jan 18, 2010 at 9:35 AM, Jim Adkins  wrote:

> I'm receiving a "404" status code when attempting to use the GWT 2.0
> Eclipse plug-in.
>
> The project was originally created with GWT 1.7 and used an Eclipse
> "Run Configuration" based on a "Java Application" run type.
>
> I modified the run configuration to use "DevMode" and GWT 2.0 library.
> When I "copy" the DevMode dialog supplied URL into a browser, I
> receive a 404.
>
> I suspect that this is occurring, because our project does not host
> the ".hmtl" file directly under the "war" directory, but
> in a sub directory under "war".
>
> We are using Maven2 and are setting a "" as well.
>
> I have noticed that all of the documentation for the GWT 2.0 Eclipse
> plugin indicates that the the "Web Application" run type is the
> standard way to designate a GWT launch profile...
>
> Any ideas?
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Maven users survey

[Keith Platfoot]

Yes, I've been meaning to reply back to this thread.  Thanks for reminding
me, Brian! :-)

Our plans for the next release of the Google Plugin for Eclipse (1.3)
include 4 changes designed to make integration with Maven and J2EE projects
easier:

   1. The WAR directory can now be configured to be *any* project-relative
   path (e.g. src/main/webapp if you're using Maven).  You'll also be able
   to specify whether that directory is source-only (typical Maven/J2EE
   scenario), or whether it should also function as the WAR output directory
   from which to run/debug or deploy to App Engine.  If your WAR directory is
   input *and* output (which will remain the default for new Web App
   projects), the plugin will manage synchronizing the contents of WEB-INF/lib
   WEB-INF/classes with your project's build path and compiled output.
Otherwise, we'll leave your WAR source directory alone and you'll need to
   specify your WAR output location when launching, deploying, etc (the plugin
   will remember the location once you set it the first time).
   2. The Web App launch configuration UI is being redesigned to allow you
   to see, and if necessary change, *any* of the launch arguments.
Previously, we were waiting until launch time to set many of these
   arguments based on heuristics that were invisible and inaccessible to you.
Now you'll be in full control of how your projects get launched.  Also,
   we're adding the capability to automatically migrate your launch
   configurations when necessary, for example, updating the -javaagent flag
   when changing App Engine SDKs.
   3. GWT/App Engine projects will no longer require our SDK library on the
   classpath.  This means Maven users will be able to pull in JAR files from
   their M2 repository as they're accustomed to and the plugin won't mind a
   bit.
   4. The severity of any problem marker generated by the plugin will be
   fully customizable via an Errors/Warnings preference page (similar to the
   Java Errors/Warnings page), letting you specify either Error, Warning, or
   Ignore.

We'll also be including a few smaller features and bug fixes as well.

What does everyone think about the 4 changes outlined above?  We've been
testing the plugin against various Maven and J2EE configurations to try to
ensure that we've eliminated the most critical roadblocks.  However, we're
very interested in also having you folks take it for a spin before the
official release date (slated for next month).  We're not quite ready yet,
but stay tuned for a 1.3 preview build to be made available hopefully in a
few weeks.  We'll distribute it as a zip file for dropin
installation<http://code.google.com/eclipse/docs/install-from-zip.html>
so
it will come with the standard warnings and caveats (use with a clean
Eclipse install and workspace, use at your risk, etc.).  However, it will
hopefully give you a chance to give us any last-minute feedback about our
changes before the final release.

Thanks,

Keith

On Thu, Feb 4, 2010 at 12:55 PM, bkbonner  wrote:

> Keith, are you going to give the folks who replied to your message
> some sort of thoughts on what you're going to implement and hopefully
> let us try it before you end up releasing the next release of the
> plugin?
>
> Brian
>
> On Jan 13, 11:35 am, Keith Platfoot  wrote:
> > Hi folks,
> >
> > For the next release of the Google Plugin for Eclipse, we're planning on
> > making a few tweaks to make life easier for Maven users. That's right:
> we've
> > seen the stars on the issue tracker, and have decided it's time to act. I
> > would say, "we feel your pain", but the problem is, we don't. Which is to
> > say, nobody on the plugin team actually uses Maven (everybody around here
> > uses Ant). However, I've been researching Maven to determine exactly what
> > changes we should make to allow it to work more seamlessly with the
> Google
> > Eclipse Plugin. I've read the relevant issues and groups postings, so I
> > think I have a rough idea of what needs to happen. However, before we go
> and
> > make any changes, I wanted to ask for the community's advice.  So, here
> are
> > some questions for you.
> >
> > What is the typical workflow of a GWT developer using Maven?
> >
> > I've installed Maven and the gwt-maven-plugin 1.2-SNAPSHOT and managed to
> > create a GWT 2.0 app with the provided archetype. After some tweaking,
> I'm
> > able to GWT compile, debug with Eclipse (though not via our Web App
> launch
> > configuration), create a WAR, etc. However, I'm more interested in how
> you all
> > are doing things. For example:
> >
> > How do you...
> >
> >- Create 

Re: Maven users survey

[Keith Platfoot]

Hi Olivier,

GPE 1.3 should be compatible with WTP/Eclipse EE.  For example, you'll be
able to easily add GWT and/or App Engine to an existing Dynamic Web Project,
and then debug the application using the GPE Web Application launch
configurations.  For GWT projects that have a separate backend (e.g. an
existing Tomcat or Jetty instance), you will be able to launch your GWT
font-end in the existing server, so you can debug both client-side code and
server-side code simultaneously.  If you change your GWT code during a
debugging session, you can refresh to get the updates immediately, and of
course do the same for server-side code and static resources changes as well
(if your server adapter supports it).

Keith

On Fri, Feb 5, 2010 at 3:17 AM, olivier nouguier  wrote:

> Thx a lot for all this, it will clearly simplify GWT with Maven, but did
> you plan to add some WTP support in the next GEP release ?
>
>
> On Thu, Feb 4, 2010 at 8:33 PM, Keith Platfoot wrote:
>
>> Yes, I've been meaning to reply back to this thread.  Thanks for reminding
>> me, Brian! :-)
>>
>> Our plans for the next release of the Google Plugin for Eclipse (1.3)
>> include 4 changes designed to make integration with Maven and J2EE projects
>> easier:
>>
>>1. The WAR directory can now be configured to be *any*project-relative 
>> path (e.g.
>>src/main/webapp if you're using Maven).  You'll also be able to
>>specify whether that directory is source-only (typical Maven/J2EE 
>> scenario),
>>or whether it should also function as the WAR output directory from which 
>> to
>>run/debug or deploy to App Engine.  If your WAR directory is input *
>>and* output (which will remain the default for new Web App projects),
>>the plugin will manage synchronizing the contents of WEB-INF/lib
>>WEB-INF/classes with your project's build path and compiled output.
>> Otherwise, we'll leave your WAR source directory alone and you'll need to
>>specify your WAR output location when launching, deploying, etc (the 
>> plugin
>>will remember the location once you set it the first time).
>>2. The Web App launch configuration UI is being redesigned to allow
>>you to see, and if necessary change, *any* of the launch arguments.
>> Previously, we were waiting until launch time to set many of these
>>arguments based on heuristics that were invisible and inaccessible to you.
>> Now you'll be in full control of how your projects get launched.  Also,
>>we're adding the capability to automatically migrate your launch
>>configurations when necessary, for example, updating the -javaagent flag
>>when changing App Engine SDKs.
>>3. GWT/App Engine projects will no longer require our SDK library on
>>the classpath.  This means Maven users will be able to pull in JAR files
>>from their M2 repository as they're accustomed to and the plugin won't 
>> mind
>>a bit.
>>4. The severity of any problem marker generated by the plugin will be
>>fully customizable via an Errors/Warnings preference page (similar to the
>>Java Errors/Warnings page), letting you specify either Error, Warning, or
>>Ignore.
>>
>> We'll also be including a few smaller features and bug fixes as well.
>>
>> What does everyone think about the 4 changes outlined above?  We've been
>> testing the plugin against various Maven and J2EE configurations to try to
>> ensure that we've eliminated the most critical roadblocks.  However, we're
>> very interested in also having you folks take it for a spin before the
>> official release date (slated for next month).  We're not quite ready yet,
>> but stay tuned for a 1.3 preview build to be made available hopefully in a
>> few weeks.  We'll distribute it as a zip file for dropin 
>> installation<http://code.google.com/eclipse/docs/install-from-zip.html> so
>> it will come with the standard warnings and caveats (use with a clean
>> Eclipse install and workspace, use at your risk, etc.).  However, it will
>> hopefully give you a chance to give us any last-minute feedback about our
>> changes before the final release.
>>
>> Thanks,
>>
>> Keith
>>
>> On Thu, Feb 4, 2010 at 12:55 PM, bkbonner wrote:
>>
>>> Keith, are you going to give the folks who replied to your message
>>> some sort of thoughts on what you're going to implement and hopefully
>>> let us try it before you end up releasing the next release of the
>>> plugin?
>>>
>>> Brian
>>>
&g

Re: Eclipse JavaEE tools + GWT Development mode

[Keith Platfoot]

Hi Chris,

We don't have any specific plans to add support to 1.3 for the sort of
project splitting you describe, but feel free to add an issue to the GWT
issue tracker <http://code.google.com/p/google-web-toolkit/issues/list> and
we'll look into working it into a future release if there's enough interest.

Thanks,

Keith

On Fri, Feb 19, 2010 at 6:17 AM, Chris Lercher wrote:

> Wow, that sounds good! I'm really happy to hear that GPE will make
> this available.
>
> There's one additional thing I'd like to be able to do: Split up the
> WebContainer part and the GWT part into two projects. This is
> currently not so easy, because
> - you'll need to have the web.xml in both projects and keep them in
> sync. I'd really like to have the web.xml in the Web project, not in
> the GWT project.
> - it's necessary to copy the GWT-compiled output folder from the GWT
> project into the Web project (I think, at least every time the
> serialization policy file changes (?)).
>
> Are there any plans for GPE to support this kind of project splitting?
>
> Chris
>
> On Feb 18, 5:40 pm, Keith Platfoot  wrote:
> > Hi Chris,
> >
> > Thanks for posting this.  It's a good explanation of how to get WTP and
> GPE
> > 1.2 working together, which is not a trivial task.  However, in the next
> > release of the plugin we're planning on making this integration a whole
> lot
> > easier<
> http://groups.google.com/group/google-web-toolkit/msg/8ff67143cce64e1...>
> > .
> >
> > With GPE 1.3, you'll be able to adapt an existing Dynamic Web Project as
> a
> > GWT project and debug using hosted/dev mode quite easily.  Here's a sneak
> > preview of how this will work in GPE 1.3:
> >
> > 1. In your project's Properties dialog, select Google > Web Toolkit and
> > check the box: *Use Google Web Toolkit*.
> >
> > 2. Switch to the Web Application property page and change *WAR source
> > directory* to "WebContent" and uncheck the box: *Also use this directory
> as
> > the output WAR directory.*
> > *
> > *
> > 3. Start your project's server (be it GlassFish, Tomcat, etc.) using your
> > configured WTP server adapter.
> >
> > 4. Create a new Web Application launch configuration.  On the Server tab,
> > uncheck: *Run built-in server* (since we want to use WTP's server
> adapter)
> > and on the GWT tab, change the -startupUrl argument to point to your
> server
> > (e.g.http://localhost:8080/WebApp)
> >
> > 5. Run/Debug your new launch configuration.  The first time you do this,
> > you'll have to select the location of the WAR directory WTP is publishing
> to
> > (this is configurable, but I think by default it is
> >
> /.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/
> ).
> >
> > 6. Presto!  GWT hosted/dev mode is now running in your own server, and
> you
> > can debug either server-side or client-side code, and get automatic
> redeploy
> > of modified class files or static resources thanks to WTP's auto-publish
> > mechanism.
> >
> > We're going to be uploading a preview built of GPE 1.3 later this month
> so
> > you can try it out for yourself and let us know what you think, ahead of
> the
> > official release.  Stay tuned!
> >
> > Keith
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Validating ClientBundles ?

[Keith Platfoot]

Hi Andrey,

I'm looking into this now, and will try to resolve it for the 1.3 release.

Thanks,

Keith

On Thu, Feb 18, 2010 at 4:49 AM, Andrey  wrote:

> Hi there,
>
> Are there any news about this issue? I've got two GWT installations -
> 1.7.0 and 2.0.0 and NO (!) google projects in my workspace. Still,
> when opening a large non-gwt project always crashes eclipse. This is
> definitely a show-stopper!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Validating ClientBundles ?

[Keith Platfoot]

I have a patch out to resolve this bug, so look for it to be fixed in 1.3.
 We're going to make available a special preview build of 1.3 next week, so
watch for an announcement in this mailing list and let me know if the 1.3
preview does not fix this for you.

Keith

On Wed, Feb 24, 2010 at 2:33 PM, Keith Platfoot wrote:

> Hi Andrey,
>
> I'm looking into this now, and will try to resolve it for the 1.3 release.
>
> Thanks,
>
> Keith
>
>
> On Thu, Feb 18, 2010 at 4:49 AM, Andrey wrote:
>
>> Hi there,
>>
>> Are there any news about this issue? I've got two GWT installations -
>> 1.7.0 and 2.0.0 and NO (!) google projects in my workspace. Still,
>> when opening a large non-gwt project always crashes eclipse. This is
>> definitely a show-stopper!
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google Web Toolkit" group.
>> To post to this group, send email to google-web-tool...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-web-toolkit+unsubscr...@googlegroups.com
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Maven users survey

[Keith Platfoot]

We're working on integrating our last few changes today, so look for an
announcement and download link sometime tomorrow or Wednesday. :-)

Keith

On Mon, Mar 1, 2010 at 2:46 PM, bkbonner  wrote:

> Keith, any news on the plugin update?
>
> Brian
>
> On Feb 4, 2:33 pm, Keith Platfoot  wrote:
> > Yes, I've been meaning to reply back to this thread.  Thanks for
> reminding
> > me, Brian! :-)
> >
> > Our plans for the next release of the Google Plugin for Eclipse (1.3)
> > include 4 changes designed to make integration with Maven and J2EE
> projects
> > easier:
> >
> >1. The WAR directory can now be configured to be *any*
> project-relative
> >path (e.g. src/main/webapp if you're using Maven).  You'll also be
> able
> >to specify whether that directory is source-only (typical Maven/J2EE
> >scenario), or whether it should also function as the WAR output
> directory
> >from which to run/debug or deploy to App Engine.  If your WAR
> directory is
> >input *and* output (which will remain the default for new Web App
> >projects), the plugin will manage synchronizing the contents of
> WEB-INF/lib
> >WEB-INF/classes with your project's build path and compiled output.
> > Otherwise, we'll leave your WAR source directory alone and you'll
> need to
> >specify your WAR output location when launching, deploying, etc (the
> plugin
> >will remember the location once you set it the first time).
> >2. The Web App launch configuration UI is being redesigned to allow
> you
> >to see, and if necessary change, *any* of the launch arguments.
> > Previously, we were waiting until launch time to set many of these
> >arguments based on heuristics that were invisible and inaccessible to
> you.
> > Now you'll be in full control of how your projects get launched.
>  Also,
> >we're adding the capability to automatically migrate your launch
> >configurations when necessary, for example, updating the -javaagent
> flag
> >when changing App Engine SDKs.
> >3. GWT/App Engine projects will no longer require our SDK library on
> the
> >classpath.  This means Maven users will be able to pull in JAR files
> from
> >their M2 repository as they're accustomed to and the plugin won't mind
> a
> >bit.
> >4. The severity of any problem marker generated by the plugin will be
> >fully customizable via an Errors/Warnings preference page (similar to
> the
> >Java Errors/Warnings page), letting you specify either Error, Warning,
> or
> >Ignore.
> >
> > We'll also be including a few smaller features and bug fixes as well.
> >
> > What does everyone think about the 4 changes outlined above?  We've been
> > testing the plugin against various Maven and J2EE configurations to try
> to
> > ensure that we've eliminated the most critical roadblocks.  However,
> we're
> > very interested in also having you folks take it for a spin before the
> > official release date (slated for next month).  We're not quite ready
> yet,
> > but stay tuned for a 1.3 preview build to be made available hopefully in
> a
> > few weeks.  We'll distribute it as a zip file for dropin
> > installation<http://code.google.com/eclipse/docs/install-from-zip.html>
> > so
> > it will come with the standard warnings and caveats (use with a clean
> > Eclipse install and workspace, use at your risk, etc.).  However, it will
> > hopefully give you a chance to give us any last-minute feedback about our
> > changes before the final release.
> >
> > Thanks,
> >
> > Keith
> >
> >
> >
> > On Thu, Feb 4, 2010 at 12:55 PM, bkbonner 
> wrote:
> > > Keith, are you going to give the folks who replied to your message
> > > some sort of thoughts on what you're going to implement and hopefully
> > > let us try it before you end up releasing the next release of the
> > > plugin?
> >
> > > Brian
> >
> > > On Jan 13, 11:35 am, Keith Platfoot  wrote:
> > > > Hi folks,
> >
> > > > For the next release of the Google Plugin for Eclipse, we're planning
> on
> > > > making a few tweaks to make life easier for Maven users. That's
> right:
> > > we've
> > > > seen the stars on the issue tracker, and have decided it's time to
> act. I
> > > > would say, "we feel your pain", but the problem is, we don't. Which
> is 

Re: GWT Eclipse Plugin Installation Problem

[Keith Platfoot]

First, did you remember to reboot after installation?

If so, try looking at the installed plugins: Help > About Eclipse Platform,
then click Plugin-in Details and see if you have any plugins whose provider
is "Google, Inc."  If you do not, then some aspect of the installation
failed.

Let me know whether Eclipse lists any Google-provided plugins, and if you
could send your Eclipse error log (/.metadata/.log) that would
also be helpful.

Keith

On Wed, Mar 3, 2010 at 4:42 AM, digidrops  wrote:

> I installed all the gwt plugins like described here:
>
> http://code.google.com/intl/de-DE/eclipse/docs/install-eclipse-3.5.html
>
> The installation went fine, but I either can't see the gwt-buttons or
> the google entries in preferences. I can't see anything from gwt
> except that the plugins are installed. Any suggestions?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT Eclipse Plugin Installation Problem

[Keith Platfoot]

That's great, Mathias, glad you got things working.

Keith

2010/3/3 Mathias Krüger 

> its seams, that was a problem with the my eclipse version. With the new
> version (3.5.3) it worked again. Tnxx
>
> 03.03.2010 17:48 schrieb am "Keith Platfoot" :
>
>
> First, did you remember to reboot after installation?
>
> If so, try looking at the installed plugins: Help > About Eclipse Platform,
> then click Plugin-in Details and see if you have any plugins whose provider
> is "Google, Inc."  If you do not, then some aspect of the installation
> failed.
>
> Let me know whether Eclipse lists any Google-provided plugins, and if you
> could send your Eclipse error log (/.metadata/.log) that would
> also be helpful.
>
> Keith
>
> On Wed, Mar 3, 2010 at 4:42 AM, digidrops  wrote:
>
> >
> > I installed all the gwt plugins like described here:
> >
> > http://code.google.com/intl/de-DE/eclip...
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" g...
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Validating ClientBundles ?

[Keith Platfoot]

Hi Greg

I've got good news... the preview release of 1.3 is almost ready, so look
for an announcement (with download URLs) on the GWT mailing list later today
or tomorrow.  Also, it does include a fix for the bug you're running into,
so although there's no workaround, 24 hours from now you won't need one. :-)

Keith

On Tue, Mar 2, 2010 at 1:37 PM, Greg  wrote:

> On schedule for preview release of 1.3 this week?
>
> I'm also anxiously awaiting a fix for this issue. We have a mature
> very large code base and recently have started using GWT for our web
> tier development.
>
> We have new developers starting and Eclipse is exploding when
> importing our projects trying to create a workspace. The last thing we
> see before it vanishes is a bunch of threads spawning to "Validate
> ClientBundles"  so I am pretty certain this is the same issue.
>
> I'm hoping this next release will fix this issue for us.
>
> Also, does anyone know of a workaround for this? I saw some mention of
> unchecking a checkbox but didn't quite follow.
>
> Thanks in advance!
>
> On Feb 24, 3:06 pm, Keith Platfoot  wrote:
> > I have a patch out to resolve this bug, so look for it to be fixed in
> 1.3.
> >  We're going to make available a special preview build of 1.3 next week,
> so
> > watch for an announcement in this mailing list and let me know if the 1.3
> > preview does not fix this for you.
> >
> > Keith
> >
> > On Wed, Feb 24, 2010 at 2:33 PM, Keith Platfoot  >wrote:
> >
> > > Hi Andrey,
> >
> > > I'm looking into this now, and will try to resolve it for the 1.3
> release.
> >
> > > Thanks,
> >
> > > Keith
> >
> > > On Thu, Feb 18, 2010 at 4:49 AM, Andrey  >wrote:
> >
> > >> Hi there,
> >
> > >> Are there any news about this issue? I've got two GWT installations -
> > >> 1.7.0 and 2.0.0 and NO (!) google projects in my workspace. Still,
> > >> when opening a large non-gwt project always crashes eclipse. This is
> > >> definitely a show-stopper!
> >
> > >> --
> > >> You received this message because you are subscribed to the Google
> Groups
> > >> "Google Web Toolkit" group.
> > >> To post to this group, send email to
> google-web-tool...@googlegroups.com.
> > >> To unsubscribe from this group, send email to
> > >> google-web-toolkit+unsubscr...@googlegroups.com
> 
> >
> > >> .
> > >> For more options, visit this group at
> > >>http://groups.google.com/group/google-web-toolkit?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Google Plugin for Eclipse 1.3 Preview is now available

[Keith Platfoot]

Hi everyone,

Last month, I announced some of the changes we had planned for the 1.3
version of the Google Plugin for Eclipse. To recap, this release is focused
on making life easier for developers using GWT/App Engine alongside
third-party tools, including Maven and Eclipse for Java EE. In my post, I
promised we'd let you download a preview of 1.3 to get some hands-on testing
of the new features and provide us with your feedback before the official
release.

I'm happy to announce that the time has come. An early preview of 1.3 is now
available for download at the following URLs:

http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.2.101.v201003031407.zip

http://dl.google.com/eclipse/plugin/3.4/zips/com.google.gdt.eclipse.suite.e34.feature_1.2.101.v201003031407.zip

http://dl.google.com/eclipse/plugin/3.3/zips/com.google.gdt.eclipse.suite.e33.feature_1.2.101.v201003031407.zip

Note: Ensure that your version of Eclipse has Eclipse's Web Standard Tools
(WST) installed before installing the plugin. WST can be installed by
navigating to the Software Installation section, and selecting the the
appropriate WST feature from the update site for your version of Eclipse.
The update sites and feature names are provided below:


   - 3.5 (Galileo): Galileo > Web, XML, and Java EE Development > Eclipse
   Web Developer Tools
   - 3.4 (Ganymede): Ganymede Update Site > Web and Java EE Development >
   Web Developer Tools
   - 3.3 (Europa): Europa Discovery Site > Web and JEE Development > Web
   Standard Tools Project

This is a preview build, so the usual caveats and warnings apply: it is not
officially supported, and we recommend using a clean installation of Eclipse
and a new workspace. Also, we're distributing this preview as a zip file so
be sure to follow the instructions on our Installing the Google Plugin for
Eclipse from zip files page (
http://code.google.com/eclipse/docs/install-from-zip.html).

*Known Issues*


   - If you change launch configuration settings in the Server or GWT tab,
   you'll need to switch to the Arguments tab before clicking Apply or
   Run/Debug.  This will be fixed in the final release.

That being said, we are very interested in your experience with this new
release, which we hope will allow the Google plugin to interoperate much
better with alternative project structures and third-party tools. The
tentative 1.3 release notes are as follows:

Enhancements


   - Configurable WAR directory to allow better integration with Eclipse for
   Java EE  and projects
   built with Maven 
   - Web Application launch configurations now display and allow editing of
   generated Program and VM arguments
   - Errors/Warnings preference page for customizing the severity of any
   generated problem marker
   - Projects can reference GWT/App Engine SDKs directly via JARs instead of
   through SDK library
   - GWT+App Engine projects automatically configured for optimal caching

Fixes


   - GWT Issue 
3583:
   Google Eclipse Plugin configuration is too strict
   - GWT Issue 
3592:
   Eclipse plugin to add 'cache forever' configuration for new 'GWT + App
   Engine' projects
   - GWT Issue 
3902:
   Allow users to configure the severity of problems reported by the eclipse
   plugin
   - App Engine Issue
1515:
   Eclipse plugin requires fixed location for war directory
   - App Engine Issue
2115:
   Using the @PersistenceAware annotation puts the Eclipse Enhancer in an
   Infinite Loop
   - App Engine Issue
1941:
   Plugin fails to enhance dependent classes on source level changes

For a complete list of fixed issues, see the GWT issue
tracker
 and App Engine issue
tracker
.

We encourage all interested developers to take the preview build for a spin,
and let us know what you think. We'll do everything possible to incorporate
your feedback before the final release, slated for later this month. Thanks!

Keith, on behalf of the Google Plugin for Eclipse team

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Maven users survey

[Keith Platfoot]

In case anyone on this thread missed the announcement, the Google Plugin for
Eclipse 1.3 preview is now available:

http://groups.google.com/group/google-web-toolkit/browse_thread/thread/981bae88b387b2a6/468ca0d8e04532cb

Keith

On Tue, Mar 2, 2010 at 2:02 PM, bkbonner  wrote:

> Cool. Thx
>
> On Mar 1, 2:56 pm, Keith Platfoot  wrote:
> > We're working on integrating our last few changes today, so look for an
> > announcement and download link sometime tomorrow or Wednesday. :-)
> >
> > Keith
> >
> > On Mon, Mar 1, 2010 at 2:46 PM, bkbonner 
> wrote:
> > > Keith, any news on the plugin update?
> >
> > > Brian
> >
> > > On Feb 4, 2:33 pm, Keith Platfoot  wrote:
> > > > Yes, I've been meaning to reply back to this thread.  Thanks for
> > > reminding
> > > > me, Brian! :-)
> >
> > > > Our plans for the next release of the Google Plugin for Eclipse (1.3)
> > > > include 4 changes designed to make integration with Maven and J2EE
> > > projects
> > > > easier:
> >
> > > >1. The WAR directory can now be configured to be *any*
> > > project-relative
> > > >path (e.g. src/main/webapp if you're using Maven).  You'll also be
> > > able
> > > >to specify whether that directory is source-only (typical
> Maven/J2EE
> > > >scenario), or whether it should also function as the WAR output
> > > directory
> > > >from which to run/debug or deploy to App Engine.  If your WAR
> > > directory is
> > > >input *and* output (which will remain the default for new Web App
> > > >projects), the plugin will manage synchronizing the contents of
> > > WEB-INF/lib
> > > >WEB-INF/classes with your project's build path and compiled
> output.
> > > > Otherwise, we'll leave your WAR source directory alone and you'll
> > > need to
> > > >specify your WAR output location when launching, deploying, etc
> (the
> > > plugin
> > > >will remember the location once you set it the first time).
> > > >2. The Web App launch configuration UI is being redesigned to
> allow
> > > you
> > > >to see, and if necessary change, *any* of the launch arguments.
> > > > Previously, we were waiting until launch time to set many of
> these
> > > >arguments based on heuristics that were invisible and inaccessible
> to
> > > you.
> > > > Now you'll be in full control of how your projects get launched.
> > >  Also,
> > > >we're adding the capability to automatically migrate your launch
> > > >configurations when necessary, for example, updating the
> -javaagent
> > > flag
> > > >when changing App Engine SDKs.
> > > >3. GWT/App Engine projects will no longer require our SDK library
> on
> > > the
> > > >classpath.  This means Maven users will be able to pull in JAR
> files
> > > from
> > > >their M2 repository as they're accustomed to and the plugin won't
> mind
> > > a
> > > >bit.
> > > >4. The severity of any problem marker generated by the plugin will
> be
> > > >fully customizable via an Errors/Warnings preference page (similar
> to
> > > the
> > > >Java Errors/Warnings page), letting you specify either Error,
> Warning,
> > > or
> > > >Ignore.
> >
> > > > We'll also be including a few smaller features and bug fixes as well.
> >
> > > > What does everyone think about the 4 changes outlined above?  We've
> been
> > > > testing the plugin against various Maven and J2EE configurations to
> try
> > > to
> > > > ensure that we've eliminated the most critical roadblocks.  However,
> > > we're
> > > > very interested in also having you folks take it for a spin before
> the
> > > > official release date (slated for next month).  We're not quite ready
> > > yet,
> > > > but stay tuned for a 1.3 preview build to be made available hopefully
> in
> > > a
> > > > few weeks.  We'll distribute it as a zip file for dropin
> > > > installation<
> http://code.google.com/eclipse/docs/install-from-zip.html>
> > > > so
> > > > it will come with the standard warnings and caveats (use with a clean
> > > > Eclipse insta

Re: Google Plugin for Eclipse 1.3 Preview is now available

[Keith Platfoot]

Hey again,

Just wanted to mention that to actually customize your project's WAR
directory (enhancement bullet 1 in the announcement email), you'll need to
navigate to Google > Web Application in your project properties dialog.  You
can use any project-relative path as the WAR directory (e.g.
src/main/webapp) and you can also use the checkbox below to toggle whether
or not you want to launch and deploy from that directory, by default.  If
you uncheck that option, Eclipse will prompt you for a location the first
time you launch your project, and will not mess with the JARs in
/WEB-INF/lib or try to move your build output directory to
/WEB-INF/classes.  You can think of the checkbox as the *Keep your
hands off my runtime WAR directory!* option. :-)

If anyone runs into issues or has questions about any of the new features,
don't hesitate to ask.  Thanks!

Keith

On Wed, Mar 3, 2010 at 7:25 PM, Keith Platfoot  wrote:

> Hi everyone,
>
> Last month, I announced some of the changes we had planned for the 1.3
> version of the Google Plugin for Eclipse. To recap, this release is focused
> on making life easier for developers using GWT/App Engine alongside
> third-party tools, including Maven and Eclipse for Java EE. In my post, I
> promised we'd let you download a preview of 1.3 to get some hands-on testing
> of the new features and provide us with your feedback before the official
> release.
>
> I'm happy to announce that the time has come. An early preview of 1.3 is
> now available for download at the following URLs:
>
>
> http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.2.101.v201003031407.zip
>
>
> http://dl.google.com/eclipse/plugin/3.4/zips/com.google.gdt.eclipse.suite.e34.feature_1.2.101.v201003031407.zip
>
>
> http://dl.google.com/eclipse/plugin/3.3/zips/com.google.gdt.eclipse.suite.e33.feature_1.2.101.v201003031407.zip
>
> Note: Ensure that your version of Eclipse has Eclipse's Web Standard Tools
> (WST) installed before installing the plugin. WST can be installed by
> navigating to the Software Installation section, and selecting the the
> appropriate WST feature from the update site for your version of Eclipse.
> The update sites and feature names are provided below:
>
>
>- 3.5 (Galileo): Galileo > Web, XML, and Java EE Development > Eclipse
>Web Developer Tools
>- 3.4 (Ganymede): Ganymede Update Site > Web and Java EE Development >
>Web Developer Tools
>- 3.3 (Europa): Europa Discovery Site > Web and JEE Development > Web
>Standard Tools Project
>
> This is a preview build, so the usual caveats and warnings apply: it is
> not officially supported, and we recommend using a clean installation of
> Eclipse and a new workspace. Also, we're distributing this preview as a zip
> file so be sure to follow the instructions on our Installing the Google
> Plugin for Eclipse from zip files page (
> http://code.google.com/eclipse/docs/install-from-zip.html).
>
> *Known Issues*
>
>
>- If you change launch configuration settings in the Server or GWT tab,
>you'll need to switch to the Arguments tab before clicking Apply or
>Run/Debug.  This will be fixed in the final release.
>
> That being said, we are very interested in your experience with this new
> release, which we hope will allow the Google plugin to interoperate much
> better with alternative project structures and third-party tools. The
> tentative 1.3 release notes are as follows:
>
> Enhancements
>
>
>- Configurable WAR directory to allow better integration with Eclipse
>for Java EE <http://www.eclipse.org/downloads/moreinfo/jee.php> and
>projects built with Maven <http://maven.apache.org/>
>- Web Application launch configurations now display and allow editing
>of generated Program and VM arguments
>- Errors/Warnings preference page for customizing the severity of any
>generated problem marker
>- Projects can reference GWT/App Engine SDKs directly via JARs instead
>of through SDK library
>- GWT+App Engine projects automatically configured for optimal caching
>
> Fixes
>
>
>- GWT Issue 
> 3583<http://code.google.com/p/google-web-toolkit/issues/detail?id=3583>:
>Google Eclipse Plugin configuration is too strict
>- GWT Issue 
> 3592<http://code.google.com/p/google-web-toolkit/issues/detail?id=3592>:
>Eclipse plugin to add 'cache forever' configuration for new 'GWT + App
>Engine' projects
>- GWT Issue 
> 3902<http://code.google.com/p/google-web-toolkit/issues/detail?id=3902>:
>Allow users to configure the severity of problems reported by the eclipse
>plugin
&

Re: Google Plugin for Eclipse 1.3 Preview is now available

[Keith Platfoot]

Hi Fabio,

What's your specific issue with Eclipse on 64-bit Linux?  We've tested the
1.3 plugin on 64-bit versions of all 3 versions of Eclipse (3.3, 3.4, 3.5)
and did not encounter any problems.

If you can provide a few details, we'll see if we can work out a resolution
for you.

Keith

On Thu, Mar 4, 2010 at 12:14 PM, Fabio Kaminski wrote:

> any workarounds for eclipse 64 bit on linux?
>
> or there is some hack in eclipse to work smoothly with it..
>
> im still doing things by hand..
>
> Thanks
>
> Fabio Kaminski
>
> On Thu, Mar 4, 2010 at 1:40 PM, Keith Platfoot wrote:
>
>> Hey again,
>>
>> Just wanted to mention that to actually customize your project's WAR
>> directory (enhancement bullet 1 in the announcement email), you'll need to
>> navigate to Google > Web Application in your project properties dialog.  You
>> can use any project-relative path as the WAR directory (e.g.
>> src/main/webapp) and you can also use the checkbox below to toggle whether
>> or not you want to launch and deploy from that directory, by default.  If
>> you uncheck that option, Eclipse will prompt you for a location the first
>> time you launch your project, and will not mess with the JARs in
>> /WEB-INF/lib or try to move your build output directory to
>> /WEB-INF/classes.  You can think of the checkbox as the *Keep your
>> hands off my runtime WAR directory!* option. :-)
>>
>> If anyone runs into issues or has questions about any of the new features,
>> don't hesitate to ask.  Thanks!
>>
>> Keith
>>
>>
>> On Wed, Mar 3, 2010 at 7:25 PM, Keith Platfoot wrote:
>>
>>> Hi everyone,
>>>
>>> Last month, I announced some of the changes we had planned for the 1.3
>>> version of the Google Plugin for Eclipse. To recap, this release is focused
>>> on making life easier for developers using GWT/App Engine alongside
>>> third-party tools, including Maven and Eclipse for Java EE. In my post, I
>>> promised we'd let you download a preview of 1.3 to get some hands-on testing
>>> of the new features and provide us with your feedback before the official
>>> release.
>>>
>>> I'm happy to announce that the time has come. An early preview of 1.3 is
>>> now available for download at the following URLs:
>>>
>>>
>>> http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.2.101.v201003031407.zip
>>>
>>>
>>> http://dl.google.com/eclipse/plugin/3.4/zips/com.google.gdt.eclipse.suite.e34.feature_1.2.101.v201003031407.zip
>>>
>>>
>>> http://dl.google.com/eclipse/plugin/3.3/zips/com.google.gdt.eclipse.suite.e33.feature_1.2.101.v201003031407.zip
>>>
>>> Note: Ensure that your version of Eclipse has Eclipse's Web Standard
>>> Tools (WST) installed before installing the plugin. WST can be installed by
>>> navigating to the Software Installation section, and selecting the the
>>> appropriate WST feature from the update site for your version of Eclipse.
>>> The update sites and feature names are provided below:
>>>
>>>
>>>- 3.5 (Galileo): Galileo > Web, XML, and Java EE Development >
>>>Eclipse Web Developer Tools
>>>- 3.4 (Ganymede): Ganymede Update Site > Web and Java EE Development
>>>> Web Developer Tools
>>>- 3.3 (Europa): Europa Discovery Site > Web and JEE Development > Web
>>>Standard Tools Project
>>>
>>> This is a preview build, so the usual caveats and warnings apply: it is
>>> not officially supported, and we recommend using a clean installation of
>>> Eclipse and a new workspace. Also, we're distributing this preview as a zip
>>> file so be sure to follow the instructions on our Installing the Google
>>> Plugin for Eclipse from zip files page (
>>> http://code.google.com/eclipse/docs/install-from-zip.html).
>>>
>>> *Known Issues*
>>>
>>>
>>>- If you change launch configuration settings in the Server or GWT
>>>tab, you'll need to switch to the Arguments tab before clicking Apply or
>>>Run/Debug.  This will be fixed in the final release.
>>>
>>> That being said, we are very interested in your experience with this new
>>> release, which we hope will allow the Google plugin to interoperate much
>>> better with alternative project structures and third-party tools. The
>>> tentative 1.3 release notes are as follows:
>>>
>>> Enhancements
>>

Re: Google Plugin for Eclipse 1.3 Preview is now available

[Keith Platfoot]

Hi Fabio,

I'm not sure you're following the instructions for installing the plugin
from a zip file.  You should be extracting the contents of the zip into the
/dropins folder (if it doesn't already exists, go ahead and create
it).  Also, you should not need to use Eclipse "Install new software" dialog
at all... plugins in /dropins are registered automatically, without any UI
interaction on your part.

Try following these instructions for installing from zip files:

http://code.google.com/eclipse/docs/install-from-zip.html

Hope this helps,

Keith

On Thu, Mar 4, 2010 at 3:59 PM, Fabio Kaminski wrote:

> Hi Keith,
>
> my version is Galileo 3.5.1 64 on fedora linux
> with all WST plugins installed and recent updates..
>
> the google plugin never worked for me on this platform (no Google menu on
> windows > preferences, no GWT project wizard and buttons available)
>
> i even try your last patch .. unziping in the eclipse folder...
> and after update google plugin using the "install new software"
> everything went fine.. and eclipse detects plugin installed sucesfully..
>
> i thought this was normal with this version.. so i give up of the plugins
> and do things manually(a lot of hacks :s)..
>
> but i guess i can have some hope now :)
>
> Thanks
>
>
> On Thu, Mar 4, 2010 at 3:49 PM, Keith Platfoot wrote:
>
>> Hi Fabio,
>>
>> What's your specific issue with Eclipse on 64-bit Linux?  We've tested the
>> 1.3 plugin on 64-bit versions of all 3 versions of Eclipse (3.3, 3.4, 3.5)
>> and did not encounter any problems.
>>
>> If you can provide a few details, we'll see if we can work out a
>> resolution for you.
>>
>> Keith
>>
>>
>> On Thu, Mar 4, 2010 at 12:14 PM, Fabio Kaminski 
>> wrote:
>>
>>> any workarounds for eclipse 64 bit on linux?
>>>
>>> or there is some hack in eclipse to work smoothly with it..
>>>
>>> im still doing things by hand..
>>>
>>> Thanks
>>>
>>> Fabio Kaminski
>>>
>>> On Thu, Mar 4, 2010 at 1:40 PM, Keith Platfoot wrote:
>>>
>>>> Hey again,
>>>>
>>>> Just wanted to mention that to actually customize your project's WAR
>>>> directory (enhancement bullet 1 in the announcement email), you'll need to
>>>> navigate to Google > Web Application in your project properties dialog.  
>>>> You
>>>> can use any project-relative path as the WAR directory (e.g.
>>>> src/main/webapp) and you can also use the checkbox below to toggle whether
>>>> or not you want to launch and deploy from that directory, by default.  If
>>>> you uncheck that option, Eclipse will prompt you for a location the first
>>>> time you launch your project, and will not mess with the JARs in
>>>> /WEB-INF/lib or try to move your build output directory to
>>>> /WEB-INF/classes.  You can think of the checkbox as the *Keep your
>>>> hands off my runtime WAR directory!* option. :-)
>>>>
>>>> If anyone runs into issues or has questions about any of the new
>>>> features, don't hesitate to ask.  Thanks!
>>>>
>>>> Keith
>>>>
>>>>
>>>> On Wed, Mar 3, 2010 at 7:25 PM, Keith Platfoot wrote:
>>>>
>>>>> Hi everyone,
>>>>>
>>>>> Last month, I announced some of the changes we had planned for the 1.3
>>>>> version of the Google Plugin for Eclipse. To recap, this release is 
>>>>> focused
>>>>> on making life easier for developers using GWT/App Engine alongside
>>>>> third-party tools, including Maven and Eclipse for Java EE. In my post, I
>>>>> promised we'd let you download a preview of 1.3 to get some hands-on 
>>>>> testing
>>>>> of the new features and provide us with your feedback before the official
>>>>> release.
>>>>>
>>>>> I'm happy to announce that the time has come. An early preview of 1.3
>>>>> is now available for download at the following URLs:
>>>>>
>>>>>
>>>>> http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.2.101.v201003031407.zip
>>>>>
>>>>>
>>>>> http://dl.google.com/eclipse/plugin/3.4/zips/com.google.gdt.eclipse.suite.e34.feature_1.2.101.v201003031407.zip
>>>>>
>>>>>
>>>>> http://dl.google.com/eclipse/plugin/3.3/zips/com.google.gdt.eclipse.

Re: Google Plugin for Eclipse 1.3 Preview is now available

[Keith Platfoot]

Hi Olivier,

Thanks for your feedback/questions.  My responses are inline.

Keith

On Fri, Mar 5, 2010 at 9:03 AM, olivier nouguier  wrote:

> hi keith,
>
>  And thx you all for the new upcoming release !
>  No new issues with this release (eclipse 3.5.1 + maven + sts + aspectj +
> wtp).
>
> * Same classloader (than GEP 1.2) issues with spring namespace handler in
> dev mode.
>

I'm not familiar with this problem.  Is there a bug on the GWT issue tracker
I can review to get more details?


>
> * I cannot figure out how to work with wtp (noserver mode). For the moment
> I have to manually modify the wtp manifest to publish the GWT resources
> (compiled js img).
>

Could you elaborate a bit more on this?  I'm able to run Web Application
launches with -noserver on Eclipse/J2EE (my project is being published to a
Tomcat instance) without any issues.  You shouldn't need to worry about the
GWT-compiled JavaScript if you're just running hosted/dev mode.

At deploy time, you can use the GWT Compile button on the toolbar and
specify your project's WebContent directory, so that the compiled JavaScript
is included in your WAR file.


>
> * What is the state of support for the "input only" assumption for maven
> src/main/webapp  ?
>

It is now possible for src/main/webapp to be treated as input-only.  In
project properties > Google > Web Application, you'll notice that below the
"WAR directory" field, there is now a checkbox labeled "Launch and deploy
from this directory."  If you uncheck that box, the plugin will treat the
directory as input-only.  This means:

   - You'll have to tell us where to launch/deploy from since presumably you
   have a separate runtime WAR directory
   - We will not try to validate or manage the contents of /WEB-INF/lib or
   /WEB-INF/classes.  It will be up to you or your IDE/framework to ensure that
   your JARs and class files are located in your "real" WAR directory when you
   launch or deploy.



>
> Since the beginning (before the first GEP release) I working with the
> noserver mode without blocking issues with maven.
>
> IMHO The only missing killing feature  would be a facet (wtp) to be able to
> detect and publish the GWT module to WTP deployement.
>

Not quite sure what you mean by publishing GWT modules to WTP deployment.
 Are you referring to the compiled JavaScript produced by the GWT compiler?


>
> Thx again.
>
>
Thank you for the feedback!


>
>
>
> On Thu, Mar 4, 2010 at 5:40 PM, Keith Platfoot wrote:
>
>> Hey again,
>>
>> Just wanted to mention that to actually customize your project's WAR
>> directory (enhancement bullet 1 in the announcement email), you'll need to
>> navigate to Google > Web Application in your project properties dialog.  You
>> can use any project-relative path as the WAR directory (e.g.
>> src/main/webapp) and you can also use the checkbox below to toggle whether
>> or not you want to launch and deploy from that directory, by default.  If
>> you uncheck that option, Eclipse will prompt you for a location the first
>> time you launch your project, and will not mess with the JARs in
>> /WEB-INF/lib or try to move your build output directory to
>> /WEB-INF/classes.  You can think of the checkbox as the *Keep your
>> hands off my runtime WAR directory!* option. :-)
>>
>> If anyone runs into issues or has questions about any of the new features,
>> don't hesitate to ask.  Thanks!
>>
>> Keith
>>
>> On Wed, Mar 3, 2010 at 7:25 PM, Keith Platfoot wrote:
>>
>>> Hi everyone,
>>>
>>> Last month, I announced some of the changes we had planned for the 1.3
>>> version of the Google Plugin for Eclipse. To recap, this release is focused
>>> on making life easier for developers using GWT/App Engine alongside
>>> third-party tools, including Maven and Eclipse for Java EE. In my post, I
>>> promised we'd let you download a preview of 1.3 to get some hands-on testing
>>> of the new features and provide us with your feedback before the official
>>> release.
>>>
>>> I'm happy to announce that the time has come. An early preview of 1.3 is
>>> now available for download at the following URLs:
>>>
>>>
>>> http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.2.101.v201003031407.zip
>>>
>>>
>>> http://dl.google.com/eclipse/plugin/3.4/zips/com.google.gdt.eclipse.suite.e34.feature_1.2.101.v201003031407.zip
>>>
>>>
>>> http://dl.google.com/eclipse/plugin/3.3/zips/com.google.gdt.eclipse.suite.e33.feature_1.2.101.v201003031407.

Re: beta eclipse plugin - running in noserver mode with tomcat - having troubles

[Keith Platfoot]

Brian,

I think the issues you were having with adding the -noserver argument to
your launch configuration were probably the result of a known issue with the
Eclipse plugin 1.3 preview (check the 1.3 announcement email for details).
 This has since been fixed, so once 1.3 final is released (probably next
week), this particular problem should be resolved.

Regarding the NoSuchFieldError exception: I have hit this same bug when
using GWT with a Tomcat server in Eclipse for Java EE.  My solution was the
same: moving the GWT dependencies to the top of the project's build
classpath.  I'll investigate to see if there is something we can do to help
prevent this problem.

As for the UiBinder errors, I probably would not be of much help there.
 I'll forward this email to someone who's more knowledgeable about the
subject.

Keith

On Wed, Mar 10, 2010 at 11:39 AM, bkbonner wrote:

> OK, it looks like the -noserver doesn't get injected into the debug
> configuration based on any of the GWT Toolkit settings.   I don't have
> it working yet, but I've tried:
>
> -remoteUI ${gwt_remote_ui_server_port}:${unique_id} -startupUrl
> http://localhost:8080:/testproject/loganalyzer.html -logLevel INFO -
> noserver -war C:\work\workspace-galileo\testproject\src\main\webapp
> com.test.gwt.Application
>
> I get:
>
> 11:38:22.194 [ERROR] [Application] Failed to load module 'Application'
> from user agent 'Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:
> 1.9.1.8) Gecko/20100202 Firefox/3.5.8' at localhost:4767
> java.lang.NoSuchFieldError:
> reportUnusedDeclaredThrownExceptionIncludeDocCommentReference
>at
> com.google.gwt.dev.javac.JdtCompiler.getCompilerOptions(JdtCompiler.java:
> 310)
>at com.google.gwt.dev.javac.JdtCompiler
> $CompilerImpl.(JdtCompiler.java:148)
>at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:
> 466)
>at com.google.gwt.dev.javac.CompilationStateBuilder
> $CompileMoreLater.compile(CompilationStateBuilder.java:142)
>at
>
> com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:
> 281)
>at
>
> com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:
> 182)
>at
> com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:
> 280)
> at com.google.gwt.dev.DevModeBase
> $UiBrowserWidgetHostImpl.createModuleSpaceHost(DevModeBase.java:99)
> at
>
> com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:
> 180)
> at
>
> com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:
> 380)
>at
>
> com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:
> 222)
>at java.lang.Thread.run(Thread.java:595)
>
> It would be nice to have an option to use existing server (which would
> inject the -noserver option)
>
> Also, the performance of the DebugConfiguration screen while I'm
> typing is really slow... I suspect there is parsing going on?   I saw
> that you have to click apply before running debug, but is there
> anything else?
>
> Any suggestions would be appreciated.
>
>
>
>
>
>
>
> On Mar 10, 10:49 am, bkbonner  wrote:
> > Keith,
> >
> > I'm trying to run our app using the eclipse beta plugin.   I'm not
> > sure if I have things configured correctly.
> >
> > The tree for our app is like:
> >
> > src\main\java\com\test\gwt\App.gwt.xml
> > src\main\java\com\test\gwt\client\Application.java
> > ...
> > src\main\webapp\
> > src\main\webapp\WEB-INF
> > src\main\webapp\WEB-INF\classes
> > src\main\webapp\WEB-INF\lib
> > ...
> > src\test\java\
> >
> > The setup for the google web toolkit is:
> >
> > Web Application
> >   X This project has a WAR directory  (checked)
> >  WAR Directory:  src/main/webapp
> >  [ ] Launch and deploy from this directory  (unchecked)  I've
> > tried it checked as well
> >
> > Web Toolkit
> >GWT 2.0.3
> >
> > In the Debug Configuration:
> >
> > Main
> >  Project
> >  testproject
> >  Main class
> >  com.google.gwt.dev.DevMode
> > Server
> >  [  ] Run built-in server  (unchecked)
> >
> > GWT  (defaults)
> >  Available Modules
> >   Application - com.test.gwt
> >
> > Arguments
> > Program Arguments
> >  -war C:\work\workspace\testproject\src\main\webapp -remoteUI $
> > {gwt_remote_ui_server_port}:${unique_id} -logLevel INFO -noserver -
> > startupUrlhttp://localhost:8080/testproject/index.html
> > com.test.gwt.Application
> >
> > When I set a breakpoint in my client code... it doesn't recognize that
> > the code is loaded.  I get this in the error console:
> >
> > Exception in thread "Code server for Application from Mozilla/5.0
> > (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100202 Firefox/
> > 3.5.8
> onhttp://localhost:8080/testproject/index.html?gwt.codesvr=localhost:9997
> > @ ;bm'fwKmW~\.LHz1" java.lang.RuntimeException:
> > java.util.concurrent.ExecutionException:
> > com.google.gwt.dev.shell.remoteui.Messag

Re: Google Plugin for Eclipse 1.3 Preview is now available

[Keith Platfoot]

Hi Andreas,

Hm, not sure why you're seeing that error.  Let me ask a few questions to
see if we can get to the bottom of this.

1. You set the WAR directory to 'src/main/webapp' via the Google > Web
Application project properties page, right?  Did you also uncheck the box
below that says 'Launch and deploy from this directory'?  This is necessary
because the 'src/main/webapp' directory is not a complete WAR directory
(WEB-INF/lib and WEB-INF/classes are empty, etc.).

2. Are you launching the project using the regular Run/Debug As > Web
Application shortcut?  Did you make sure to first delete any other Web
Application launch configurations associated with the project?

3. When you launch, you should be prompted to select the runtime WAR
directory.  Unless you're also using Eclipse for Java EE, you'll probably
want to first do a 'mvn clean package' and then select the exploded WAR in
'/target/-' as your runtime WAR.

4. When you launch, are you seeing the Development Mode view appear at the
bottom of your workspace, with a URL to open in your browser?  Does the URL
have a ?gwt.codesvr=x.x.x.x:9997 at the end?  Does your web browser have the
GWT Development Mode plugin installed? (the browser should load a page to
prompt you if it's not installed).

5. After you launch, what are the arguments in the generated launch
configuration?  One of the features of 1.3 is the ability to inspect/tweak
the arguments via the regular Arguments tab in the launch configuration
dialog.  Let me know what your exact argument set is.

Also: to see code changes reflected when you hit refresh, you'll need to get
the class files into your runtime WAR directory.  One simple way to do this
is by changing your build output path (probably just for src/main/java and
src/main/resources) to the WEB-INF/classes directory in your runtime WAR.
 This works, but it is a bit hacky.

Alternatively, you can convert your project into a Dynamic Web Project in
Eclipse for Java EE, which provides automatic refresh-on-change behavior out
of the box.  It also creates a staging WAR directory by default so you don't
have to use the exploded WAR under /target.  If you're interested in this
approach, I can send you detailed instructions (which will also appear in
our FAQs after 1.3 launch).

Keith

On Fri, Mar 12, 2010 at 8:19 AM, andreas wrote:

> Hi Keith,
>
> we are happy to test the preview version.
>
> We are using Maven and the gwt-maven-project layout for our projects.
> We loved the dependency management and also clear code structure
> coming along with Maven but ran in the same problem mentioned a lot
> before: we could not get Google Eclipse Plugin run with our projects.
>
> The first workaround was to use the gwt:run goal, which actually works
> fine and forget about GEP.
>
> Now I still wanted to find out if we can use that nice web application
> run configuration of GEP again with the preview release. So I
> installed it and set the "war/" folder to "src/main/webapp" and tried
> to run our project as a web application.
>
> It did not work and we got the error "project may need to be
> (re)compiled". I figured out that the launch configuration was missing
> all the generated js-files. When they are located in "src/main/webapp"
> it launches the web application, but apparently using the generated js-
> files. No changes to the java code are reflected upon refresh.
>
> Am I missing something in the setup process of the GEP preview
> version?
>
> On 4 Mrz., 01:25, Keith Platfoot  wrote:
> > Hi everyone,
> >
> > Last month, I announced some of the changes we had planned for the 1.3
> > version of the Google Plugin for Eclipse. To recap, this release is
> focused
> > on making life easier for developers using GWT/App Engine alongside
> > third-party tools, including Maven and Eclipse for Java EE. In my post, I
> > promised we'd let you download a preview of 1.3 to get some hands-on
> testing
> > of the new features and provide us with your feedback before the official
> > release.
> >
> > I'm happy to announce that the time has come. An early preview of 1.3 is
> now
> > available for download at the following URLs:
> >
> > http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.s...
> >
> > http://dl.google.com/eclipse/plugin/3.4/zips/com.google.gdt.eclipse.s...
> >
> > http://dl.google.com/eclipse/plugin/3.3/zips/com.google.gdt.eclipse.s...
> >
> > Note: Ensure that your version of Eclipse has Eclipse's Web Standard
> Tools
> > (WST) installed before installing the plugin. WST can be installed by
> > navigating to the Software Installation section, and selecting the the

Re: beta eclipse plugin - running in noserver mode with tomcat - having troubles

[Keith Platfoot]

Brian,

You're correct that your WEB-INF/lib should only require one
gwt-servlet.jar.  The others (gwt-user, gwt-soyc-vis) are only used at
compile-time, so there's no need to deploy them with your WAR file.

Also, using Tomcat with -noserver seems like the right approach to me.  It
certainly should be easier than trying to rig the embedded Jetty instance to
do what you want.

Keith

On Fri, Mar 12, 2010 at 1:06 PM, bkbonner  wrote:

> I suspect this is a classloader thing, but I'm not sure how to resolve
> it.
>
> when I run WTP tomcat server and look at the WEB-INF/lib directory
>
> I have:
>
> gwt-servlet-2.0.3.jar
> gwt-servlet.jar
> gwt-soyc-vis-2.0.3.jar
> gwt-user-2.0.3.jar
>
> Do all of these need to be there in the WAR?
>
> I thought only a single gwt-servlet had to be out there.   These are
> all out there because I'm using m2eclipse and these are defined to be
> exported in the Java EE Module section of the project preferences
> (what JARs are placed in WEB-INF/lib).
>
> I suspect this is part of the problem, but I can't say for certain.
>
> Brian
>
> On Mar 12, 10:13 am, bkbonner  wrote:
> > Hi, Keith.
> >
> > Yes, i was wondering if that was the case.  I hope that the plugin
> > just includes the -noserver configuration as part of it.
> >
> > The UIBinder error makes it seem like the xml code is not being
> > recognized by OOPHM when it's trying to run.
> >
> > Thanks for getting back to me.  I hope someone can give me some help
> > with this.  In the meantime, I've been using the plugin in a separate
> > project (no Maven or special config) and running it out of jetty and
> > it seems to work pretty well.
> >
> > Another option I have is to get things running in jetty -- are there
> > any tips on configuring the embedded jetty instance to support a
> > server -- or should I shy away from that?
> >
> > I'm looking for the fastest way to get up and running and it seemed
> > like it was to have my app running in tomcat and run the OOPHM using
> > jetty with -noserver.  Any advice would be appreciated.
> >
> > Brian
> >
> > On Mar 11, 2:41 pm, Keith Platfoot  wrote:
> >
> > > Brian,
> >
> > > I think the issues you were having with adding the -noserver argument
> to
> > > your launch configuration were probably the result of a known issue
> with the
> > > Eclipse plugin 1.3 preview (check the 1.3 announcement email for
> details).
> > >  This has since been fixed, so once 1.3 final is released (probably
> next
> > > week), this particular problem should be resolved.
> >
> > > Regarding the NoSuchFieldError exception: I have hit this same bug when
> > > using GWT with a Tomcat server in Eclipse for Java EE.  My solution was
> the
> > > same: moving the GWT dependencies to the top of the project's build
> > > classpath.  I'll investigate to see if there is something we can do to
> help
> > > prevent this problem.
> >
> > > As for the UiBinder errors, I probably would not be of much help there.
> > >  I'll forward this email to someone who's more knowledgeable about the
> > > subject.
> >
> > > Keith
> >
> > > On Wed, Mar 10, 2010 at 11:39 AM, bkbonner  >wrote:
> >
> > > > OK, it looks like the -noserver doesn't get injected into the debug
> > > > configuration based on any of the GWT Toolkit settings.   I don't
> have
> > > > it working yet, but I've tried:
> >
> > > > -remoteUI ${gwt_remote_ui_server_port}:${unique_id} -startupUrl
> > > >http://localhost:8080:/testproject/loganalyzer.html-logLevelINFO -
> > > > noserver -war C:\work\workspace-galileo\testproject\src\main\webapp
> > > > com.test.gwt.Application
> >
> > > > I get:
> >
> > > > 11:38:22.194 [ERROR] [Application] Failed to load module
> 'Application'
> > > > from user agent 'Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:
> > > > 1.9.1.8) Gecko/20100202 Firefox/3.5.8' at localhost:4767
> > > > java.lang.NoSuchFieldError:
> > > > reportUnusedDeclaredThrownExceptionIncludeDocCommentReference
> > > >at
> > > >
> com.google.gwt.dev.javac.JdtCompiler.getCompilerOptions(JdtCompiler.java:
> > > > 310)
> > > >at com.google.gwt.dev.javac.JdtCompiler
> > > > $CompilerImpl.(JdtCompiler.java:148)
> > > >at
> com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.

Re: Google Plugin for Eclipse 1.3 Preview is now available

[Keith Platfoot]

uot;Run As.." -> "Web
> Application" from GEP
>
> 3. I use Eclipse EE. On that first launch, I pointed the runtime WAR
> directory to the folder under "target" you mentioned. One thing I did
> not clearly understand: you said "unless you're also using Eclipse
> EE..."; well I do so where else should or could the runtime WAR
> directory point to? I also did a 'mvn clean package'.
>
> 4. Yes, yes and yes. The web application is displayed in the browser
> as expected.
>
> 5. Programm args:
> -remoteUI ${gwt_remote_ui_server_port}:${unique_id} -startupUrl
> index.html -logLevel INFO -port  -war /home/ahorst/workspace/
> GWTEntryApp/target/GWTEntryApp-0.0.1-SNAPSHOT
> de.se.proced.GWTEntryApp.Application
>
> VM args:
> -Xmx512m
>
> Working directory:
> /GWTEntryApp/target/GWTEntryApp-0.0.1-SNAPSHOT
>
> So far it all worked. Unfortunately the "refresh" code changes does
> not work. I set output folders of src/main/java and src/main/resources
> to the WEB-INF/classes inside the working directory. Did this through
> the build path configuration.
>
> Code changes are not reflected upon refresh; neither in the browser
> (F5) or by restarting the server in the Development view.
>
> Nevertheless when I launch the gwt:run goal, it works.
>
> Could it be a gwt-maven property that stops "refresh" code changes?
> Besides the GWT and Java version I did not change anything. I guess I
> have to stick to the gwt-maven docs to find out if the exploded WAR is
> not set properly.
>
> On 12 Mrz., 18:15, Keith Platfoot  wrote:
> > Hi Andreas,
> >
> > Hm, not sure why you're seeing that error.  Let me ask a few questions to
> > see if we can get to the bottom of this.
> >
> > 1. You set the WAR directory to 'src/main/webapp' via the Google > Web
> > Application project properties page, right?  Did you also uncheck the box
> > below that says 'Launch and deploy from this directory'?  This is
> necessary
> > because the 'src/main/webapp' directory is not a complete WAR directory
> > (WEB-INF/lib and WEB-INF/classes are empty, etc.).
> >
> > 2. Are you launching the project using the regular Run/Debug As > Web
> > Application shortcut?  Did you make sure to first delete any other Web
> > Application launch configurations associated with the project?
> >
> > 3. When you launch, you should be prompted to select the runtime WAR
> > directory.  Unless you're also using Eclipse for Java EE, you'll probably
> > want to first do a 'mvn clean package' and then select the exploded WAR
> in
> > '/target/-' as your runtime WAR.
> >
> > 4. When you launch, are you seeing the Development Mode view appear at
> the
> > bottom of your workspace, with a URL to open in your browser?  Does the
> URL
> > have a ?gwt.codesvr=x.x.x.x:9997 at the end?  Does your web browser have
> the
> > GWT Development Mode plugin installed? (the browser should load a page to
> > prompt you if it's not installed).
> >
> > 5. After you launch, what are the arguments in the generated launch
> > configuration?  One of the features of 1.3 is the ability to
> inspect/tweak
> > the arguments via the regular Arguments tab in the launch configuration
> > dialog.  Let me know what your exact argument set is.
> >
> > Also: to see code changes reflected when you hit refresh, you'll need to
> get
> > the class files into your runtime WAR directory.  One simple way to do
> this
> > is by changing your build output path (probably just for src/main/java
> and
> > src/main/resources) to the WEB-INF/classes directory in your runtime WAR.
> >  This works, but it is a bit hacky.
> >
> > Alternatively, you can convert your project into a Dynamic Web Project in
> > Eclipse for Java EE, which provides automatic refresh-on-change behavior
> out
> > of the box.  It also creates a staging WAR directory by default so you
> don't
> > have to use the exploded WAR under /target.  If you're interested in this
> > approach, I can send you detailed instructions (which will also appear in
> > our FAQs after 1.3 launch).
> >
> > Keith
> >
> > On Fri, Mar 12, 2010 at 8:19 AM, andreas  >wrote:
> >
> > > Hi Keith,
> >
> > > we are happy to test the preview version.
> >
> > > We are using Maven and the gwt-maven-project layout for our projects.
> > > We loved the dependency management and also clear code structure
> > > coming along with Maven but ran in the sam

Re: Google Plugin for Eclipse 1.3 Preview is now available

[Keith Platfoot]

@Andreas: Forgot to mention that if you're *not* using Eclipse for Java
EE, when you make changes to server-side code, you will also need to restart
GWT embedded Jetty instance.  For GWT 2.0+, click the Restart Server button
in the Development Mode view, or for older versions of GWT, the Reload
Server button on the Hosted Mode shell toolbar.

Keith

On Mon, Mar 15, 2010 at 2:27 PM, Keith Platfoot wrote:

> Hi Andreas,
>
> It looks like you're following the correct procedure, and you indicated
> that you were able to load the application in devmode, but you're not seeing
> code changes reflected when you Refresh the browser.  It might help if I
> explain briefly how changes are *supposed* to be reflected, and suggest a
> few ideas for things to check if refresh is not working:
>
> - Client-side code changes should *always* be reflected when you click
> Refresh in your browser during a devmode session, regardless of your source
> folders' build output paths.  This is because GWT devmode is actually using
> your .java source files, not the compiled .class files.  Double-check in
> your launch configuration's Classpath tab that your source folders appear at
> the top of the User Entries section.  If your gwt:run goal *does*correctly 
> reflect code changes in devmode when you Refresh, it would be
> useful to compare the devmode process arguments in that case to the devmode
> process created by the Eclipse launch configuration (you can find the
> arguments in Eclipse by right-click > Properties the "java" process in the
> stacktrace view in the Debug perspective).  Let me know if there are
> differences between the two sets of arguments.
>
> - Server-side code changes will only be reflected if the compiled .class
> files are propagated to your runtime WAR directory's WEB-INF/classes
> directory.  As you mentioned, one way to do this is to set your source
> folders' build output paths to your runtime WAR directory's WEB-INF/classes
> directory.  Of course, Eclipse must also be configured to build
> automatically (Project > Build Automatically).  If server-side code refresh
> is still not working, you might try making a change, and then manually
> verifying that the runtime WAR directory is getting the new .class file in
> WEB-INF/classes.
>
> - Changes to your HTML/CSS/other static resources will need to be mirrored
> in your runtime WAR directory (similar to server-side code changes).  I'm
> not aware of any out-of-the-box solution for this if you're using a standard
> Eclipse distribution (Eclipse Classic or Eclipse for Java developers).
>  You'll need to stop devmode, do another 'mvn clean package', and then
> launch devmode again.  However, if you're using Eclipse for Java EE, there
> is a way to configure it to automatically push WAR resource changes while
> devmode is running (this should answer your question in your #3 step).
>
> Basically, you start by converting your project into a Dynamic Web Project.
>  I don't know if you can automatically  migrate an existing project, but it
> should be possible to create a new Dynamic Web Project and then simply
> import your original project's source folders and build path entries.  Next,
> you'll need to configure the Eclipse project to use 'src/main/webapp' as
> your WAR directory instead of 'WebContent' (Eclipse default).  Close Eclipse
> and edit the file at:  root>/.settings/org.eclipse.wst.common.component.  Find the 
> element with a 'source-path' attribute of '/WebContent'.  Change the
> attribute value to '/src/main/webapp', save the file, and re-open Eclipse.
>  Now, when you start the project's configured server (Tomcat, Jetty, etc...
> define a server in the Servers view), Eclipse will automatically propagate
> changes in your source code and static resource files to your runtime WAR
> directory.  However, in Eclipse for Java EE, this runtime WAR directory will
> *not* be 'target/'.  Eclipse will instead create a staging
> directory in a temporary location (by default,
> /.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/)
> and *this* is the WAR directory you'll need to select when launching the
> Web Application launch configuration.  One more note: Eclipse for Java EE
> will also automatically push your updated .class files into
> /WEB-INF/classes, so no need to manually change your source folders'
> build output paths.
>
> Does that all make sense?  At launch, we'll be adding a couple new FAQ
> entries to our documentation to explain the process of using the Google
> plugin with Maven, with Eclipse for Java EE, and with both at once.
>  Hopefully my inst

Re: beta eclipse plugin - running in noserver mode with tomcat - having troubles

[Keith Platfoot]

tructor.java:494)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.ModuleSpace.rebindAndCreate(ModuleSpace.java:
> > > > > 422)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.GWTBridgeImpl.create(GWTBridgeImpl.java:39)
> > > > > at com.google.gwt.core.client.GWT.create(GWT.java:98)
> > > > > at
> com.test.gwt.client.Application.onModuleLoad(Application.java:
> > > > > 24)
> > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > > at
> > > > >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > > > > 39)
> > > > > at
> > > > >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
> > > > > 25)
> > > > > at java.lang.reflect.Method.invoke(Method.java:585)
> > > > > at
> com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:
> > > > > 369)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:
> > > > > 185)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:
> > > > > 380)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:
> > > > > 222)
> > > > > at java.lang.Thread.run(Thread.java:595)
> >
> > > > > 13:45:30.806 [ERROR] [Application] Unable to load module entry
> point
> > > > > class com.test.gwt.client.Application (see associated exception for
> > > > > details)
> > > > > java.lang.RuntimeException: Deferred binding failed for
> > > > > 'com.test.gwt.client.ActivityLogView' (did you forget to inherit a
> > > > > required module?)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.GWTBridgeImpl.create(GWTBridgeImpl.java:43)
> > > > > at com.google.gwt.core.client.GWT.create(GWT.java:98)
> > > > > at
> com.test.gwt.client.Application.onModuleLoad(Application.java:
> > > > > 24)
> > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > > at
> > > > >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > > > > 39)
> > > > > at
> > > > >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
> > > > > 25)
> > > > > at java.lang.reflect.Method.invoke(Method.java:585)
> > > > > at
> com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:
> > > > > 369)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:
> > > > > 185)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:
> > > > > 380)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:
> > > > > 222)
> > > > > at java.lang.Thread.run(Thread.java:595)
> > > > > Caused by: com.google.gwt.core.ext.UnableToCompleteException: (see
> > > > > previous log entries)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.ModuleSpace.rebindAndCreate(ModuleSpace.java:
> > > > > 449)
> > > > > at
> > > > >
> com.google.gwt.dev.shell.GWTBridgeImpl.create(GWTBridgeImpl.java:39)
> > > > > at com.google.gwt.core.client.GWT.create(GWT.java:98)
> > > > > at
> com.test.gwt.client.Application.onModuleLoad(Application.java:
> > > > > 24)
> > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > > at
> > > > >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > > > > 39)
> > > > > at
> > > > >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
> > > > > 25)
> > > > > at java.lang.reflect.Method.invoke(Method.java:585)
> > > > > at
> com

Re: Google plugin 1.3 preview and jar SDK

[Keith Platfoot]

Hi Mickaël,

Thanks for your feedback about the 1.3 preview of the Google Plugin for
Eclipse.

The 1.3 version does allow you to use the GWT jars from your Maven repo, but
as you discovered, it will not recognize the filenames if you try to add it
to the set of registered SDKs via the Google > GWT preference page.
 Instead, just add the jars directly to your project's build path and then
enable GWT for the project (project properties > Google > GWT). As of
version 1.3, the plugin will recognize the jars on your classpath as a valid
GWT SDK, even though they have been renamed.  In versions of the plugin
prior to 1.3, you would have seen an error that your project did not contain
any GWT SDK.

You may file a bug in the issue tracker if you feel that this behavior is
incorrect, since the official 1.3 release will work the same way regarding
that feature.

Keith


2010/3/15 LEDUQUE Mickaël 

> Hello,
> I tested the 1.3 preview for the plugin, and one of the nice new
> feature is the ability to use a gwt-user JAR instead.
> So I tried to use the gwt-user-2.0.3.jar file that is in my maven2
> local repository.
>
> But when I set "Installation drectory" to the good path in the "Add
> Google Web Toolkit SDK" dialog, all I get is
> /com/google/gwt/gwt-user/2.0.3/gwt-user.jar is missing.
>
> That's right because the name is gwt-user-2.0.3.jar, not gwt-user.jar.
>
> I think it'd be better to let the user configure jar name as well as
> path.
>
> Can I put an issue fin the issue tracker for a preview version ?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Google Plugin for Eclipse 1.3 is now available

[Keith Platfoot]

Hi everyone,

I'm happy to announce the release of version 1.3 of the Google Plugin for
Eclipse (http://code.google.com/eclipse).

This release is designed to make life easier for developers using GWT and/or
App Engine alongside third-party tools.  For example, we've taken the pain
out of using the plugin with projects built with the ever-popular Maven
build system: no more ugly hacks or workarounds, or polluted WEB-INF/lib
directories!  We've even added a new FAQ dedicated to Maven usage:
http://code.google.com/eclipse/docs/faq.html#gwt_with_maven.

We've also worked hard to make sure the plugin works well with Dynamic Web
projects in Eclipse for Java EE.  See the following FAQ for details on this
scenario:
http://code.google.com/eclipse/docs/faq.html#gwt_in_eclipse_for_java_ee.

In addition to improving third-party interoperability, we've also made the
plugin more customizable and robust overall.  Launch configurations now
allow direct editing of generated command line arguments, and a new
Errors/Warnings preference page lets you tweak the severity of any problem
marker we create.  We've also fixed a number of bugs related to App Engine
ORM enhancement.

To install the Google Plugin for Eclipse, you can find our update site URLs,
along with detailed instructions, here:
http://code.google.com/eclipse/docs/download.html

If you're upgrading from a previous version of the plugin, you may want to
consult our Upgrading the Plugin guide:
http://code.google.com/eclipse/docs/updating_the_plugin.html

*Note: If you installed the Google Plugin for Eclipse 1.3 Preview, be sure
to remove the relevant subfolders from your /dropins folder before
installing the official 1.3 release via the update site.*

*Enhancements*

   - Configurable WAR directory to allow better integration with Eclipse for
   Java EE and projects built with Maven
   - Web Application launch configurations now display and allow editing of
   generated Program and VM arguments
   - Errors/Warnings preference page for customizing the severity of any
   generated problem marker
   - Projects can reference GWT/App Engine SDKs directly via JARs instead of
   through SDK library
   - GWT+App Engine projects automatically configured for optimal caching

*Fixes*

   - GWT Issue 3583: Google Eclipse Plugin configuration is too strict
   - GWT Issue 3592: Eclipse plugin to add 'cache forever' configuration for
   new 'GWT + App Engine' projects
   - GWT Issue 3902: Allow users to configure the severity of problems
   reported by the eclipse plugin
   - App Engine Issue 1515: Eclipse plugin requires fixed location for war
   directory
   - App Engine Issue 2115: Using the @PersistenceAware annotation puts the
   Eclipse Enhancer in an Infinite Loop
   - App Engine Issue 1941: Plugin fails to enhance dependent classes on
   source level changes

For a complete list of fixed issues, see the GWT issue tracker and App
Engine issue tracker.

 We hope you enjoy using this new version of the Google Plugin for Eclipse
for all your GWT/App Engine development needs!  Let us know if you have
questions or run into any issues.  Thanks!

Keith, on behalf of the Google Plugin for Eclipse team

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Eclipse JavaEE tools + GWT Development mode

[Keith Platfoot]

Hi Neciu,

We just released the 1.3 version of the Google Plugin for Eclipse on
Tuesday, which should have a Google > Web Application project property page
with the WAR directory field.  Are you certain your plugin version is 1.3?

Keith

On Mon, Mar 15, 2010 at 3:41 PM, Neciu  wrote:

> Hi Keith,
>
> can you tell how to configure Eclipse + Google Plugin for Eclipse (the
> newest version), so I can debug my GWT project with DB connections?
> Your previous solution doesn't work anymore (I can't find anythig
> about WAR in "Web Application property").
>
> Thanks in advance,
> Neciu.
>
> On 18 Lut, 17:40, Keith Platfoot  wrote:
> > Hi Chris,
> >
> > Thanks for posting this.  It's a good explanation of how to get WTP and
> GPE
> > 1.2 working together, which is not a trivial task.  However, in the next
> > release of the plugin we're planning on making this integration a whole
> lot
> > easier<
> http://groups.google.com/group/google-web-toolkit/msg/8ff67143cce64e1...>
> > .
> >
> > With GPE 1.3, you'll be able to adapt an existing Dynamic Web Project as
> a
> > GWT project and debug using hosted/dev mode quite easily.  Here's a sneak
> > preview of how this will work in GPE 1.3:
> >
> > 1. In your project's Properties dialog, select Google > Web Toolkit and
> > check the box: *Use Google Web Toolkit*.
> >
> > 2. Switch to the Web Application property page and change *WAR source
> > directory* to "WebContent" and uncheck the box: *Also use this directory
> as
> > the output WAR directory.*
> > *
> > *
> > 3. Start your project's server (be it GlassFish, Tomcat, etc.) using your
> > configured WTP server adapter.
> >
> > 4. Create a new Web Application launch configuration.  On the Server tab,
> > uncheck: *Run built-in server* (since we want to use WTP's server
> adapter)
> > and on the GWT tab, change the -startupUrl argument to point to your
> server
> > (e.g.http://localhost:8080/WebApp)
> >
> > 5. Run/Debug your new launch configuration.  The first time you do this,
> > you'll have to select the location of the WAR directory WTP is publishing
> to
> > (this is configurable, but I think by default it is
> >
> /.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/).
> >
> > 6. Presto!  GWT hosted/dev mode is now running in your own server, and
> you
> > can debug either server-side or client-side code, and get automatic
> redeploy
> > of modified class files or static resources thanks to WTP's auto-publish
> > mechanism.
> >
> > We're going to be uploading a preview built of GPE 1.3 later this month
> so
> > you can try it out for yourself and let us know what you think, ahead of
> the
> > official release.  Stay tuned!
> >
> > Keith
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Google Plugin for Eclipse 1.3 Preview is now available

[Keith Platfoot]

Hi Andreas,

It looks like your GEP classpath is ok based on the contents of the
Classpath tab, but it would actually be more useful to look at the exact
launch arguments, to see if there are differences between that and "mvn
gwt:run".  When you launch using GEP, switch to the Debug perspective and
right-click the appropriate java process in the Debug view (it's the one
where stack traces show up while at a breakpoint).  Select Properties from
the context menu, and you should see the full argument list in the dialog
that appears.  Compare that to the command used by "mvn gwt:run".

Also, just to verify, when you are make code changes, are you changing the
source code for client-side code only (code accessible from a GWT module
entrypoint)?  Note that if you change any server-side code or static
resources, you'll have to perform additional configuration unless you're
using a Dynamic Web project in Eclipse for Java EE.

You may want to check out the new FAQ on GEP + Maven (+ Eclipse for Java EE,
optionally):

http://code.google.com/eclipse/docs/faq.html#gwt_with_maven

It contains better instructions for enabling refresh for client-side
code/server-side code/static resources than my previous message.

Keith

On Wed, Mar 17, 2010 at 6:22 AM, andreas wrote:

> Hi Keith,
>
> I'm looking for the classpath settings now. Here's what "mvn gwt:run"
> uses:
>
> /bin/sh -c /usr/lib/jvm/java-6-sun-1.6.0.15/jre/bin/java -Xmx512m -
> classpath "/home/ahorst/workspace/App/src/main/java":"/home/ahorst/
> workspace/App/src/main/resources":"/home/ahorst/workspace/App/war/WEB-
> INF/classes":"/home/ahorst/.m2/repository/com/google/gwt/gwt-servlet/
> 2.0.3/gwt-servlet-2.0.3.jar":"/home/ahorst/.m2/repository/com/google/
> gwt/gwt-user/2.0.3/gwt-user-2.0.3.jar":"/home/ahorst/.m2/repository/
> com/google/gwt/gwt-dev/2.0.3/gwt-dev-2.0.3.jar"
> com.google.gwt.dev.DevMode -war "/home/ahorst/workspace/App/war" -gen
> "/home/ahorst/workspace/App/target/.generated" -logLevel INFO -port
>  -startupUrl "com.my.example.App.Application/Application.html"
> com.my.example.App.Application
>
> While the run configuration of GEP lists the following entries:
>
> - Bootstrap Entries
>  - JRE System Library [JavaSE-1.6]
> - User Entries
>  - java - /App/src/main/
>  - resources - /App/src/main/
>  - java - /App/src/test/
>  - App (default classpath)
>- App
>- Maven Dependencies
>- GWT SDK [GWT - 2.0.3]
>
> The java source folder is the first entry, but no code changes
> reflected on refresh with the GEP run configuration. "mvn gwt:run"
> though does it. Are the Bootstrap Entries conflicting here?
>
> On 15 Mrz., 21:05, Keith Platfoot  wrote:
> > @Andreas: Forgot to mention that if you're *not* using Eclipse for Java
> > EE, when you make changes to server-side code, you will also need to
> restart
> > GWT embedded Jetty instance.  For GWT 2.0+, click the Restart Server
> button
> > in the Development Mode view, or for older versions of GWT, the Reload
> > Server button on the Hosted Mode shell toolbar.
> >
> > Keith
> >
> > On Mon, Mar 15, 2010 at 2:27 PM, Keith Platfoot  >wrote:
> >
> > > Hi Andreas,
> >
> > > It looks like you're following the correct procedure, and you indicated
> > > that you were able to load the application in devmode, but you're not
> seeing
> > > code changes reflected when you Refresh the browser.  It might help if
> I
> > > explain briefly how changes are *supposed* to be reflected, and suggest
> a
> > > few ideas for things to check if refresh is not working:
> >
> > > - Client-side code changes should *always* be reflected when you click
> > > Refresh in your browser during a devmode session, regardless of your
> source
> > > folders' build output paths.  This is because GWT devmode is actually
> using
> > > your .java source files, not the compiled .class files.  Double-check
> in
> > > your launch configuration's Classpath tab that your source folders
> appear at
> > > the top of the User Entries section.  If your gwt:run goal
> *does*correctly reflect code changes in devmode when you Refresh, it would
> be
> > > useful to compare the devmode process arguments in that case to the
> devmode
> > > process created by the Eclipse launch configuration (you can find the
> > > arguments in Eclipse by right-click > Properties the "java" process in
> the
> > > stacktrace view in the Debug perspective).  Let me know if there are
> > > differences between

Re: Google Plugin for Eclipse 1.3 ignores WTP web directory

[Keith Platfoot]

Hi Michail,

I've confirmed that this is a bug in 1.3: a directory browse dialog
*should*be appearing when you launch, to ask for a WAR directory.
However, it
appears that this only happens when you create a new launch configuration
from within the Run/Debug Configurations dialog.  If you delete the existing
launch configuration and then right-click the project and select Run As >
Web Application, you should see the WAR directory prompt as expected (at
least the first time... after that the -war argument should be persisted).

Also, regarding the use of relative WAR directory paths: the lastWarOutDir
setting is only used for convenience as an initial path when we display a
directory browse dialog for selecting the WAR directory.  If you want to
specify the WAR directory argument in a launch configuration as a
workspace-relative path, you should be able to use something like this:

-war ${workspace_loc}/path/to/war

However*,* I say *should* be able to, because unfortunately there is another
bug in 1.3 that prevents that variable from being resolved.

The good news is that* **we will release a fix tomorrow to resolve both of
these bugs*, as well as the auto-escaping bug on Windows (
http://code.google.com/p/google-web-toolkit/issues/detail?id=4762).

Keith

On Wed, Mar 17, 2010 at 6:53 AM, Michail Prusakov <
michail.prusa...@gmail.com> wrote:

> I've updated the plugin and while trying out the new stuff noticed
> that the plugin seems to ignore the web directory name.
>
> Here is what I've done: (for the record I am using eclipse galileo
> SR2)
> 1) created a wtp project with a default content directory (WebContent)
> 2) checked "Use Google Web Toolkit"
> 3) checked "This Project has a WAR directory", entered the name and
> unchecked "Launch and deploy from this directory"
> 4) saved the configuration and since I am using tomcat 6 as container,
> changed the order of the gwt library as it is written here:
>
> http://groups.google.com/group/google-web-toolkit/browse_thread/thread/98add5c7f6317fd5
> (BTW it would be great if the FAQ would mention it)
> 5) created a module, html page, entry class (all using wizards)
> 6) ran the project in tomcat
> 7) created a debug configuration (all according to
> http://code.google.com/eclipse/docs/faq.html#gwt_in_eclipse_for_java_ee)
>
> Now the funny thing is, the manual said that the plugin would ask for
> a destination, but it did not. Furthermore it created a war directory
> and as a result the project did not work. I've then ran the gwt
> compiler which did ask for the destination and compiled my project.
> After that everything worked perfectly.
>
> Even though the gwt compiler added a line lastWarOutDir= here> to the com.google.gwt.eclipse.core.prefs file in
> project's .settings directory, every time I lunch the project for some
> reason the plugin still creates the war directory.
>
> I've created another similar project. This time I've created a debug
> configuration with "Run built-in server" checked. The plugin did ask
> for the destination but still created the war directory.
>
> BTW would it be possible to allow lastWarOutDir to accept relative
> paths (relative to workspace that is)? We usually put the settings to
> source control so that only one person would have to go through all
> the setup process.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Problem in downloading Google Plugin for Eclipse

[Keith Platfoot]

Hi Sandeep,

The URLs are working, although it may not appear so if you navigate
directly to them in a web browser.  These URLs are Eclipse update
sites, which means you'll need to use Eclipse's update mechanism to
install the plugin.  See the documentation for Eclipse 3.3 (http://
code.google.com/eclipse/docs/install-eclipse-3.3.html) or Eclipse 3.4
(http://code.google.com/eclipse/docs/install-eclipse-3.4.html).

>From a web browser, these URLs will indeed produce a 404, even when
the update site is ok.  To test them from a browser, just tack on /
site.xml to the end of the URL, and you should see a short message
indicating that you're hitting the Google plugin update site.

Keith

On Apr 14, 3:56 am, "sandeepla...@gmail.com" 
wrote:
> Hello ,
>    I am trying to download Google Plug-in for Eclipse using below
> URLs , which seems not working.
>
> Eclipse 3.3 (Europa)http://dl.google.com/eclipse/plugin/3.3
> Eclipse 3.4 (Ganymede)http://dl.google.com/eclipse/plugin/3.4
>
> Both the URLs are not working.
>
> Can someone please provide guidelines to download this plug in  ?
>
> Thanks
> Sandeep S. Lawar

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: GWT eclipse plug manual install?

[Keith Platfoot]

GWT 1.6 download: http://code.google.com/webtoolkit/download.html

Keith

On Apr 15, 12:45 pm, gcr  wrote:
> All,
>
> I have looked and I cannot find a link from where I can download GWT
> 1.6 for a manual install.  (I could also be blind.)  Is there such a
> thing, or is it update site or nothing?
>
> I am trying to upgrade to GWT 1.6.  When I attempt to do so using the
> update site, It throws an error (see below).  Has anyone seen this
> kind of thing before?
>
> I have successfully upgraded two other machines.  It's only this third
> box that gives me trouble.  All three machines have eclipse 3.4 on
> WinXP.
>
> An error occurred while collecting items to be installed
>   Error closing the output stream for
> org.eclipse.datatools.sqldevtools.data.feature/
> org.eclipse.update.feature/1.6.2.v200810071455-3109oA55V589K5QA5 on
> repository file:/C:/Program Files/eclipse-ganymede/.
>   Error unzipping C:\DOCUME~1\groberts\LOCALS~1\Temp
> \org.eclipse.datatools.sqldevtools.data.feature_1.6.2.v200810071455-3109oA5 
> 5V589K5QA54838407210649109424.jar:
> Invalid zip file format
>   Problems downloading artifact:
> osgi.bundle,org.eclipse.datatools.sqltools.data.core,
> 1.1.0.v200901140930.
>     Exception connecting 
> tohttp://download.eclipse.org/datatools/downloads/drops/N_updates/plugi
>
> http://download.eclipse.org/datatools/downloads/drops/N_updates/plugi...
>     Exception connecting 
> tohttp://download.eclipse.org/datatools/downloads/drops/N_updates/plugi
>
> http://download.eclipse.org/datatools/downloads/drops/N_updates/plugi...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Compiling Error with using JPA & GWT

[Keith Platfoot]

Here's the documentation on organizing your GWT project structure:

http://code.google.com/webtoolkit/doc/1.6/DevGuideOrganizingProjects.html

Keith

On Apr 16, 4:38 am, Salvador Diaz  wrote:
> I think you're trying to use server-side code in the client-side of
> your application, do you understand how modules are structured and the
> difference between server-side code and client-side code in GWT ? If
> not, I suggest you read the GWT Documentation, which explains the
> whole of it pretty nicely.
>
> Salvador
>
> On Apr 16, 6:23 am, yyanghhong  wrote:
>
> > Hey
> > I got the following error when using JPA query, which module should I
> > put into GWT compiler class path?
>
> > Compiling module web.google.
> >      [java]    Refreshing module from source
> >      [java]       Validating newly compiled units
> >      [java]          Removing units with errors
> >      [java]             [ERROR] Errors in 'file:/ogle/client/EMF.java'
> >      [java]                [ERROR] Line 14: No source code is
> > available for type javax.persistence.EntityManagerFactory; did you
> > forget to inherit a required module?
> >      [java]                [ERROR] Line 15: No source code is
> > available for type javax.persistence.Persistence; did you forget to
> > inherit a required module?
> >      [java]    Compiling 5 permutations
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: GWT 1.6, Google App Engine, and java.awt.image.*

[Keith Platfoot]

Hi Danny,

It sounds like you've resolved the issue, but I'd like to reiterate
for any other users having problems.

GWT and App Engine work well together, but as Vitali mentioned, they
are orthogonal and can be used in isolation just as easily.  When
creating a new Web Application project using the Eclipse plugin, use
the checkboxes in the Google SDKs group to choose whether to support
GWT, App Engine, or both.  To configure existing projects, open
project properties and navigate to Google -> Web Toolkit or Google ->
App Engine to enable or disable that SDK for your project.

Keith

On Apr 22, 9:12 pm, Danny  wrote:
> Clarifying: I am using Java image classes on the server, where the
> Java sky should be almost limitless.  Right now, I would like to get
> my application of a few thousand lines of code working under GWT 1.6.
> It works great under GWT 1.5.  I took your advice and told Eclipse to
> not use App Engine, and Eclipse did stop complaining.  I hope this
> works in the end.
>
> Thanks,
>
> Danny
>
> On Apr 22, 8:15 pm, Ben FS  wrote:
>
> > Client-side: GWT lets you use Java language, but only a sub-set of the
> > J2SE library, supplemented by a variety of GWT-specific UI classes.
>
> > Server-side: You can use whatever you want, including Java. If you
> > wish to use Java (J2EE) on the server, you can - and then the GWT RPC
> > mechanism can be handy. If you wish to deploy to GAE, there are some
> > restrictions - for example, no file access - but the main difference
> > with GAE is how you store data persistently.
>
> > On Apr 22, 3:35 pm, Danny  wrote:
>
> > > I am trying to put my application under GWT 1.6, but I am having
> > > problems, because I use some java.awt.image classes.  I understand
> > > that Google is working on App Engine for java and has probably not yet
> > > implemented image.
>
> > > How can I proceed, since the new eclipse plugins insist on App Engine,
> > > even when I remove the App Engine SDK.
>
> > > Any suggestions?
>
> > > Danny
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: GWT Compile Project problem in Eclipse

[Keith Platfoot]

Hi Guidobot,

If I understand correctly, when you compile the project from either
the Eclipse toolbar button or from ant, the resulting application is
broken (pop-up doesn't work), but if you compile from the GWT hosted
browser, it does?  If this is the case, we need to figure out what is
going wrong with your Eclipse/ant compilations.  When you compile from
Eclipse, are there any error messages (or if you can try compiling
with log level INFO, is there a success message at the end)?

If the compilation in Eclipse appears to be completing successfully,
are you always using the same web browser when testing the compiled
application?  Also, could you clarify exactly what you mean by pop-
up?  Is this a native alert box, a GWT DialogBox or PopupPanel, or a
new browser window?

Keith

On Apr 29, 9:27 pm, Guidobot  wrote:
> Has anyone else had this problem?
>
> I compile a project from Eclipse, which works, but a browser does not
> show pop-up (running the JS).
>
> Oddly, all works fine if I Compile/Browse from the GWT host. On the
> otherhand, 'ant build' has a similar problem (it compiles but does not
> launch a browser).
>
> Feels like I'm missing some setting somewhere? Perhaps Vista related?
>
> Any sugestions would be much appreciated.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: GWT Compile Project problem in Eclipse

[Keith Platfoot]

Sorry Guidobot, I think I misunderstood your original question.  If
you were expecting the Eclipse button or ant to pop-up a browser
window at the end of compilation, then as Alex and Isaac pointed out,
this is a function of the GWT hosted browser only.  I apologize for
the confusion!

Keith

On Apr 29, 9:27 pm, Guidobot  wrote:
> Has anyone else had this problem?
>
> I compile a project from Eclipse, which works, but a browser does not
> show pop-up (running the JS).
>
> Oddly, all works fine if I Compile/Browse from the GWT host. On the
> otherhand, 'ant build' has a similar problem (it compiles but does not
> launch a browser).
>
> Feels like I'm missing some setting somewhere? Perhaps Vista related?
>
> Any sugestions would be much appreciated.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Google Plugin for Eclipse 1.3 ignores WTP web directory

[Keith Platfoot]

Hi José,

Thanks for the report.  We'll be updating the FAQs to include a note about
moving the GWT SDK above the Tomcat library to prevent the error you saw.

Keith

On Sat, Mar 20, 2010 at 6:30 AM, Pepe  wrote:

> I just tried the new 1.3.1 version and it works fine now.
>
> I got the following exception on the first try though
> java.lang.NoSuchMethodError:
>
> org.eclipse.jdt.internal.compiler.lookup.ProblemReferenceBinding.closestReferenceMatch()Lorg/
> eclipse/jdt/internal/compiler/lookup/ReferenceBinding;
>at com.google.gwt.dev.javac.JsniChecker
> $CheckingVisitor.findClass(JsniChecker.java:231)
>at com.google.gwt.dev.javac.JsniChecker
> $CheckingVisitor.checkRefs(JsniChecker.java:142)
>at com.google.gwt.dev.javac.JsniChecker
> $CheckingVisitor.endVisit(JsniChecker.java:65)
>at
>
> org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.traverse(MethodDeclaration.java:
> 247)
>at
>
> org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:
> 1337)
>at
>
> org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:
> 1206)
>at
>
> org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:
> 518)
>at com.google.gwt.dev.javac.JsniChecker.check(JsniChecker.java:350)
>at com.google.gwt.dev.javac.JsniChecker.check(JsniChecker.java:340)
>at
>
> com.google.gwt.dev.javac.CompilationUnitInvalidator.validateCompilationUnits(CompilationUnitInvalidator.java:
> 159)
>at
> com.google.gwt.dev.javac.CompilationState.compile(CompilationState.java:
> 198)
>at
> com.google.gwt.dev.javac.CompilationState.refresh(CompilationState.java:
> 178)
>at
> com.google.gwt.dev.javac.CompilationState.(CompilationState.java:
> 93)
>at
> com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:
> 264)
>at
> com.google.gwt.dev.cfg.ModuleDef.getTypeOracle(ModuleDef.java:325)
>at com.google.gwt.dev.SwtHostedModeBase
> $SwtBrowserWidgetHostImpl.createModuleSpaceHost(SwtHostedModeBase.java:
> 66)
>at
>
> com.google.gwt.dev.shell.ie.BrowserWidgetIE6$External.gwtOnLoad(BrowserWidgetIE6.java:
> 73)
>at
>
> com.google.gwt.dev.shell.ie.BrowserWidgetIE6$External.invoke(BrowserWidgetIE6.java:
> 161)
>at
> com.google.gwt.dev.shell.ie.IDispatchImpl.Invoke(IDispatchImpl.java:
> 294)
>at
> com.google.gwt.dev.shell.ie.IDispatchImpl.method6(IDispatchImpl.java:
> 194)
>at
> org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:
> 117)
>at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
>at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1925)
>at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2966)
>at
> com.google.gwt.dev.SwtHostedModeBase.processEvents(SwtHostedModeBase.java:
> 264)
>at
> com.google.gwt.dev.HostedModeBase.pumpEventLoop(HostedModeBase.java:
> 557)
>at com.google.gwt.dev.HostedModeBase.run(HostedModeBase.java:405)
>at com.google.gwt.dev.HostedMode.main(HostedMode.java:232)
>
> This was solved by changing the order of the GWT library as mentioned
> in point 4 in the original email. This should really be mentioned
> somewhere.
>
> Thank you
>
> /José
>
> On Mar 19, 5:11 pm, Zak  wrote:
> > Hi Keith-
> >
> > We're also hurtin from the absolute ${workspace_loc} path. Looking
> > forward to the fix!
> >
> > On Mar 18, 5:31 pm, Keith Platfoot  wrote:
> >
> > > Hi Michail,
> >
> > > I've confirmed that this is a bug in 1.3: a directory browse dialog
> > > *should*be appearing when you launch, to ask for a WAR directory.
> > > However, it
> > > appears that this only happens when you create a new launch
> configuration
> > > from within the Run/Debug Configurations dialog.  If you delete the
> existing
> > > launch configuration and then right-click the project and select Run As
> >
> > > Web Application, you should see the WAR directory prompt as expected
> (at
> > > least the first time... after that the -war argument should be
> persisted).
> >
> > > Also, regarding the use of relative WAR directory paths: the
> lastWarOutDir
> > > setting is only used for convenience as an initial path when we display
> a
> > > directory browse dialog for selecting the WAR directory.  If you want
> to
> > > specify the WAR directory argument in a launch configuration as a
> > 

Re: GWT 2.0.3 + Maven2 + Eclipse

[Keith Platfoot]

Hi Sergio,

Just wanted to mention that we've just released the 1.3.1 version of the
Google Plugin for Eclipse, which has much better interoperability with
GWT+Maven projects.  We even have a new FAQ dedicated to this scenario:

http://code.google.com/eclipse/docs/faq.html#gwt_with_maven

As of 1.3, it is easy to debug your Maven project's GWT code with a regular
Web Application launch configuration.  If you're using Eclipse for Java EE,
you can also get automatic refresh when your source code or static resources
(HTML, CSS, etc.) change.  Unlike previous versions of the Eclipse plugin,
you can now customize your project's configured WAR directory (e.g. set it
to 'src/main/webapp') and specify that it should be used as input-only (per
Maven convention).

Keith

On Mon, Mar 15, 2010 at 4:30 PM, Sergio  wrote:

> Hello everybody, I'm beginning with GWT development and I have a
> problem.
>
>  I've already configured Eclipse 3.5 with gwt plugin and m2eclipse
> plugin. I create a new maven project with gwt-maven-plugin archetype,
> but I'm not able to communicate client side with server side. I've
> read the same problem is happened other people but no solution.
>
> I'm trying to debug the sample application with gwt:debug goal and
> then "Run remote java application" in "Debug configuration". I don't
> know if I am doing anything wrong. Any idea?
>
> Thank you and sorry for my English.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT 2.0.3 + Maven2 + Eclipse

[Keith Platfoot]

That's great Will, glad you found my instructions useful!  Configuring Maven
+ GWT + Eclipse did take a little while to figure out, but the good news is
it's now *much* easier to use such a configuration with the Google Plugin
for Eclipse, as of version 1.3.

Keith

On Wed, Mar 24, 2010 at 11:25 AM, will0  wrote:

> I can confirm the instructions from Keith work. Thanks so much. I must
> have spent eight hours trying to figure this out.
>
> Will Temperley
>
> On Mar 23, 3:37 pm, Keith Platfoot  wrote:
> > Hi Bert,
> >
> > I converted the GWT starter app into a Maven project (see attachment),
> which
> > might serve as a good starting point for you.  It uses GWT 2.0.3,
> > gwt-maven-plugin 1.2, and Google Plugin for Eclipse 1.3.1.  I've also
> > included an Eclipse project and launch configuration.  To import the
> > project:
> >
> >- Ensure you have Eclipse for Java EE installed
> >- Create a server adapter for the project (right-click in Servers via
> and
> >select New).  I used Tomcat, which runs on port 8080 (this needs to be
> >reflected in the Web Application launch configuration)
> >- Create an M2_REPO classpath variable pointing to your Maven
> repository
> >(Preferences > Java > Build Path).
> >- Because the project references the GWT jars from the Maven repo
> instead
> >of a standard GWT SDK installation, you'll probably get a spurious
> error on
> >the project which you can suppress via Preferences > Google >
> >Errors/Warnings > Project structure and SDKs > Missing SDK.
> >
> > Keith
> >
> > On Wed, Mar 17, 2010 at 11:06 AM, Bert  wrote:
> > > I'm also very interested in setting up a Project like this.
> > > Any sample code from anyone?
> >
> > > On Mar 17, 1:44 am, zggame  wrote:
> > > > I think the latest gwt-maven-plugin is gwt 1.6.4.  Not 2.0.3
> >
> > > > On Mar 15, 3:30 pm, Sergio  wrote:
> >
> > > > > Hello everybody, I'm beginning with GWT development and I have a
> > > > > problem.
> >
> > > > >  I've already configured Eclipse 3.5 with gwt plugin and m2eclipse
> > > > > plugin. I create a new maven project with gwt-maven-plugin
> archetype,
> > > > > but I'm not able to communicate client side with server side. I've
> > > > > read the same problem is happened other people but no solution.
> >
> > > > > I'm trying to debug the sample application with gwt:debug goal and
> > > > > then "Run remote java application" in "Debug configuration". I
> don't
> > > > > know if I am doing anything wrong. Any idea?
> >
> > > > > Thank you and sorry for my English.
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google Web Toolkit" group.
> > > To post to this group, send email to
> google-web-tool...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-web-toolkit+unsubscr...@googlegroups.com
> 
> >
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-web-toolkit?hl=en.
> >
> >
> >
> >  MavenAppRpc.zip
> > 21KViewDownload
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: help integrating GWT project to an existing Web Project (on Tomcat) within Eclipse

[Keith Platfoot]

Hi aish,

Yes, this type of configuration is definitely possible.  However, as of
right now, using it with the current version of the Google Plugin for
Eclipse requires a few hacky workarounds.  The good news is that we're
releasing an update today or tomorrow (1.3.2) with a few surgical fixes that
will make the process more seamless.  After we release the new version, I'll
post back to this thread with instructions for setting up a multiple project
configuration (projects for client code, server code, and optionally shared
code).

Keith

On Tue, Mar 23, 2010 at 12:50 PM, aish sundar  wrote:

> I am a newbie to GWT and have some integrating a GWT project to an
> existing web project running on Tomcat within Eclipse. It will be
> great if any one of you can help out. Heres the scenario.
>
> 1) I have a separate GWT project I created using GWT plugin for
> Eclipse. Lets call it TestUI
> 2) I already have an existing web project within eclipse, called
> TestWeb, which runs on Tomcat6.0
> 3) Now I am somehow looking to integrate TestUI (in form of a war file
> or something) into TestWeb, so that I can get to the GWT UI pages
> through the tomcat server.
>
> Is this even feasible? Could you elaborate steps required to achieve
> #3 above?
>
> Thanks,
> aish
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: help integrating GWT project to an existing Web Project (on Tomcat) within Eclipse

[Keith Platfoot]

tall it.
   14. If all went well, you now have your GWT code running in development
   mode on top of your custom server.  You should be able to edit code in any
   of the 3 projects and have the changes reflected when you refresh your
   browser (server-side changes may not require a refresh but do take a few
   moments to propagate).
   15. Bonus step: To create a WAR file for deployment, you'll first need to
   compile FooClient to JavaScript.  Select the FooClient project and click the
   GWT Compile toolbar button.  Click Advanced and enter the following
   argument: -war /path/to/FooServer/WebContent and click Compile.  Once
   compilation finishes refresh the FooServer project.  You should see a new
   directory under WebContent containing the compiled JavaScript.  Now, select
   the FooServer project and select File > Export > Web > WAR file.

Hope folks find this useful, and let me know if I forgot any steps or
something does't work for you!

Keith

On Wed, Mar 24, 2010 at 3:11 PM, aish sundar  wrote:

> Thats sounds gr8!! Thanks a lot. will look out for the reply
>
> On Mar 24, 1:51 pm, Keith Platfoot  wrote:
> > Hi aish,
> >
> > Yes, this type of configuration is definitely possible.  However, as of
> > right now, using it with the current version of the Google Plugin for
> > Eclipse requires a few hacky workarounds.  The good news is that we're
> > releasing an update today or tomorrow (1.3.2) with a few surgical fixes
> that
> > will make the process more seamless.  After we release the new version,
> I'll
> > post back to this thread with instructions for setting up a multiple
> project
> > configuration (projects for client code, server code, and optionally
> shared
> > code).
> >
> > Keith
> >
> > On Tue, Mar 23, 2010 at 12:50 PM, aish sundar 
> wrote:
> > > I am a newbie to GWT and have some integrating a GWT project to an
> > > existing web project running on Tomcat within Eclipse. It will be
> > > great if any one of you can help out. Heres the scenario.
> >
> > > 1) I have a separate GWT project I created using GWT plugin for
> > > Eclipse. Lets call it TestUI
> > > 2) I already have an existing web project within eclipse, called
> > > TestWeb, which runs on Tomcat6.0
> > > 3) Now I am somehow looking to integrate TestUI (in form of a war file
> > > or something) into TestWeb, so that I can get to the GWT UI pages
> > > through the tomcat server.
> >
> > > Is this even feasible? Could you elaborate steps required to achieve
> > > #3 above?
> >
> > > Thanks,
> > > aish
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google Web Toolkit" group.
> > > To post to this group, send email to
> google-web-tool...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-web-toolkit+unsubscr...@googlegroups.com
> 
> >
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT 2.0.3 + Maven2 + Eclipse

[Keith Platfoot]

mcat 5.5.
> >
> > Is it known that hosted mode does not work for tomcat 5.5?
> >
> > And in my hosted mode I saw that theGWTcontents do not get loaded.
> > I only get the static text to display, not theGWTtextbox/Button.
> >
> > If I run a packaged version of the war in my tomcat, I do see theGWT
> > textbox/Button and I'm able
> > to perform the RPC call.
> >
> > Anyone familiar with this? Am I Missing some set-up for running the
> > hosted mode?
> >
> > On 23 mrt, 16:37, Keith Platfoot  wrote:
> >
> > > Hi Bert,
> >
> > > I converted theGWTstarter app into aMavenproject (see attachment),
> which
> > > might serve as a good starting point for you.  It usesGWT2.0.3,
> > >gwt-maven-plugin 1.2, and Google Plugin for Eclipse 1.3.1.  I've also
> > > included an Eclipse project and launch configuration.  To import the
> > > project:
> >
> > >- Ensure you have Eclipse for Java EE installed
> > >- Create a server adapter for the project (right-click in Servers
> via and
> > >select New).  I used Tomcat, which runs on port 8080 (this needs to
> be
> > >reflected in the Web Application launch configuration)
> > >- Create an M2_REPO classpath variable pointing to
> yourMavenrepository
> > >(Preferences > Java > Build Path).
> > >- Because the project references theGWTjars from theMavenrepo
> instead
> > >of a standardGWTSDK installation, you'll probably get a spurious
> error on
> > >the project which you can suppress via Preferences > Google >
> > >Errors/Warnings > Project structure and SDKs > Missing SDK.
> >
> > > Keith
> >
> > > On Wed, Mar 17, 2010 at 11:06 AM, Bert  wrote:
> > > > I'm also very interested in setting up a Project like this.
> > > > Any sample code from anyone?
> >
> > > > On Mar 17, 1:44 am, zggame  wrote:
> > > > > I think the latestgwt-maven-plugin isgwt1.6.4.  Not2.0.3
> >
> > > > > On Mar 15, 3:30 pm, Sergio  wrote:
> >
> > > > > > Hello everybody, I'm beginning withGWTdevelopment and I have a
> > > > > > problem.
> >
> > > > > >  I've already configured Eclipse 3.5 withgwtplugin and m2eclipse
> > > > > > plugin. I create a newmavenproject withgwt-maven-plugin
> archetype,
> > > > > > but I'm not able to communicate client side with server side.
> I've
> > > > > > read the same problem is happened other people but no solution.
> >
> > > > > > I'm trying to debug the sample application withgwt:debug goal and
> > > > > > then "Run remote java application" in "Debug configuration". I
> don't
> > > > > > know if I am doing anything wrong. Any idea?
> >
> > > > > > Thank you and sorry for my English.
> >
> > > > --
> > > > You received this message because you are subscribed to the Google
> Groups
> > > > "Google Web Toolkit" group.
> > > > To post to this group, send email to
> google-web-tool...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > google-web-toolkit+unsubscr...@googlegroups.com
> 
> >
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/google-web-toolkit?hl=en.
> >
> > >  MavenAppRpc.zip
> > > 21KWeergevenDownloaden
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: help integrating GWT project to an existing Web Project (on Tomcat) within Eclipse

[Keith Platfoot]

Hi aish,

After you start Tomcat, see if the runtime WAR directory (the one specified
with -war argument in your GWT launch configuration) has the
GreetingService.class file under /WEB-INF/classes/com/foo/client.  If
it's not there, that would explain the ClassNotFoundException.  Then the
only question is how to get it there.

Your configuration as you described it sounds correct.  GreetingService
should be copied into FooServer's WEB-INF/classes by means of it being
declared an Java EE module dependency.  FooServer also needs gwt-servlet.jar
as a module dependency, but if you were missing that you would get a
different error.

If you can't make any headway getting things to work, I could probably zip
up my sample projects and you could try importing those.  Just let me know.

Keith

On Wed, Mar 31, 2010 at 2:55 PM, aish sundar  wrote:

> Thanks Keith. The steps seemed a lot clearer now and I followed it to
> set uo my workspace exactly as yours. Now when I start the Tomcat
> server, launch the client in DEV mode and go to
> http://localhost:8080/TestWeb,
> everything loads up fine and I get to the client HTML page alright.
> However when I click a button, which is tied to an Asynchronous RPC
> call, I get the following exception :
>
> SEVERE: Allocate exception for servlet greetServlet
> java.lang.ClassNotFoundException: com.foo.client.GreetingService
>at java.net.URLClassLoader$1.run(Unknown Source)
>at java.security.AccessController.doPrivileged(Native Method)
>at java.net.URLClassLoader.findClass(Unknown Source)
>at java.lang.ClassLoader.loadClass(Unknown Source)
>at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
>at java.lang.ClassLoader.loadClass(Unknown Source)
>at java.lang.ClassLoader.loadClassInternal(Unknown Source)
>at java.lang.ClassLoader.defineClass1(Native Method)
>at java.lang.ClassLoader.defineClass(Unknown Source)
>at java.security.SecureClassLoader.defineClass(Unknown Source)
>at java.net.URLClassLoader.defineClass(Unknown Source)
>at java.net.URLClassLoader.access$000(Unknown Source)
>at java.net.URLClassLoader$1.run(Unknown Source)
>at java.security.AccessController.doPrivileged(Native Method)
>at java.net.URLClassLoader.findClass(Unknown Source)
>at java.lang.ClassLoader.loadClass(Unknown Source)
>at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
>at java.lang.ClassLoader.loadClass(Unknown Source)
>at
>
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:
> 1275)
>at
>
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:
> 1206)
>at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:
> 1083)
>at
> org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:
> 806)
>at
>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:
> 129)
>at
>
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:
> 175)
>at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:
> 128)
>at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:
> 102)
>at
>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:
> 109)
>at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:
> 286)
>at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:
> 844)
>at org.apache.coyote.http11.Http11Protocol
> $Http11ConnectionHandler.process(Http11Protocol.java:583)
>at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:
> 447)
>at java.lang.Thread.run(Unknown Source)
>
> The synchronous version of the GreetingService is in com.foo.client
> package within the FooShared project(just as you have mentioned). I
> have also added FooShared as a proj dependancy of FooClient and a
> module dependency of FooServer.
>
> NOTE: I did not do Step 15 in your instructions i.e., haven't really
> created a WAR file for deployment yet. Its all running locally.
>
> The error message is not very helpful as well, in terms of when and
> where was the exception thrown. any idea what could have caused it.
>
> Thanks,
> aish
>
> On Mar 30, 1:51 pm, Keith Platfoot  wrote:
> > Hi aish,
> >
> > 1) Yes, FooServer would be your existing Dynamic Web project (TestWeb).
> >  This project should include anything in the .server package of your GWT
> app
> > (e.g. GreetingServerImpl) as well as any existing s

Re: help integrating GWT project to an existing Web Project (on Tomcat) within Eclipse

[Keith Platfoot]

Hi aish,

1. Ah, it looks like I was mistaken: it is correct that you are not seeing
the com/foo/server folder in your runtime WAR directory's WEB-INF/classes
directory.  Eclipse does not actually push class files from dependent
projects into WEB-INF/classes, but rather, creates a jar and pushes that to
WEB-INF/lib.  So, check /WEB-INF/lib for FooShared.jar, which
should contain the compiled classes from FooShared.  If the jar is missing,
or does not have the expected class files, then something is probably wrong
with the configuration of your FooShared project.

2. Your WEB-INF folder inside FooServer is correct.  The WAR folder inside
your project (WebContent by default) should only contain input files and
resources: HTML, JSP, CSS, etc.).  Eclipse will take care of populating the
WEB-INF/lib and WEB-INF/classes of your runtime WAR directory (or exported
WAR file) automatically, based on your Java EE module dependencies.  No need
to create an ant task to do so manually.

I can zip up my Foo* projects and upload them here, if it would help get you
going.

Keith

On Mon, Apr 5, 2010 at 12:34 PM, aish sundar  wrote:

> Hey Keith,
>
> I am seeing a couple of things off here.
>
> 1. after I start Tomcat, I do not see "client" folder under the war
> directory "/WEB-INF/classes/com/foo/". I just see the "server"
> folder there. Do you know how to get the client there? I have added
> FooShared as a Java EE module dependency of FooServer. The -war
> argument in the GWT launch config is set to  workspace>/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/
> wtpwebapps/FooServer.
>
> 2. Another thing I noticed is that the WEB-INF folder within FooServer
> does not have any 'classes' folder within it. All it has is
>   (i) lib folder
>   (ii) web.xml
>
>  As I said, I have added FooShared as a Java EE module dependency of
> FooServer. Should we create a build.xml for FooServer (or some other
> procedure) to copy all the client and shared classes manually into
> WebContent/WEB-INF of FooServer?
>
> Thanks,
> Aishwarya
>
> On Apr 2, 2:39 pm, Keith Platfoot  wrote:
> > Hi aish,
> >
> > After you start Tomcat, see if the runtime WAR directory (the one
> specified
> > with -war argument in your GWT launch configuration) has the
> > GreetingService.class file under /WEB-INF/classes/com/foo/client.
>  If
> > it's not there, that would explain the ClassNotFoundException.  Then the
> > only question is how to get it there.
> >
> > Your configuration as you described it sounds correct.  GreetingService
> > should be copied into FooServer's WEB-INF/classes by means of it being
> > declared an Java EE module dependency.  FooServer also needs
> gwt-servlet.jar
> > as a module dependency, but if you were missing that you would get a
> > different error.
> >
> > If you can't make any headway getting things to work, I could probably
> zip
> > up my sample projects and you could try importing those.  Just let me
> know.
> >
> > Keith
> >
> > On Wed, Mar 31, 2010 at 2:55 PM, aish sundar  wrote:
> > > Thanks Keith. The steps seemed a lot clearer now and I followed it to
> > > set uo my workspace exactly as yours. Now when I start the Tomcat
> > > server, launch the client in DEV mode and go to
> > >http://localhost:8080/TestWeb,
> > > everything loads up fine and I get to the client HTML page alright.
> > > However when I click a button, which is tied to an Asynchronous RPC
> > > call, I get the following exception :
> >
> > > SEVERE: Allocate exception for servlet greetServlet
> > > java.lang.ClassNotFoundException: com.foo.client.GreetingService
> > >at java.net.URLClassLoader$1.run(Unknown Source)
> > >at java.security.AccessController.doPrivileged(Native Method)
> > >at java.net.URLClassLoader.findClass(Unknown Source)
> > >at java.lang.ClassLoader.loadClass(Unknown Source)
> > >at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
> > >at java.lang.ClassLoader.loadClass(Unknown Source)
> > >at java.lang.ClassLoader.loadClassInternal(Unknown Source)
> > >at java.lang.ClassLoader.defineClass1(Native Method)
> > >at java.lang.ClassLoader.defineClass(Unknown Source)
> > >at java.security.SecureClassLoader.defineClass(Unknown Source)
> > >at java.net.URLClassLoader.defineClass(Unknown Source)
> > >at java.net.URLClassLoader.access$000(Unknown Source)
> > >at java.net.URLClassLoader$1.run(Unknown Source)
&

Re: Eclipse JavaEE tools + GWT Development mode

[Keith Platfoot]

Hi Eric,

Hm, I'm not really sure about that error.  Is it possible to use another
parser rather than the Oracle Parser?  Also, are there DTD references in
your module file?  The error mentions a missing
http://apache.org/xml/features/nonvalidating/load-external-dtd feature,
which might only be an problem if you actually have references to external
DTD's in your XML.  Just a guess.

Keith

On Mon, Apr 5, 2010 at 10:22 PM, ekr  wrote:

> Hi Keith,
>
> I'm very encouraged - I was able to get my existing project updated
> using Google -> Web Application properties and the Web Toolkit
> properties. I'm using GWT 2.0.3 and Google Plugin for Eclipse 3.5 -
> 1.3.2.v201003242055.  I have a manual build (Ant) working with a
> Dynamic Web Project with a WebContent directory.
>
> Now the GWT Compile Project recognizes the project but when I try to
> run it I have a problem. I'm using OC4J 10.1.3.5.0 which includes the
> Oracle Parser which doesn't like the feature. Any Ideas?
>
> Thanks, Eric
>
> [ERROR] Failure while parsing XML
> org.xml.sax.SAXNotRecognizedException:
> http://apache.org/xml/features/nonvalidating/load-external-dtd
>at
> oracle.xml.jaxp.JXSAXParserFactory.setFeature(JXSAXParserFactory.java:
> 128)
>at com.google.gwt.dev.util.xml.ReflectiveParser
> $Impl.parse(ReflectiveParser.java:320)
>at com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access
> $100(ReflectiveParser.java:48)
>at
> com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:
> 398)
>at
> com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:
> 257)
>at
> com.google.gwt.dev.cfg.ModuleDefLoader$1.load(ModuleDefLoader.java:
> 169)
>at
> com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:
> 283)
>at
>
> com.google.gwt.dev.cfg.ModuleDefLoader.loadFromClassPath(ModuleDefLoader.java:
> 141)
>at com.google.gwt.dev.Compiler.run(Compiler.java:184)
>at com.google.gwt.dev.Compiler$1.run(Compiler.java:152)
>at
> com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:
> 87)
>at
>
> com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:
> 81)
>at com.google.gwt.dev.Compiler.main(Compiler.java:159)
> [ERROR] Unexpected error while processing XML
> com.google.gwt.core.ext.UnableToCompleteException: (see previous log
> entries)
>at com.google.gwt.dev.util.xml.ReflectiveParser
> $Impl.parse(ReflectiveParser.java:351)
>at com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access
> $100(ReflectiveParser.java:48)
>at
> com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:
> 398)
>at
> com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:
> 257)
>at
> com.google.gwt.dev.cfg.ModuleDefLoader$1.load(ModuleDefLoader.java:
> 169)
>at
> com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:
> 283)
>at
>
> com.google.gwt.dev.cfg.ModuleDefLoader.loadFromClassPath(ModuleDefLoader.java:
> 141)
>at com.google.gwt.dev.Compiler.run(Compiler.java:184)
>at com.google.gwt.dev.Compiler$1.run(Compiler.java:152)
>at
> com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:
> 87)
>at
>
> com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:
> 81)
>at com.google.gwt.dev.Compiler.main(Compiler.java:159)
>
>
> On Mar 18, 8:33 am, Keith Platfoot  wrote:
> > Hi Neciu,
> >
> > We just released the 1.3 version of the Google Plugin for Eclipse on
> > Tuesday, which should have a Google > Web Application project property
> page
> > with the WAR directory field.  Are you certain your plugin version is
> 1.3?
> >
> > Keith
> >
> >
> >
> > On Mon, Mar 15, 2010 at 3:41 PM, Neciu  wrote:
> > > Hi Keith,
> >
> > > can you tell how to configure Eclipse + Google Plugin for Eclipse (the
> > > newest version), so I can debug my GWT project with DB connections?
> > > Your previous solution doesn't work anymore (I can't find anythig
> > > about WAR in "Web Application property").
> >
> > > Thanks in advance,
> > > Neciu.
> >
> > > On 18 Lut, 17:40, Keith Platfoot  wrote:
> > > > Hi Chris,
> >
> > > > Thanks for posting this.  It's a good explanation of how to get WTP
> and
> > > GPE
> > > > 1.2 working together, which is not a trivial task.  However, in the
> next
> > &

Re: customize new web application wizard

[Keith Platfoot]

Not at this time.  We have discussed adding more options to the New Web
Application Project wizard in the future, but for now your best bet is to
generate the project with the wizard and then tweak the artifacts as needed.
Keith

On Wed, Jul 15, 2009 at 12:30 PM, goose  wrote:

>
> Is it possible to customize the gwt new Web Application Project wizard
> in eclipse 3.4? Things to customize might be the content of the host
> web page html or the default build path and libraries.
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Stack overflow at line :0 (Hosted mode memory error)

[Keith Platfoot]

Hi Trevis,
If you're getting a stack overflow, you could try increasing the Java stack
size using the -xss JVM argument.  In Eclipse, open the launch
configurations dialog (Run -> Run Configurations...) and select your launch
configuration from the tree on the left.  Then switch to the Arguments tab
and in the VM arguments field, add something like:

-Xss512k

This increases your stack size from the default (128k) to 512k.

Let me know if that doesn't work for you...

Keith

On Tue, Jul 28, 2009 at 10:28 AM, Trevis  wrote:

>
> I've been developing in GWT for about 3 weeks now. At first i just
> wanted to get my feet wet and maybe port a minor dynamic piece of my
> site to GWT but i'm so blown away by the technology that i'm
> considering a full UI port.
>
> So far the one issues that i can not seem to resolve is this "Stack
> overflow at line :0" popup message that happens when i launch the code
> in hosted mode.  I know that i'm not the only one who has the problem
> and i've seen blog posts where people talk about having resolved it by
> modifying the memory settings that it uses but nothing seems to work
> for me.
>
> I'm using Eclipse and have seen this message with GWT 1.6 and 1.7.
> The hosted browser takes a long time to render my content and then i
> get that popup.  It works fine if i compile it and hit it with a real
> browser.  It seems strange to me that the popup says "Microsoft
> Internet Explorer" but i guess that's what's being launched
> internally.  How do i make this go away?
>
>
>
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Eclipse plugin: Run As -> Web Application

[Keith Platfoot]

Hi Philip,
The Google Eclipse Plugin is not entirely compatible with Maven, so I
suspect the interaction between the two plugins may be the source of your
troubles.  Is it possible to create another GWT project which does *not* use
the Maven plugin, and see if you run into similar problems?  Let me know
what you find.

Keith

On Wed, Aug 5, 2009 at 10:54 AM, pgraham wrote:

>
> Hi all,
>
> I'm having some problems running my gwt projects in hosted mode using
> the Run As -> Web Application option from within eclipse.
>
> For starters, I'm running eclipse 3.5 with the maven plugin as well as
> the google plugin.
>
> The first problem I have is the following exception:
>
> Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load
> library: $M2_REPO/com/google/gwt/gwt-dev-linux/1.7.0/libswt-pi-
> gtk-3235.so
>at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1650)
>at java.lang.Runtime.load0(Runtime.java:769)
>at java.lang.System.load(System.java:968)
>at org.eclipse.swt.internal.Library.loadLibrary(Library.java:132)
>at org.eclipse.swt.internal.Callback.(Callback.java:36)
>at org.eclipse.swt.widgets.Display.createDisplay(Display.java:807)
>at org.eclipse.swt.widgets.Display.create(Display.java:781)
>at org.eclipse.swt.graphics.Device.(Device.java:145)
>at org.eclipse.swt.widgets.Display.(Display.java:452)
>at org.eclipse.swt.widgets.Display.(Display.java:443)
>at org.eclipse.swt.widgets.Display.getDefault(Display.java:1522)
>at
> com.google.gwt.dev.SwtHostedModeBase.(SwtHostedModeBase.java:
> 93)
>at com.google.gwt.dev.HostedMode.(HostedMode.java:271)
>at com.google.gwt.dev.HostedMode.main(HostedMode.java:230)
>
> * The actual error message has the full path to the file instead of
> $M2_REPO but changing the path to the repository in my maven
> settings.xml file changes the path of the error message.
>
> I can fix this problem by putting the file it can't find from a gwt
> download to the path it's looking for, but I don't understand why it's
> even looking for the file there in the first place since it's part of
> the gwt sdk that I have configured for my project.
>
> NOTE: Once I put the libswt-pi-gtk-3235.so file where it's being
> looked for, I also have to do the same thing with mozilla-hosted-
> browswer.conf, mozilla-1.7.12 (directory), libswt-gtk-3235.so, libswt-
> mozilla-gtk-3235.so and libgwt-ll.so
>
> Any help on this would be appreciated,
> Thanks
>
> Philip
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Eclipse plugin: Run As -> Web Application

[Keith Platfoot]

Hi Philip,
Hm, ok.  I'm not sure, but it's possible that your project may have some
classpath configuration issues that are causing this.  Would you be able to
send me your .classpath file (located in the project's root directory)?  I
can take a look and see if anything appears problematic.  Alternatively, if
you like you could actually send the entire project and I can try to see if
I can reproduce the error here.

Keith

On Wed, Aug 5, 2009 at 3:34 PM, Philip Graham <
philip.robert.gra...@gmail.com> wrote:

>
> Hi Keith,
>
> I've copied one of my projects and stripped it down to the bare
> minimum, removed it's pom file, imported it as a normal Java project
> and set it up to use GWT.  When I try and run I get a similar error:
>
> Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load
> library: $PROJECT_HOME/war/WEB-INF/lib/libswt-pi-gtk-3235.so
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1650)
>at java.lang.Runtime.load0(Runtime.java:769)
>at java.lang.System.load(System.java:968)
>at org.eclipse.swt.internal.Library.loadLibrary(Library.java:132)
> at org.eclipse.swt.internal.gtk.OS.(OS.java:22)
>at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63)
>at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54)
>at org.eclipse.swt.widgets.Display.(Display.java:126)
>at
> com.google.gwt.dev.SwtHostedModeBase.(SwtHostedModeBase.java:82)
> (*$PROJECT_HOME displays as the actual path to where the project is on
> my filesystem)
>
> If I copy the files I described in my original message into
> $PROJECT_HOME/war/WEB-INF/lib/ then it runs ok.
>
> This is not a huge deal since I can get things running but I
> appreciate any help you can give as it is a little bit annoying.
>
> Thanks,
> Philip
>
>
>
> On Wed, Aug 5, 2009 at 1:26 PM, Keith Platfoot
> wrote:
> > Hi Philip,
> > The Google Eclipse Plugin is not entirely compatible with Maven, so I
> > suspect the interaction between the two plugins may be the source of your
> > troubles.  Is it possible to create another GWT project which does not
> use
> > the Maven plugin, and see if you run into similar problems?  Let me know
> > what you find.
> > Keith
> >
> > On Wed, Aug 5, 2009 at 10:54 AM, pgraham  >
> > wrote:
> >>
> >> Hi all,
> >>
> >> I'm having some problems running my gwt projects in hosted mode using
> >> the Run As -> Web Application option from within eclipse.
> >>
> >> For starters, I'm running eclipse 3.5 with the maven plugin as well as
> >> the google plugin.
> >>
> >> The first problem I have is the following exception:
> >>
> >> Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load
> >> library: $M2_REPO/com/google/gwt/gwt-dev-linux/1.7.0/libswt-pi-
> >> gtk-3235.so
> >>at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1650)
> >>at java.lang.Runtime.load0(Runtime.java:769)
> >>at java.lang.System.load(System.java:968)
> >>at org.eclipse.swt.internal.Library.loadLibrary(Library.java:132)
> >>at org.eclipse.swt.internal.Callback.(Callback.java:36)
> >>at
> org.eclipse.swt.widgets.Display.createDisplay(Display.java:807)
> >>at org.eclipse.swt.widgets.Display.create(Display.java:781)
> >>at org.eclipse.swt.graphics.Device.(Device.java:145)
> >>at org.eclipse.swt.widgets.Display.(Display.java:452)
> >>at org.eclipse.swt.widgets.Display.(Display.java:443)
> >>at org.eclipse.swt.widgets.Display.getDefault(Display.java:1522)
> >>at
> >> com.google.gwt.dev.SwtHostedModeBase.(SwtHostedModeBase.java:
> >> 93)
> >>at com.google.gwt.dev.HostedMode.(HostedMode.java:271)
> >>at com.google.gwt.dev.HostedMode.main(HostedMode.java:230)
> >>
> >> * The actual error message has the full path to the file instead of
> >> $M2_REPO but changing the path to the repository in my maven
> >> settings.xml file changes the path of the error message.
> >>
> >> I can fix this problem by putting the file it can't find from a gwt
> >> download to the path it's looking for, but I don't understand why it's
> >> even looking for the file there in the first place since it's part of
> >> the gwt sdk that I have configured for my project.
> >>
> >> NOTE: Once I put the libswt-pi-gtk-3235.so file where i

Re: eclipse plugin and j2ee

[Keith Platfoot]

Hi Hank,
It should be possible to use GWT and the Eclipse plugin with a J2EE project.
 You said if you create the project as a dynamic web project, some GWT
modules fail.  By "GWT modules", do you mean GWT functionality within the
plugin, or "modules" as defined by
GWT?
 The Eclipse plugin does support enabling GWT for an existing project, as
long as your project has a 'war' directory.  I'm not sure about going in the
other direction, though: creating the project as a Web Application project
and then enabling J2EE features on it (such as associating it with a Tomcat
server).  Could you elaborate a bit on what sort of failures you're seeing?

Depending on your setup, the integration might be easier if you are willing
to use 2 projects, one with your GWT code and one with your JSPs and server
code.  GWT supports debugging against a separate backend, so it should
be able to run/debug GWT code alongside your JSPs hosted by Tomcat.

You'll need to do is start the Tomcat server first (debug or run mode should
be fine).  Then in your Google Web Application launch config, uncheck the
box on the Main tab labelled 'Run built-in server' and change the URL in the
GWT tab to the address of your Tomcat server.  When you start the Web
Application launch configuration, the GWT hosted mode shell will hit your
Tomcat server, but still provide full debugging functionality for your GWT
code.

If you can let me know more about your application setup and more details
about the problems you're running into, we'll see if we can get something
figured out.  Thanks,

Keith

On Wed, Aug 12, 2009 at 9:00 AM, Hank  wrote:

>
> We're in the process of migrating a large application (well, a
> collection of applications, really -- we're decomposing a very big
> webapp along business process lines) from jsp/tomcat with a little bit
> of ajax to all-gwt, and are having difficulty setting things up in
> eclipse.  If we set the project up as a dynamic web project, some gwt
> modules fail in various ways.  If (and this is what we prefer) we set
> the project up as a gwt project, there doesn't seem to be any way to
> associate the project with tomcat.  What we'd like to be able to do is
> to run/test/debug gwt in the normal way and also run/test/debug
> conventional jsp's on a local tomcat from within the same project.
> This because we're trying to move incrementally -- convert/integrate
> one bit of an application, then the next, then the next, repeat until
> done.
>
> Ideally, we'd also be able to transparently deploy gwt modules to the
> local tomcat and run/test/debug gwt integrated with the jsp's.  Am I a
> cockeyed optimist, or is this feasible?
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: using gwt in dynamic web project uin eclipse

[Keith Platfoot]

Hi,
If you're using the Eclipse plugin , you
should be able to enable GWT for an existing web project.  Take a look at
this page in the plugin documentation:

http://code.google.com/eclipse/docs/existingprojects.html

This recent Groups thread might also help you:

http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/cfca25b211dd81d2/da229a147fe24ac3

Let me know if you run into specific problems we can help you with.

Keith

On Wed, Aug 12, 2009 at 9:22 AM, aseem  wrote:

>
> hey
> Iam working on a dynamic web project and needed to use gwt for some
> applications in my project. Can anyone help me as to how can i
> integrate gwt application in my project.
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: hosted mode debugging with -noserver in eclipse

[Keith Platfoot]

Hi Mike,
I think your issue has to do with certain changes made to GWT in version
1.6.  Before 1.6, the GWTShell class was used to launch applications in
hosted mode.  In 1.6, the default structure of GWT projects was changed to
make it more similar to Java web apps.  By convention, GWT projects now
assume the existence of a directory named "war" which contains the contents
of the deployed WAR file.  This includes source files, such as your web.xml
and any public HTML pages.  The WAR directory also contains subdirectories
with the compiled JavaScript output of each GWT module.  In 1.6 and later a
new class, HostedMode, replaces the older GWTShell as the default class for
launching hosted mode.

The plugin supports GWT versions both older and newer than 1.6.  It uses
some heuristics to determine whether to launch applications with the
GWTShell or HostedMode class.  It sounds like in your case, you are able to
use HostedMode from the command line, but when you launch from Eclipse, the
plugin is using GWTShell... is that correct?

If so, I have two follow-up questions.  First, does your project contain a
WAR directory named "war"?  I know that many maven users use a different
naming convention, but as of right now, the plugin does *not* support
configuring the name of the WAR directory (it must be "war").  If yours is
named differently, your best bet might be to try to create a symlink named
"war" pointing to your actual WAR folder.  I haven't actually tested that
scenario, but it *should* work.

Once your project has a proper "war" directory (or symlink), the second
thing to check is whether your project is tagged as a Google Web Application
project.  This won't actually show up in the Eclipse UI, but if you look at
your project's .project file, you should see the following tag nested under


com.google.gdt.eclipse.core.webAppNature

If it's *not *there, go ahead and add it, and then restart Eclipse.  Then
try launching the project again, and see what happens.  Let me know if you
still run into problems.

Keith

On Wed, Oct 7, 2009 at 12:12 PM, mike_mac  wrote:

>
> Just to follow up on this ... this seems to be the eclipse plugin,
> I've managed to get host mode running from the command line and it
> works.
>
> The weird thing is, it DOES work with a small war project that I
> built, deployed on jboss and ran the hosted mode -noserver option from
> eclipse via the plugin. Our more complicated maven built war (part of
> a larger ear) doesn't and it seems to classpath issue but I don't know
> how to debug the eclipse plugin.
>
> I've added the command line startup command into my eclipse run so I
> can debug but it would be better if the plugin worked :(
>
> I did notice that the usage for plugin was different from commandline
> options so there could well be a bug here (i.e. theres a possiblity
> I'm not going mad). GWTShell vs HostedMode ??
>
> Unknown argument: -blah
> Google Web Toolkit 1.7.0
> GWTShell [-noserver] [-port port-number | "auto"] [-whitelist
> whitelist-string] [-blacklist blacklist-string] [-logLevel level] [-
> gen dir] [-style style] [-ea] [-out dir] [url]
>
> where
>  -noserver   Prevents the embedded web server from running
>  -port   Specifies the TCP port for the embedded web server
> (defaults to )
>  -whitelist  Allows the user to browse URLs that match the specified
> regexes (comma or space separated)
>  -blacklist  Prevents the user browsing URLs that match the specified
> regexes (comma or space separated)
>  -logLevel   The level of logging detail: ERROR, WARN, INFO, TRACE,
> DEBUG, SPAM, or ALL
>  -genThe directory into which generated files will be written
> for review
>  -style  Script output style: OBF[USCATED], PRETTY, or DETAILED
> (defaults to OBF)
>  -ea Debugging: causes the compiled output to check assert
> statements.
>  -outThe directory to write output files into (defaults to
> current)
> and
>  url Automatically launches the specified URL
>
> versus
>
> java -cp gwt-dev-.jar
> com.google.gwt.dev.HostedMode
> Missing required argument 'module[s]'
> Google Web Toolkit 1.7.0
> HostedMode [-noserver] [-port port-number | "auto"] [-whitelist
> whitelist-string
> ] [-blacklist blacklist-string] [-logLevel level] [-gen dir] [-style
> style] [-ea
> ] [-server servletContainerLauncher] [-startupUrl url] [-war dir] [-
> extra dir] [
> -workDir dir] [-localWorkers count] module[s]
>
> where
>  -noserver  Prevents the embedded web server from running
>  -port  Specifies the TCP port for the embedded web server
> (defaults to )
>  -whitelist Allows the user to browse URLs that match the
> specified regexes (comma or space separated)
>  -blacklist Prevents the user browsing URLs that match the
> specified regexes (comma or space separated)
>  -logLevel  The level of logging detail: ERROR, WARN, INFO,
> TRACE, DEBUG, SPAM, or ALL
>  -gen   The directory into which generated files will be
> written fo

Re: Google Eclipse Plugin - doubt about Web Application

[Keith Platfoot]

Yes, it just suppresses the warnings.
When you launch or deploy a web app project, any jars used at runtime (i.e.
anything your server-side code uses) need to be bundled within your servlet
in WEB-INF/lib.  The plugin will automatically warn if you have jars on your
build path which are *not* in this location.

However, occasionally, you will have one or more jars used only at
build-time.  An example would be a GWT add-on library.  Since the compiled
GWT output is just JavaScript, you wouldn't need to worry about deploying
that jar with your application.  The list of exclusions in Project
Properties -> Google -> Web Application is how you tell the plugin to stop
bothering you about it.

Keith

On Wed, Oct 14, 2009 at 9:28 AM, Ittai  wrote:

>
> +1
> I'd like to know what it does? It says "Suppress warnings about these
> build path entries outside of WEB-INF/lib" but what does it actually
> do? only suppress the warnings?
>
> On Oct 14, 3:12 pm, Diego Lovison  wrote:
> > click with the right button in the project will open one window click
> > in properties..
> >
> > go to Google -> Web Application
> >
> > what is the propose add the jar here?
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Google Eclipse Plugin issue w/ GWT 1.7.1 and hosted mode

[Keith Platfoot]

Hi Chad,

I tried to repro this with Eclipse 3.4.2 and GWT 1.7.1 using the latest
Eclipse plugin (1.1.2), but was not able to trigger a 404.  I tested on both
Windows and Ubuntu.

Just to verify that I followed the right sequence: I created two projects,
renamed the HTML page in each war directory to 'index.html' and then ran
each (one at a time, of course) by right-clicking each HTML file and
selecting Run As -> Web Application.  Each application started up in hosted
mode as expected.  If I then open the launch configurations dialog, I see 2
new launch configurations, each named after the HTML page I launched from:
'index.html' and 'index.html (1)'.

The first thing to check is your launch configurations dialog, to make sure
you also have 2 newly-generated configurations, each with the correct
project association and the right available modules (in the GWT tab).  If
not, try creating a second launch configuration by hand pointing to the
other project and retry your test by selecting the saved launch
configurations via the toolbar menu instead of using the Run As -> Web
Application menu item.

Let me know what you find,

Keith

On Wed, Oct 21, 2009 at 5:24 PM, cretz  wrote:

>
> I am posting here before I post an issue to the tracker to see if
> anyone has run across it. I am using Eclipse 3.4.2, but I doubt it's
> specific to an Eclipse version. Basically, if you have two unrelated
> Web Application projects in the same workspace that have the same HTML
> filename then running as a Web Application will use the previously run
> one instead of the project you right clicked on.
>
> To replicate:
>
> 1. Create a Web Application project named 'testapp1'
> 2. Create a Web Application project named 'testapp2'
> 3. Run each (one at a time of course) to make sure they run
> 4. Rename testapp1/war/testapp1.html to index.html, then run it as a
> Web Application
> 5. Rename testapp2/war/testapp2.html to index.html, then run it as a
> Web Application
>
> It will attempt to run w/ testapp1's classpath and server resources
> which cause a 404. Can anyone else replicate this issue before I open
> a bug? Has anyone seen or reported this issue before?
>
> Thanks
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Where can I find older Versions of the Eclipse Plugin?

[Keith Platfoot]

Hi Chris,

You're correct; the update site always points to only the latest version of
the plugin.  However, we do have zip distributions of some older versions
available as well, although I don't believe this is documented anywhere.
 Here are the URL's for plugin versions back to 1.1.0:

1.1.0 -
http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.1.0.v200907291526.zip
1.1.1 -
http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.1.1.v200909221731.zip
1.1.2 -
http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.1.2.v200910131704.zip

Note that these URL's are active right now, but we can't guarantee they
won't disappear at some point in the future.  Also, zip distributions come
with a few caveats, which you can learn about from this page in our help
docs:

http://code.google.com/eclipse/docs/install-from-zip.html

Finally, I want to point out that the latest version of the plugin (1.2.0)
should be backwards compatible with older versions of the GWT SDK, at least
back to 1.6.  Is there a particular reason you're looking for older versions
of the plugin itself?

Keith

On Thu, Dec 10, 2009 at 11:49 AM, Chris Moog  wrote:

> Does anybody know where to download older Versions of the Eclipse
> Plugin?
> http://dl.google.com/eclipse/plugin/3.5 always points to the current
> version. Is there an archive where I can find earlier versions?
>
> Cheers,
>
> Chris
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>

--

You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: My first deploy

[Keith Platfoot]

Hi Ista,

Could you provide a little more detail about your setup?  For example, are
you using the latest GWT version (2.0)?.  Also, how are you launching the
project?  It sounds like you are running a local web server, and placing the
compiled GWT application there, and then navigating to your index page with
a web browser.  If you can elaborate a little, that would be helpful in
troubleshooting the problem.  Thanks,

Keith

On Wed, Dec 16, 2009 at 4:52 AM, Ista Pouss  wrote:

> Hi,
>
> I have my little gwt application with eclipse, and I copy the
> directory app in place my little web site in local, I modify
> index.html with gwt things, i lauch it... and I see :
>
> GWT module 'diap' may need to be (re)compiled
>
>
> What is that ?
>
> I've seen
> http://groups.google.com/group/google-web-toolkit/browse_frm/thread/81b75d2c71bd4775?tvc=1&q=may+need+to+be+(re)compiled
> and I delete the directory and recompile, it's always the same.
>
> Thanks for your help.
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>

--

You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Migration Problem (From 1.5 to 2.0)

[Keith Platfoot]

Hi Haydar,

Since version 1.6, GWT projects have a new canonical structure that includes
a top-level directory named "war", where GWT expects to find your
publicly-served HTML/CSS, as well as various configuration files (including
the web.xml with your servlet declarations, inside a WEB-INF directory).
 See
http://code.google.com/webtoolkit/doc/1.6/ReleaseNotes_1_6.html#NewFeaturesfor
a good overview of the structural changes between 1.5 and 1.6.  This
doc
on GWT project organization may also be helpful:
http://code.google.com/webtoolkit/doc/latest/DevGuideOrganizingProjects.html#DevGuideDirectoriesPackageConventions
.

Hope this helps.

Keith

On Wed, Dec 16, 2009 at 9:19 AM, Haydar  wrote:

> Hi,
>
> I had a project in GWT 1.5 and I decided to migrate to GWT 2.0
>
> In my project I had my servlet declarations in gwt.xml file. But I
> think GWT 2.0
> looks for them in web.xml.
> I have done what is told on gwt site about migrating and then ran my
> project in devmode.
> But it gives me this warning:
>
> "00:00:03,032 [WARN] Module declares 1  declaration(s), but a
> valid 'web.xml' was not found at 'D:\projects\myworkspace\myproject\war
> \WEB-INF\web.xml' "
>
> When I look at that path I can't even find a WEB-INF folder. It
> doesn't create it, pretends as it is created and looks for an xml file
> which is not in a non-existing folder.
> I couldn't understand the problem.
>
> I can't even see my first page in the application. Should I create a
> web.xml which contains my servlet definitions? How can I do this? What
> must I have done wrong? Can anyone please help me?
>
> Thanks in advance...
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-tool...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
>

--

You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.