What version of GWT is Vaadin 7.4/7.5 based on?
I know vaadin includes their own version of GWT with some addons and possible additional bug fixes but what version is vaadin 7.4/7.5 based on?
Surely you need to know this if you intend to switch from GWT jars to vaadin provided jars. For example GWT RPC does not work in development mode when you use GWT jars on the client and vaadin jars on the server even when vaadin is based on the same version of GWT. e.g Vaadin 7.1 which I believe is based on GWT 2.5.1
We have a GWT application that uses RPC and also a Vaadin application. We've had to make sure the vaadin gwt version and the gwt application use the same version of GWT (if you know what I mean).
We want to move to vaadin 7.4/7.5 so I am assuming we will need to migrate our GWT application to the same version vaadin 7.4/7.5 is based on?
I'd say 2.7 with some changes for vaadin.
I can't say for sure, but my assumptions are based on the property
gwt.version=2.7.0.vaadin3
in this file: https://github.com/vaadin/vaadin/blob/7.5/build.properties
Here the same file fore vaadin 7.4: https://github.com/vaadin/vaadin/blob/7.4/build.properties
Related
I need to develop a presentation layer for an existing Java EE application running on JBoss AS 4.2.1.GA. I have been reading on JSF, Facelets and RichFaces and tried a few examples - some things worked but others didn't because of the limitations of library versions I used, considering the outdated JBoss.
Can someone recommend the direction I need to be heading to get this done as quickly as possible by using the mentioned server? By this I mean the Eclipse tool (WTP, JBoss Tools, ...), type of project, dependencies, ... Also, to shorten development time, maybe also use JRebel?
I know I would be better off using the latest server, but unfortunately it is not an option.
Also, I have installed JBoss Tools for Eclipse Indigo, but for creating RichFaces Project, it requires JBoss EAP 6 or AS 7.1.
I had created applications using JSF 1.2, RichFaces 3.3.3, JBoss Seam 2.0.2 (not required) for JBoss AS 4.2.2.GA. For development was used Eclipse (3.4/3.5) IDE for Java EE Developers. Version of Eclipse is not important. Yes, you need WTP. In my projects seam-gen was used for generating project skeleton. If you don't use Seam you can create Web project.
I have a GWT project(GWT version 2.4). I want to start up Spray-servlet in server side GWT, but GWT does not support servlet-3.0, therefore I wanted to use org.apache.sling.extensions.gwt.servlet-3.0.0.jar for using servlet-3.0.0.
How I can use org.apache.sling.extensions.gwt.servlet-3.0.0.jar in GWT?
EDIT
If sling does not help me, then how can I run spray-servlet-1.2-RC1 in server side GWT?
org.apache.sling.extensions.gwt.servlet-3.0.0.jar is not a Servlet 3.0 package for GWT, but an extension to Apache Sling meant to allow server-side GWT code to run.
It's not what you're looking for.
Is is possible to implement the client side of a Play Framework 2.x web application using GWT or Vaadin?
Play 1.x has a special module that provides GWT integration, but I can not find examples of the use of these technologies together in Play 2.x version. Can these technologies be integrated? Is there a module, or must some other approach be used?
GWT and Play2 can work together seamlessly, just as GWT can be used with python and go backends.
Using GWT with Play2 has two parts, serving static files and client-server communication.
For the GWT produced static files (js, css, img..) you can just add them to the Play2 public directory, and they will be accessible based on the routes configuration.
For client-server communication your best bet is using a pure json-rest approach, as request-factory, gwt-rpc have some dependency on J2EE servlets.
There are plenty examples of providing a json/REST api with Play2, and plenty examples of interacting with json/REST APIs with GWT.
Henri Kerola demoed this recently for play 2.x and will give a talk at javaone this year:
http://www.youtube.com/watch?v=IwuqAh0VSek
I found a project on github which integrates Vaadin with Play 2.2:
https://github.com/henrikerola/play-vaadin-integration
You can't use Vaadin with play2. Vaadin is basically a Java EE servlet that must live in a Java EE container such as Tomcat.
Play is not based on Java EE, it uses its own server.
As for GWT all server side code needs a Java EE container. But if you just want the client side then it's totally possible as it is with any web framework.
Just create json web services and remove server dependancies.
For an example in php : http://gwtquickstart.blogspot.fr/2009/11/call-php-script-from-gwt.html
I am using GWT 2.4 with Hibernate 3.0. I wanted to know what changes I need to make in my application for integrating GWT 2.5 in my application ?
Nothing special.
Replace 2.4.0 dependencies with 2.5.0-rc1 ones (depending on how you manage dependencies, either download the SDK and drop the new JARs to replace the previous ones, or bump the version number in your POM –if using Maven– or similar build file).
If you're using Maven and the gwt-maven-plugin, make sure you re-define the plugin dependencies too (note gwt-maven-plugin 2.4.0 also needs gwt-servlet to be overridden); or you can test the gwt-maven-plugin 2.5.0-rc1.
Check the list of breaking changes though; chances are small that they affect you, but there's still a risk.
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.