Re: running gwt server code on apache

Leon, Ed

Thanks for looking at this. I realized I have an apache2 problem at this stage more than a GWT one.

A bit of proxy code in tomcat and apache2 + enabling  proxy_http has fixed the problem. Most of my  enlightenment came from

https://tomcat.apache.org/tomcat-8.5-doc/proxy-howto.html#Apache_httpd_Proxy_Support

and also seeing that an apache module was needed from the logs. Production machine is debian and proxy_http does not seem to be enabled by default.

I expect there are other ways to skin this cat, especially since I'm using AJP anyway, but I think I'll leave it here :-)

David

On Thursday, 9 November 2023 at 19:33:37 UTC Ed wrote:

i think gwt has a same source domain filter

On Thu, Nov 9, 2023 at 11:47 AM Leon <leon.p...@gmail.com> wrote:

As far as I know, gwt uses relative paths wrt it's own context root. So the client calls should always be able to reach the gwt servlets. I've never had to configure anything to make that happen.

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 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 <google-we...@googlegroups.com> wrote:

yeah that sounds doable, I think it's along the lines I was already thinking

So mydomain..com is served by apache2 and includes the GWT javascript

Apache2 also has a conf for subdomain.mydomain.com that creates a backend  AJP to tomcat where I serve subdomain.mydomain.com/appA and subdomain.mydomain.com/appB

So I just create a ROOT folder in webapps, pop a copy of my GWT code's WEB-INF there and that does a job.

But not the job! The servelet that GWT server code creates to pass the remote ip to the client code is now running at subdomain.mydomain.com/foo/bar instead of mydomain.com/foo/bar, so the GWT produced client javascript served at mydomain.com and the servelet can't talk.

I feel there must be a solution, but just now I don't see it and even thus far, I feel I'm jumping through hoops. Am I missing a recommended way to do this?

On Thursday, 9 November 2023 at 13:40:02 UTC Leon Pennings wrote:

You can deploy the web application on tomcat and use mod_proxy on apache2 to forward https (or http if required) to tomcat on 8080 (or another port if required)

Op woensdag 8 november 2023 om 18:31:19 UTC+1 schreef dav...@googlemail.com:

hi Ed

Yes understood and most of  the "app" is GWT produced javascript, part of a web page, which I've always run on apache2 and don't really want to change that for the ip address supplying servelet which is a recent addition. I already also run  a backend tomcat with an AJP connection to apache2 for a couple of  java coded apps. So is setting up the WEB-INF directory of my GWT "app" separately in tomcat the preferred way to do this or at least a possibility?

Prior to adding  the server code the WEB_INF directory was not needed by apache2 I believe, 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:48 AM 'dav...@googlemail.com' via GWT Users <google-we...@googlegroups.com> wrote:

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 supposed to do ie pass request address back to client code.

It does not work in production were the code is run on apache; the server is not created as on jetty, so that's not unexpected. I first suspicion was that modsecurity is preventing the creation of the server, but that proves to be not so. I also see the same failure over http as over https.

I have a pretty basic apache2 setup on debian (apart from adding modsecurity) and the site config is pretty bog standard for both http and https. I'm guessing I need to tweak something somewhere to allow the server to be created?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6aafe876-bff0-4b02-86f2-239e94201324n%40googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/z7HMUEfBOZk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/63dd206e-2a3c-4d5f-8fba-fbd036aa2d2an%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CABjQu7T8K0yiM0zg-AiUt3vqmsT%2B6nOPz4q54k3WUbRSX8_dcg%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/c3366dfd-e570-4837-a2f2-b3d3beb13404n%40googlegroups.com.

Re: running gwt server code on apache

i think gwt has a same source domain filter

On Thu, Nov 9, 2023 at 11:47 AM Leon <leon.pennings@gmail.com> wrote:

As far as I know, gwt uses relative paths wrt it's own context root. So the client calls should always be able to reach the gwt servlets. I've never had to configure anything to make that happen.

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 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 <google-web-toolkit@googlegroups.com> wrote:

yeah that sounds doable, I think it's along the lines I was already thinking

So mydomain..com is served by apache2 and includes the GWT javascript

Apache2 also has a conf for subdomain.mydomain.com that creates a backend  AJP to tomcat where I serve subdomain.mydomain.com/appA and subdomain.mydomain.com/appB

