Hi Keith,
I played and played with Eclipse build path order etc. to see if I
could get the GWT plugin to use the JDK parser, not the one from the
J2EE app server OC4J. No Luck. Not sure what is driving this.
I looked at the source code In the dev subproject
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
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
Cris, your notes were really helpfully.
However I would like to know how you manage to debug your application
using your Glassfish (tomcat in my case) in order to use breakpoints
and those stuff.
Thanks you so much
--
You received this message because you are subscribed to the Google Groups
Hi David,
I haven't tried the same setup with Tomcat yet, but I expect it should
be the same procedure: In the Servers view in Eclipse, select the
server you deployed the EAR to. Right-click it and choose Debug.
This allows you to set breakpoints in your server side code.
To debug the client
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
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,
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
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
Additional steps to integrate with EJBs (3.1, probably similar for
3.0) This is more straightforward, but there are a few minor stumbling
blocks:
7. Enterprise Archive
--
Create a JavaEE/Enterprise Application project. Let's call it
myEar.
Add myProject to its module
Hi,
today I set up a GWT project that should use GlassFish v3 instead of
Jetty for GWT's development mode. It was important for me to make it
work seamlessly with the Eclipse JavaEE (WST/WTP) tools. Turns out,
it's not perfectly straightforward, at least not, if you want auto
rebuild/deploy. I've
11 matches
Mail list logo
