It seems to me that since GWT 2.0's development mode runs until your project is complete there is essentially no technical reason to run the actual Java->Javascript portion of the compiler when developing. Unfortunately in Idea 9 before your application server starts up the GWT compiler runs and the output is bundled into your .war. The server-side .java files are (somewhat) incrementally compiled when you do an Intellij "Make" but the GWT code always does a full compile.
Without resorting to writing my own build scripts is there a way to have Intellij not compile GWT code when I am developing and instead rely only on development mode?
You can use GWT Run configuration to start GWT in Dev Mode. In such case IDEA will not build war file so GWT compiler won't run.
Related
When I run my GWT 2.7.0 app in Eclipse, all is fine.
I compile the app Right click on project > Google > GWT Compile. I build my war. Copy the war in the webapps directory.
I get the first page ok (static HTML), then when I click on the app, after some time, I get a message box that says:
The page at xxx:8081 says:
Couldn't load app from Super Dev Mode
server at http://xxx:9876.
Please make sure this server is ready.
Do you want to try again?
Here is what happened:
In debug / deployment mode, as I was working within eclipse, a library which used to be 100% compatible with GWT Client Side has evolved and is not anymore. It seems that the library was not recompiled while I was testing it (no need for recompilation) but when I compiled for deployment it did want to recompile the library, failed, but build the war anyway (probably lack of testing on the result), deployed the war, and got this error...
I found the same problem. And this happends because I generated the war file after deploying the project in Super Dev mode. The solution for me was to compile the project and generate the war before deploying it in Super Dev mode (which it is supposed to use the 9876 port not used in tomcat)
I have install OpenEJB eclipse plugin, but it seems openEJB server does not recognize project's class path. It works fine only if i copy all dependencies(third party jars) into OpenEJB/lib directory. Is there any other way to work around, specially eclipse configuration?? Thanks
The plugin itself really isn't needed. Possibly check out http://vimeo.com/6149008 which details using OpenEJB as a plain library in Eclipse for developing and testing EJBs.
With a little more details on the ultimate goal (development vs test vs production) I can probably give a better recommendation.
I spent a couple of days trying to add internationalization (I18n) support to my gwt application project in IntelliJ IDEA 10. I was not successful. I tried to generate the necessary files with i18nCreator, but I don't how to hook the generated shell script to IntelliJ IDEA. I'm using maven2 in my project with a pom.xml file that was generated via GWT webAppCreator script.
When you debug or run a target IntelliJ allows you to run a maven goal. Same thing with artifacts.
So our new webapp project is based on maven. I'm really liking the dependency management and IDE agnostic approach but I'm having problems with compilation and debugging.
Here's how I would currently get a clean copy of the project working
Check out the main project from SVN
Open the project in IDE (I've tried in eclipse 3.4 and netbeans 6.7)
The IDE will automatically open two subprojects one being the webapp, the other being a supporting utils jar.
From the command line I run mvn war:inplace on the webapp module which builds a working copy of the webapp with all dependencies in WEB-INF/lib/
This then runs fine but whenever I change a java class I have to clean and build / reload the app context.
I've googled high and low but no one seems to be complaining about this so I guess there must be something really obvious I'm missing. How is everyone else handling incremental compilation and hot deploy with maven?
To clarify all I'm looking for is the replicate the behavior I used to have before maven where I could make simple changes to java classes and they would be instantaneously compiled and hot deployed to a running webapp. I don't need anything fancy like jRebel etc I just want the new tool to give me the same functionality I enjoyed with my old tools.
If you can use mvn jetty:run it will read the classes and resources directly from the project. Using Maven2 Eclipse plugin and running the server embedded in Eclipse has auto-publishing, which gets you there in the end, although it's slower. And JRebel starting with 2.0 (as you may know) can map the Maven module directly to the deployed application, so you get instant build and redeploy. Those are the only solutions I know of.
Netbeans should support it out of the box. Though, there remains a bug related to this: http://netbeans.org/bugzilla/show_bug.cgi?id=177230
In-place deployment works for me with Netbeans 7.0.1 and Tomcat 6.0.x if I use Tomcat 7.0.x in-place deployment doesn't work. Tomcat always copies application to $CATALINA_HOME/temp :(
I am new to GWT. I have developed a GWT application in version-1.6.4 and it is working fine. Now I want to integrate with that project in existing Java EE application. I don't know how to go ahead.
Where to copy the GWT source code in this existing Java EE application? I am also using RPC in GWT.
Can anyone provide help on this?
GWT is just a set of javascript and HTML files, so the most basic form of integration is just to put them in a folder in the same place your as your web pages go.
One step up from there would be to integrate the gwt Compiler in with your build process. If you use Netbeans there is a good plugin called GWT4NB that will handle all of this process for you, so that when you build the WAR of your project it will build the GWT portions of it as well. There would probably be something similar for Eclipse. You could also do all this by hand using maven or ant.
You would tell the compiler where you want it to put the generated files, which again, would be in the same location you put your web pages for your WAR project. The RPC side of it will still work just fine no matter where you put the files.