So I just create a ROOT folder in webapps, pop a copy of my GWT code's WEB-INF there and that does a job.

But not the job! The servelet that GWT server code creates to pass the remote ip to the client code is now running at subdomain.mydomain.com/foo/bar instead of mydomain.com/foo/bar, so the GWT produced client javascript served at mydomain.com and the servelet can't talk.

I feel there must be a solution, but just now I don't see it and even thus far, I feel I'm jumping through hoops. Am I missing a recommended way to do this?

On Thursday, 9 November 2023 at 13:40:02 UTC Leon Pennings wrote:

You can deploy the web application on tomcat and use mod_proxy on apache2 to forward https (or http if required) to tomcat on 8080 (or another port if required)

Op woensdag 8 november 2023 om 18:31:19 UTC+1 schreef dav...@googlemail.com:

hi Ed

Yes understood and most of  the "app" is GWT produced javascript, part of a web page, which I've always run on apache2 and don't really want to change that for the ip address supplying servelet which is a recent addition. I already also run  a backend tomcat with an AJP connection to apache2 for a couple of  java coded apps. So is setting up the WEB-INF directory of my GWT "app" separately in tomcat the preferred way to do this or at least a possibility?

Prior to adding  the server code the WEB_INF directory was not needed by apache2 I believe, 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:48 AM 'dav...@googlemail.com' via GWT Users <google-we...@googlegroups.com> wrote:

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 supposed to do ie pass request address back to client code.

It does not work in production were the code is run on apache; the server is not created as on jetty, so that's not unexpected. I first suspicion was that modsecurity is preventing the creation of the server, but that proves to be not so. I also see the same failure over http as over https.

I have a pretty basic apache2 setup on debian (apart from adding modsecurity) and the site config is pretty bog standard for both http and https. I'm guessing I need to tweak something somewhere to allow the server to be created?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6aafe876-bff0-4b02-86f2-239e94201324n%40googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/z7HMUEfBOZk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/63dd206e-2a3c-4d5f-8fba-fbd036aa2d2an%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CABjQu7T8K0yiM0zg-AiUt3vqmsT%2B6nOPz4q54k3WUbRSX8_dcg%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CAMgbRPvn-OB80tmJyao5EbZ0oY9yXbdgNwNHSM%2B0ZaESNisBZQ%40mail.gmail.com.

Re: running gwt server code on apache

As far as I know, gwt uses relative paths wrt it's own context root. So the client calls should always be able to reach the gwt servlets. I've never had to configure anything to make that happen.

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 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 <google-web-toolkit@googlegroups.com> wrote:

yeah that sounds doable, I think it's along the lines I was already thinking

So mydomain..com is served by apache2 and includes the GWT javascript

Apache2 also has a conf for subdomain.mydomain.com that creates a backend  AJP to tomcat where I serve subdomain.mydomain.com/appA and subdomain.mydomain.com/appB

So I just create a ROOT folder in webapps, pop a copy of my GWT code's WEB-INF there and that does a job.

But not the job! The servelet that GWT server code creates to pass the remote ip to the client code is now running at subdomain.mydomain.com/foo/bar instead of mydomain.com/foo/bar, so the GWT produced client javascript served at mydomain.com and the servelet can't talk.

I feel there must be a solution, but just now I don't see it and even thus far, I feel I'm jumping through hoops. Am I missing a recommended way to do this?

On Thursday, 9 November 2023 at 13:40:02 UTC Leon Pennings wrote:

You can deploy the web application on tomcat and use mod_proxy on apache2 to forward https (or http if required) to tomcat on 8080 (or another port if required)

Op woensdag 8 november 2023 om 18:31:19 UTC+1 schreef dav...@googlemail.com:

hi Ed

Yes understood and most of  the "app" is GWT produced javascript, part of a web page, which I've always run on apache2 and don't really want to change that for the ip address supplying servelet which is a recent addition. I already also run  a backend tomcat with an AJP connection to apache2 for a couple of  java coded apps. So is setting up the WEB-INF directory of my GWT "app" separately in tomcat the preferred way to do this or at least a possibility?

Prior to adding  the server code the WEB_INF directory was not needed by apache2 I believe, 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:48 AM 'dav...@googlemail.com' via GWT Users <google-we...@googlegroups.com> wrote:

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 supposed to do ie pass request address back to client code.

