fixed
It's now just the old servlet thing of needing servlet jar to compile (but
not run) the code. In the ant build file I just added a
* hi Colin
>
> import com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet;
> //import com.google.gwt.user.server.rpc.RemoteServiceServlet;
>
> As above
hi Colin
import com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet;
//import com.google.gwt.user.server.rpc.RemoteServiceServlet;
As above, I replaced the import statement as you suggest. Also I
referenced gwt-servlet-jakarta.jar instead of gwt-servlet.jar in my ant
build file; gwt-se
Thanks Shaik & Jens for your replies, but I've still got the same problem.
To recap the project includes a servlet (yes it is gwt-rpc) that simply
grabs the remote IP and makes it available to client code. If I browse to
the servlet, I should get a 405 signifying that the servlet is running but
hi
I'm trying to upgrade from 2.10.0 to 2.12.1.
My app runs in tomcat / java 21 with apache using it as a proxy. It's
mostly client code except for a servlet whose sole function is to grab the
remote ip and make it available to client code. With the 2.10.0 setup I had
to run the server class th
).getHeader("X-Forwarded-For");
>
>
> On Fri, Nov 10, 2023 at 7:22 PM 'dav...@googlemail.com' via GWT Users <
> google-we...@googlegroups.com> wrote:
>
>> Leon
>>
>> The servelet runs at *subdomain.mydomain.com/foo/bah
>> <http://subdomai
y times with gwt applications. Works like charm.
>
> On Fri, Nov 10, 2023 at 6:34 PM 'dav...@googlemail.com' via GWT Users <
> google-we...@googlegroups.com> wrote:
>
>> Spot why this can never work ie running a site on apache2 that proxies to
>> a webapp running o
.
>>> If you setup apache2 to forward virtual name based hosts to tomcat,
>>> apache2 is nothing more than a proxy server to 127.0.0.1:8080. Then you
>>> can keep the tomcat fairly simple and straightforward.
>>> There are multiple examples online of how to
the tomcat fairly simple and straightforward.
>> There are multiple examples online of how to deploy a .war file to tomcat
>> on the internet. It's nothing more than that.
>>
>>
>> On Thu, Nov 9, 2023 at 6:34 PM 'dav...@googlemail.com' via GWT Users <
dnesday, 8 November 2023 at 12:31:36 UTC Ed wrote:
>>
>>> jetty is application server while apache2 is a web server. tomcat is
>>> the apache app server.
>>>
>>> On Wed, Nov 8, 2023 at 4:48 AM 'dav...@googlemail.com' via GWT Users <
>>
ve, rather just the javascript, directory. so that does
appear to be a reasonable way to go?
David
On Wednesday, 8 November 2023 at 12:31:36 UTC Ed wrote:
> jetty is application server while apache2 is a web server. tomcat is the
> apache app server.
>
> On Wed, Nov 8, 2023 at 4:4
On my development machine I test my code in jetty. The client code calls a
server to get the client ip address. This works fine and I see a server at
localhost:8080/foo/bar as I expect. If I browse to it I get a 405 as GET
request are not allowed, but that's not a problem as it does the job it's
This is my bad :-)
The problem is me losing track of threading issues, which I've solved
It's *not* a GWT problem
On Tuesday, 7 November 2023 at 04:08:06 UTC dav...@googlemail.com wrote:
> I'm using GWT 2.10
> My app client code calls the server to get the ip address of the client.
>
> Testing
I'm using GWT 2.10
My app client code calls the server to get the ip address of the client.
Testing locally, I have this snippet
String lp = remoteIP.getIP();
Window.alert(ip);
the pop up says 127.0.0.1 as expected, but trying to include the ip
string in some HTML output gives "undefined" as
13 matches
Mail list logo
