On Apr 2, 11:44 am, "Alex (Google)" wrote:
> To expand on Isaac's suggestion, everything that used to be in www is
> now in a directory called war. (I think the name is a bit misleading,
> too.) You should be able to copy everything from war to your web
> server. And since you aren't using a
To expand on Isaac's suggestion, everything that used to be in www is
now in a directory called war. (I think the name is a bit misleading,
too.) You should be able to copy everything from war to your web
server. And since you aren't using any Java servlets you can omit
copying the war/WEB-INF
I only use GWT for producing the client side javascript, which I copy
into a .Net web project that includes the server side code and a host
HTML file that integrates the GWT output with third party libraries.
It seems that a .war archive would make it more complicated to copy
the GWT output that I
What's stopping you from copying your compiler output to the Apache
document root?
On Thu, Apr 2, 2009 at 9:24 AM, Roberto -MadBob- Guido
wrote:
>
> I found in 1.6 is not managed a fallback mode to obtain a classic
> "www" folder to copy in the server's folder (such as in previous
> releases of
I found in 1.6 is not managed a fallback mode to obtain a classic
"www" folder to copy in the server's folder (such as in previous
releases of GWT), and I'm asking why...
I can understand for *many* people the .war archive is easier to
deploy, but it is not necessarly true for *everyone*! A .war r