It does not work in production were the code is run on apache; the server is not created as on jetty, so that's not unexpected. I first suspicion was that modsecurity is preventing the creation of the server, but that proves to be not so. I also see the same failure over http as over https.

I have a pretty basic apache2 setup on debian (apart from adding modsecurity) and the site config is pretty bog standard for both http and https. I'm guessing I need to tweak something somewhere to allow the server to be created?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6aafe876-bff0-4b02-86f2-239e94201324n%40googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/z7HMUEfBOZk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/63dd206e-2a3c-4d5f-8fba-fbd036aa2d2an%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CABjQu7T8K0yiM0zg-AiUt3vqmsT%2B6nOPz4q54k3WUbRSX8_dcg%40mail.gmail.com.

Re: running gwt server code on apache

yeah that sounds doable, I think it's along the lines I was already thinking

So mydomain..com is served by apache2 and includes the GWT javascript

Apache2 also has a conf for subdomain.mydomain.com that creates a backend  AJP to tomcat where I serve subdomain.mydomain.com/appA and subdomain.mydomain.com/appB

So I just create a ROOT folder in webapps, pop a copy of my GWT code's WEB-INF there and that does a job.

But not the job! The servelet that GWT server code creates to pass the remote ip to the client code is now running at subdomain.mydomain.com/foo/bar instead of mydomain.com/foo/bar, so the GWT produced client javascript served at mydomain.com and the servelet can't talk.

I feel there must be a solution, but just now I don't see it and even thus far, I feel I'm jumping through hoops. Am I missing a recommended way to do this?

On Thursday, 9 November 2023 at 13:40:02 UTC Leon Pennings wrote:

You can deploy the web application on tomcat and use mod_proxy on apache2 to forward https (or http if required) to tomcat on 8080 (or another port if required)

Op woensdag 8 november 2023 om 18:31:19 UTC+1 schreef dav...@googlemail.com:

hi Ed

Yes understood and most of  the "app" is GWT produced javascript, part of a web page, which I've always run on apache2 and don't really want to change that for the ip address supplying servelet which is a recent addition. I already also run  a backend tomcat with an AJP connection to apache2 for a couple of  java coded apps. So is setting up the WEB-INF directory of my GWT "app" separately in tomcat the preferred way to do this or at least a possibility?

Prior to adding  the server code the WEB_INF directory was not needed by apache2 I believe, 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:48 AM 'dav...@googlemail.com' via GWT Users <google-we...@googlegroups.com> wrote:

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 supposed to do ie pass request address back to client code.

It does not work in production were the code is run on apache; the server is not created as on jetty, so that's not unexpected. I first suspicion was that modsecurity is preventing the creation of the server, but that proves to be not so. I also see the same failure over http as over https.

I have a pretty basic apache2 setup on debian (apart from adding modsecurity) and the site config is pretty bog standard for both http and https. I'm guessing I need to tweak something somewhere to allow the server to be created?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6aafe876-bff0-4b02-86f2-239e94201324n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/63dd206e-2a3c-4d5f-8fba-fbd036aa2d2an%40googlegroups.com.

Re: running gwt server code on apache

You can deploy the web application on tomcat and use mod_proxy on apache2 to forward https (or http if required) to tomcat on 8080 (or another port if required)

Op woensdag 8 november 2023 om 18:31:19 UTC+1 schreef dav...@googlemail.com:

hi Ed

Yes understood and most of  the "app" is GWT produced javascript, part of a web page, which I've always run on apache2 and don't really want to change that for the ip address supplying servelet which is a recent addition. I already also run  a backend tomcat with an AJP connection to apache2 for a couple of  java coded apps. So is setting up the WEB-INF directory of my GWT "app" separately in tomcat the preferred way to do this or at least a possibility?

Prior to adding  the server code the WEB_INF directory was not needed by apache2 I believe, 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:48 AM 'dav...@googlemail.com' via GWT Users <google-we...@googlegroups.com> wrote:

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 supposed to do ie pass request address back to client code.

It does not work in production were the code is run on apache; the server is not created as on jetty, so that's not unexpected. I first suspicion was that modsecurity is preventing the creation of the server, but that proves to be not so. I also see the same failure over http as over https.

I have a pretty basic apache2 setup on debian (apart from adding modsecurity) and the site config is pretty bog standard for both http and https. I'm guessing I need to tweak something somewhere to allow the server to be created?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6aafe876-bff0-4b02-86f2-239e94201324n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/685dc5d5-db0c-4423-b667-598a44bcd10an%40googlegroups.com.

