« »

New Tutorial – Deploying GWT Apps

Posted January 17th, 2008 by Nazmul

We believe in the power of ONE, at ScreamingToaster. We believe in innovation - ONE experience can change a person's life. We believe in partnerships - ONE endeavor can establish lasting trust & mutual success. We believe in education - ONE training course can empower a developer for life. We believe in giving back - ONE open-source project can inspire future entrepreneur. ONE person can become the leader that starts a revolution. ONE company can change the world and make it a better place - join us.

There are two aspects to deploying a GWT application: client side deployment, and server side packaging and deployment. In this tutorial, I will cover the different sets of issues that are tied to each aspect of deployment and packaging.

Here are things you have to keep in mind for client side deployment:

  1. are you going to embed the GWT app in an inframe?
  2. are you going to embed the GWT app in a div?
  3. are you going to use cross site scripting?
  4. are you going to use services on a different host/port than the one you are deploying your app into?
  5. are you going to embed the GWT app into an existing web app or webpage?
  6. are you going to create a new app from scratch, without having to deal with legacy integration and deployment issues?

Here are things that you have to keep in mind for server side packaging and deployment:

  1. are you going to host the WAR file in an HTTP or HTTPS server?
  2. are you going to serve up the client app on a different host than the service host?

Go directly to the tutorial – GWT Tutorial – Deploying GWT Apps

 

We believe in the power of ONE, at ScreamingToaster. We believe in innovation - ONE experience can change a person's life. We believe in partnerships - ONE endeavor can establish lasting trust & mutual success. We believe in education - ONE training course can empower a developer for life. We believe in giving back - ONE open-source project can inspire future entrepreneur. ONE person can become the leader that starts a revolution. ONE company can change the world and make it a better place - join us.

7 Responses to “New Tutorial – Deploying GWT Apps”

  1. Prasan Says:

    Thanks for the great tutorial.

    I am running into a problem while deploying Two different gwt apps in a single page at two different .

    first I include the nocache.js files in BODY as

    JS1.nocache.js hooks into ( RootPanel.get(“firstDiv”).add(…) )
    JS2.nocache.js hooks into ( RootPanel.get(“secondDiv”).add(…))

    and then I do have both Div in my html.

    It so happens that only the first module is shown. In above case JS1 is only shown. Now if I change the order of tag for JS1 and JS2 keeping JS2 to appear first, then only module JS2 is shown.

    Any idea why this should be happening?

  2. Nazmul Says:

    Hi Prasan

    You’re most welcome for the tutorial; I’m glad you liked it.

    I’m not sure why it’s not working… Maybe try using iframes in the firstDiv and secondDiv areas?

    Nazmul.

  3. mariqn Says:

    Great tutorial, that solves many not trivial cases. Very very good tutorial.

  4. Nazmul Says:

    Thanks Mariqn. I appreciate it.

  5. komal Says:

    Hi,
    I need the single sign on feature for the multiple applications created using Gwt but I am confused for what approach should be taken .
    I need the user to be logged in once and if he tries to access another application he should be logged in directly .
    Should be done using servlets or what I need some guidance .
    I am using tomcat 6.018
    Thanks in advance..

  6. Conny Says:

    Hi,

    first thanks for this great tutorial.

    I want to integrate my gwt application in an external webpage. But I don’t want to use an iframe. Therefore I run in the same origin policy problem. I’m using a JBoss which runs my application. Can someone give me a hint or post some links where I can find some documentation/solutions about this problem?

    Thanks in advance!

  7. John V Denley Says:

    You said: “If you need access to the iframe’s parent DOM element, and you need to make RPC calls on an originating host that’s different from the enclosing page, then you are in in trouble :(

    Can you tell me how I CAN set/reset/refresh the parents URL from within an iframe. When I am in my iframe and I press F5 (refresh), I get the result I need (refreshes the parent page), but when I try to do this programatically it doesn’t seem to do what I want it to!

    Ive tried:

    Window.Location.reload();

    Window.open(“http://www.myurl.com”, “_top”,”");

    SetParentURL();

    where SetParentURL() is:
    private native void SetParentURL() /*- { parent.location = “http://www.myurl.com”; } -*/;

Leave a Reply