Re: The import cannot be resolved

Eclipse has 2 notions of classpath. 1. Classpath: Modify this in the Project > properties > BuildPath settings 2. Runtime classpath: Modify this in Project > properties > run/debug configuration settings Almost every Eclipse classpath (ClassNotFoundException could be solved this

Re: The import cannot be resolved

GPE development mode removes some jar from the classpath of Jetty based on the code actually used. Check your code refers to at least one class of the jar sqljdbc4.jar. If not, try to reference (e.g. instantiate) whathever class from this jar inside your GWT application (either on client or server

Re: The import cannot be resolved

Hi, Do you use those classes on the client side ? If it the case, it cannot work since you probably don't have any *.gwt.xml in your jar since this code cannot be translated to javascript. Else it is a classpath problem of your running application. Can you describe please how you launch the appli

The import cannot be resolved

I have gone thru some of the other threads but still cannot resolve this issue. I am using indigo eclipse. I have added the jar sqljdbc4.jar file to the java build path. When I hit the debug as 'web application' the page loads but the following errors appear in the "Development Mode' tab. Line

import cannot be resolved

HI Every one can anybody tell me in detail how to fix this issue "import com.google cannot be resolved". working in Eclipse SDK Version: 3.6.1. Saw in trouble shooting column of GWT Documentation, in that they told add a tag in .gwt.xml file, depending on that in my project package in .gwt.xml f

Re: Problems creating my first reusable module: import cannot be resolved

Thanks for the responses - much appreciated. The root cause turned out to be a few things. 1. My Eclipse environment was in some weird state. After restarting Eclipse, things became much more obvious. 2. Hyphens in the .gwt.xml name were a no-no 3. Class.newInstance() isn't supported in the

Re: Problems creating my first reusable module: import cannot be resolved

feel free to shoot me a zip of the project and I will tell you whats wrong. On Aug 18, 11:44 am, Sleeveen wrote: > I've dropped the JAR in war/WEB-INF/lib since it will (eventually) be > used on the server side of things. > > I've removed the hyphens from the name of the module (everywhere): > st

Re: Problems creating my first reusable module: import cannot be resolved

For me... package: src `-my.site.tools.layout `-Layout.gwt.xml progect.gwt.xml: ...works perfectly. Test your project before you pack them in jar. debug->junit->compile- >jar The very first thing that comes to mind: Jar not empty? On Aug 18, 11:44 pm, Sleeveen wrote: > I've dropped the JAR

Re: Problems creating my first reusable module: import cannot be resolved

I've dropped the JAR in war/WEB-INF/lib since it will (eventually) be used on the server side of things. I've removed the hyphens from the name of the module (everywhere): still no luck. I've removed the rename-to attribute: still no luck. I am indeed using Eclipse. The JAR is configured as a li

Re: Problems creating my first reusable module: import cannot be resolved

Fernando, Could you elaborate on this comment? Do you mean the my-module.gwt.xml? And where do you think it should be placed? Thanks! On Aug 18, 9:42 am, Fernando wrote: > Your .xml seems out of place > -- You received this message because you are subscribed to the Google Groups "Google We

Re: Problems creating my first reusable module: import cannot be resolved

>From what I can tell there is nothing wrong with the structure of your project or the packaging. Generics have been supported since GWT 1.5. First of all, you dont want it to be in war/WEB-INF/lib. This is for server-side Java libraries, but this won't hurt anything. Second, I would try taking

Re: Problems creating my first reusable module: import cannot be resolved

Your .xml seems out of place On 17 ago, 18:12, Sleeveen wrote: > I'm in the process of trying to create my first reusable module in > GWT. For > now, this module contains only some simple classes to be used as part > of a > GWT RPC implementation. The module DOES NOT have an entry-point, just > s

Problems creating my first reusable module: import cannot be resolved

I'm in the process of trying to create my first reusable module in GWT. For now, this module contains only some simple classes to be used as part of a GWT RPC implementation. The module DOES NOT have an entry-point, just source path specifications. This code would normally go into the "shared" su

import cannot be resolved...NOT

We use Ant to build GWT project. Occasionally our developers write code comments using {...@link ...} syntax to link to a class outside of the designated client package, thus insert a "import" statement that causes the notorious "The import ... cannot be resolved" ERROR. That