Re: running gwt server code on apache

hi Ed

Yes understood and most of  the "app" is GWT produced javascript, part of a web page, which I've always run on apache2 and don't really want to change that for the ip address supplying servelet which is a recent addition. I already also run  a backend tomcat with an AJP connection to apache2 for a couple of  java coded apps. So is setting up the WEB-INF directory of my GWT "app" separately in tomcat the preferred way to do this or at least a possibility?

Prior to adding  the server code the WEB_INF directory was not needed by apache2 I believe, 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:48 AM 'dav...@googlemail.com' via GWT Users <google-we...@googlegroups.com> wrote:

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 supposed to do ie pass request address back to client code.

It does not work in production were the code is run on apache; the server is not created as on jetty, so that's not unexpected. I first suspicion was that modsecurity is preventing the creation of the server, but that proves to be not so. I also see the same failure over http as over https.

I have a pretty basic apache2 setup on debian (apart from adding modsecurity) and the site config is pretty bog standard for both http and https. I'm guessing I need to tweak something somewhere to allow the server to be created?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6aafe876-bff0-4b02-86f2-239e94201324n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/b6acf504-b260-46d3-bd8e-6bc3aff3c357n%40googlegroups.com.

Re: running gwt server code on apache

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 <google-web-toolkit@googlegroups.com> wrote:

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 supposed to do ie pass request address back to client code.

It does not work in production were the code is run on apache; the server is not created as on jetty, so that's not unexpected. I first suspicion was that modsecurity is preventing the creation of the server, but that proves to be not so. I also see the same failure over http as over https.

I have a pretty basic apache2 setup on debian (apart from adding modsecurity) and the site config is pretty bog standard for both http and https. I'm guessing I need to tweak something somewhere to allow the server to be created?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6aafe876-bff0-4b02-86f2-239e94201324n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CAMgbRPtUWTq_MVYo1_8X8vZ4dGS70jfU730yjB-hpeb4Qh4XCQ%40mail.gmail.com.

running gwt server code on apache

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 supposed to do ie pass request address back to client code.

It does not work in production were the code is run on apache; the server is not created as on jetty, so that's not unexpected. I first suspicion was that modsecurity is preventing the creation of the server, but that proves to be not so. I also see the same failure over http as over https.

I have a pretty basic apache2 setup on debian (apart from adding modsecurity) and the site config is pretty bog standard for both http and https. I'm guessing I need to tweak something somewhere to allow the server to be created?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6aafe876-bff0-4b02-86f2-239e94201324n%40googlegroups.com.

Re: undefined String problem

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 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 output.

So how to get the same value in some HTML to be displayed in a FlowPanel as in the alert popup? I tried to use the StringUtils.javaScriptString() method, but that does not effect the situation.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/199e7769-dac3-43a6-b39c-4ea489169e86n%40googlegroups.com.

undefined String problem

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 output.

So how to get the same value in some HTML to be displayed in a FlowPanel as in the alert popup? I tried to use the StringUtils.javaScriptString() method, but that does not effect the situation.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/1c533314-10bf-446f-ae28-694c6770fb07n%40googlegroups.com.

Re: GWT Designer

Cool Sachin!

El dom, 5 nov 2023 a las 17:10, Sachin Bal (<sachinbal@gmail.com>) escribió:

Wanted to inform that I could deploy the war file and I can now access the application on localhost and could get all the screens required. Thanks for all the help.

Regards

Sachin

On Monday, October 30, 2023 at 9:22:41 PM UTC+5:30 Sachin Bal wrote:

Earlier, I remember when I clicked the source tab, it showed the source code which it is showing. And when I used to click the design tab, I could see a screen which I could modify. This is explained on (https://www.youtube.com/watch?v=kV5H3rGfqOE) at 3:00 min on the video.

I feel that I am missing something and it has been many years since I have used GWT Designer, and therefore cannot remember

Do you remember anything which could help me? Thanks

On Monday, October 30, 2023 at 7:10:14 PM UTC+5:30 Edu wrote:

Hi,

If i remember correctly if you already installed the Designer plugin you need to open the java file that is linked with that xml file using the Designer editor not the default one.

El lun, 30 oct 2023 a las 10:20, Sachin Bal (<sach...@gmail.com>) escribió:

Hi,

I installed Eclipse Kepler and when I open any ui.xml file, I can see two tabs, source and design. In the source, I can see the code but in the design I am not able to see the generated screen. I have a feeling that I have missed something but I cannot remember exactly. Can you please advise? Attached below is the source and design screens. It would be great, if you could guide me. Thanks

On Sunday, October 29, 2023 at 7:00:22 PM UTC+5:30 Sachin Bal wrote:

Thanks. I will check the old version of eclipse. I believe it was Eclipse Kepler which we had used earlier. 

Regards

Sachin

On Saturday, October 28, 2023 at 3:13:56 AM UTC+5:30 Colin Alworth wrote:

If memory serves, the GWT Designer tool was never part of GWT itself, but was a component that could be installed in Eclipse, allowing for WYSIWYG UI design (in part by running something like dev mode while you were editing?). Changes that the author of the project made were reflected in standard source files (.java and .ui.xml) that GWT itself was able to compile - as such, a newer compiler version can likely still compile (with small or minimal changes to source) such an old project. I would suggest small steps in upgrading, to keep such changes (if any) manageable.

If you're hoping to run GWT Designer itself, you probably need a very old version of eclipse - my memory here is that it wasn't used enough to be worth maintaining. The code still lives at https://github.com/gwt-plugins/gwt-designer, but I can't guess what it would take to bring it back to life. I have a memory of this being based on WindowBuilder, and some internal changes in WindowBuilder requiring substantial changes to the gwt-designer project, which never was done.

On Friday, October 27, 2023 at 3:19:36 PM UTC-5 sach...@gmail.com wrote:

Hi All,

We had created an application in 2014-2015. We had used GWT to design the UI of our application.  Unfortunately, we have folded that project in 2017 . I wanted to showcase our project to a prospective customer and was keen to know whether there is some way to migrate the project to the latest version of GWT? 

If that is not possible, I would like to display the screens which we had designed using GWT Designer so that I can at the least create a story around it.

Looking forward to some positive response

Please advise. 

Thanks

Sachin

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/1f61346d-1507-4f79-a26c-91e40655f2c7n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f23e250f-0633-4638-bc36-637d6b8ebf4fn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CAM5HcKp0avDdRhcyscObgWgeL_nWT-u6AKb%2BGiL2UwB6iN330w%40mail.gmail.com.

Re: GWT Designer

Wanted to inform that I could deploy the war file and I can now access the application on localhost and could get all the screens required. Thanks for all the help.

Regards

Sachin

On Monday, October 30, 2023 at 9:22:41 PM UTC+5:30 Sachin Bal wrote:

Earlier, I remember when I clicked the source tab, it showed the source code which it is showing. And when I used to click the design tab, I could see a screen which I could modify. This is explained on (https://www.youtube.com/watch?v=kV5H3rGfqOE) at 3:00 min on the video.

I feel that I am missing something and it has been many years since I have used GWT Designer, and therefore cannot remember

Do you remember anything which could help me? Thanks

On Monday, October 30, 2023 at 7:10:14 PM UTC+5:30 Edu wrote:

Hi,

If i remember correctly if you already installed the Designer plugin you need to open the java file that is linked with that xml file using the Designer editor not the default one.

El lun, 30 oct 2023 a las 10:20, Sachin Bal (<sach...@gmail.com>) escribió:

Hi,

I installed Eclipse Kepler and when I open any ui.xml file, I can see two tabs, source and design. In the source, I can see the code but in the design I am not able to see the generated screen. I have a feeling that I have missed something but I cannot remember exactly. Can you please advise? Attached below is the source and design screens. It would be great, if you could guide me. Thanks

On Sunday, October 29, 2023 at 7:00:22 PM UTC+5:30 Sachin Bal wrote:

Thanks. I will check the old version of eclipse. I believe it was Eclipse Kepler which we had used earlier. 

Regards

Sachin

On Saturday, October 28, 2023 at 3:13:56 AM UTC+5:30 Colin Alworth wrote:

If memory serves, the GWT Designer tool was never part of GWT itself, but was a component that could be installed in Eclipse, allowing for WYSIWYG UI design (in part by running something like dev mode while you were editing?). Changes that the author of the project made were reflected in standard source files (.java and .ui.xml) that GWT itself was able to compile - as such, a newer compiler version can likely still compile (with small or minimal changes to source) such an old project. I would suggest small steps in upgrading, to keep such changes (if any) manageable.

If you're hoping to run GWT Designer itself, you probably need a very old version of eclipse - my memory here is that it wasn't used enough to be worth maintaining. The code still lives at https://github.com/gwt-plugins/gwt-designer, but I can't guess what it would take to bring it back to life. I have a memory of this being based on WindowBuilder, and some internal changes in WindowBuilder requiring substantial changes to the gwt-designer project, which never was done.

On Friday, October 27, 2023 at 3:19:36 PM UTC-5 sach...@gmail.com wrote:

Hi All,

We had created an application in 2014-2015. We had used GWT to design the UI of our application.  Unfortunately, we have folded that project in 2017 . I wanted to showcase our project to a prospective customer and was keen to know whether there is some way to migrate the project to the latest version of GWT? 

If that is not possible, I would like to display the screens which we had designed using GWT Designer so that I can at the least create a story around it.

Looking forward to some positive response

Please advise. 

Thanks

Sachin

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/1f61346d-1507-4f79-a26c-91e40655f2c7n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/f23e250f-0633-4638-bc36-637d6b8ebf4fn%40googlegroups.com.

Re: DominoKit has a new home

Congratulations to the whole team, great work 👌👌

On Fri, Nov 3, 2023, 09:06 Andrea Stocchero <stocki.nail@gmail.com> wrote:

well done guys!

Il giorno mercoledì 1 novembre 2023 alle 18:31:31 UTC+1 lofid...@gmail.com ha scritto:

Great work! Congrats!

Vegegoku schrieb am Dienstag, 31. Oktober 2023 um 09:41:19 UTC+1:

Exciting news — https://dominokit.com is live! Our new platform stands as a beacon of inclusion, unifying detailed documentation in one centralized location to empower and educate. We invite you to explore this collective reservoir of knowledge, designed to support and inspire. Please help us spread the word by sharing this resource with your network and beyond. Together, we can create a vast community of shared wisdom and resources.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/74c23d48-1d9b-47f9-b77d-d4e313ba9a96n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CALMWpTUDbSKteecL%3DcO2mijBmxVmqN8by1roc72N7dArBk6nPg%40mail.gmail.com.

Re: DominoKit has a new home

well done guys!

Il giorno mercoledì 1 novembre 2023 alle 18:31:31 UTC+1 lofid...@gmail.com ha scritto:

Great work! Congrats!

Vegegoku schrieb am Dienstag, 31. Oktober 2023 um 09:41:19 UTC+1:

Exciting news — https://dominokit.com is live! Our new platform stands as a beacon of inclusion, unifying detailed documentation in one centralized location to empower and educate. We invite you to explore this collective reservoir of knowledge, designed to support and inspire. Please help us spread the word by sharing this resource with your network and beyond. Together, we can create a vast community of shared wisdom and resources.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/74c23d48-1d9b-47f9-b77d-d4e313ba9a96n%40googlegroups.com.

Re: Illegal reflective access in RPC serializer

The workaround is to use --add-opens but this basically open the full java.util package for reflection which is not ideal. I also tried to replace the custom serializer, but due to the way custom serializers are loaded (using the exact package name), this doesn't seems possible without compiling a custom jar.

You can copy the file and put it into your source directory. However you must also make sure that the serializer is deployed on server side and not only compiled to JavaScript. Serializers supplied by GWT are in gwt-user.jar (for JS compilation) and in gwt-servlet.jar (server). The easiest solution is to fork GWT itself, apply the patch and build your own GWT SDK for now.

 There is a plan to release 2.11 but no concrete time frame: https://groups.google.com/g/google-web-toolkit-contributors/c/JfIAPN6XFCo

-- J.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/2e475bfa-4022-450a-9a4d-652c321ade34n%40googlegroups.com.

Re: DominoKit has a new home

Great work! Congrats!

Vegegoku schrieb am Dienstag, 31. Oktober 2023 um 09:41:19 UTC+1:

Exciting news — https://dominokit.com is live! Our new platform stands as a beacon of inclusion, unifying detailed documentation in one centralized location to empower and educate. We invite you to explore this collective reservoir of knowledge, designed to support and inspire. Please help us spread the word by sharing this resource with your network and beyond. Together, we can create a vast community of shared wisdom and resources.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/0fed71ba-6c21-45bc-a3b8-66a642036404n%40googlegroups.com.