Tuesday, December 3, 2024

Re: Chrome SecurityError: Failed to execute 'pushState' on 'History'

First... you should update this to use jsinterop - consider just adding elemental2-dom to your project and calling DomGlobal.history.pushState(new Object(), "", historyRewrite); in plain Java?

To answer the question more directly, you probably need to change "window" to "$wnd" to access the actual outer window. Your current code, as written, is technically attempting to change the URL of the iframe that the app is loaded in.
On Tuesday, December 3, 2024 at 11:43:00 AM UTC-6 Lonzak wrote:
I successfully updated GWT from 2.10.1 to 2.12.1.
In Firefox everything works perfectly however not in chrome based browsers. When I try to
execute the following code:

public static native int setHistory(String historyRewrite) /*-{

window.history.pushState({}, '', historyRewrite);

}-*/;


Error:
SEVERE: (SecurityError) : Failed to execute 'pushState' on 'History': A history state object with URL 'https://company.url/home' cannot be created in a document
with origin 'https://company.url' and URL 'about:blank'.
com.google.gwt.core.client.JavaScriptException: (SecurityError) : Failed to execute 'pushState' on 'History': A history state object with URL
'https://company.url/home' cannot be created in a document with origin 'https://company.url' and URL 'about:blank'.

If I revert to GWT it works again.
Any idea what changed (and how to fix it)?
Is the script maybe loaded before the document is fully loaded?

Thanks!

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/823d20ba-4973-436d-813d-815ec143a792n%40googlegroups.com.

Chrome SecurityError: Failed to execute 'pushState' on 'History'

I successfully updated GWT from 2.10.1 to 2.12.1.
In Firefox everything works perfectly however not in chrome based browsers. When I try to
execute the following code:

public static native int setHistory(String historyRewrite) /*-{

window.history.pushState({}, '', historyRewrite);

}-*/;


Error:
SEVERE: (SecurityError) : Failed to execute 'pushState' on 'History': A history state object with URL 'https://company.url/home' cannot be created in a document
with origin 'https://company.url' and URL 'about:blank'.
com.google.gwt.core.client.JavaScriptException: (SecurityError) : Failed to execute 'pushState' on 'History': A history state object with URL
'https://company.url/home' cannot be created in a document with origin 'https://company.url' and URL 'about:blank'.

If I revert to GWT it works again.
Any idea what changed (and how to fix it)?
Is the script maybe loaded before the document is fully loaded?

Thanks!

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/c51129ca-0e5f-4b0e-9314-b326cff23aafn%40googlegroups.com.

Re: Servlet problem after upgrade

If you are using jakarta.servlet, you shouldn't need to do any bytecode fixing, provided you are depending on gwt-servlet-jakarta.jar and have changed your servlet implementation to extend from com.google.gwt.user.server.rpc.jakarta.RemoteServiceServlet.

If you aren't getting any error except 404, that suggests to me that the servlet isn't configured to be loaded at all - can you confirm that it is listed in the web.xml? If instead you are using annotations for discovery, confirm it is jakarta.servlet.annotation.WebServlet rather than javax, and consider adding some logging to verify that your servlet is having its constructor and init(config) method called at all. If not, something is probably misconfigured in how you are signaling to your servlet container how it should find and load the required servlets.

On Tuesday, December 3, 2024 at 6:04:49 AM UTC-6 dav...@googlemail.com wrote:
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 GET is not supported; but I still get a 404.

Prompted by your replies, I saw I had neglected  to update the ant build file with gwt-servlet-jakarta.jar instead of gwt-servlet.jar, but nothing else you suggested seems to apply. The web.xml and <project>.gwt.xml files are unchanged  and nothing else on the production server (apache, tomcat) has changed.

I again tried replacing the server class with a byte enhanced version as I need to do with 2.10.0,  but although it does add a few bytes, still  I get the 404. Nothing in either apache or tomcat logs apart from the 404s and 405s

On Monday, 2 December 2024 at 14:41:12 UTC SHAIK FAYAZ wrote:

Almost path problem it would be or check the path names correctly


On Sun, Dec 1, 2024, 7:05 AM SHAIK FAYAZ <sfay...@gmail.com> wrote:

1. Check How the Servlet is Set Up
Look at the file where your servlet is connected to a URL, like web.xml or in your annotations (comments in the code). Make sure the URL path for your servlet is correct, so it gets triggered when you visit the right link.
2. Ensure You Updated All Java Imports
When you updated from version 2.10.0 to 2.12.1, you need to check if your code is using the updated jakarta.* package instead of javax.*. Some of the old names have changed, so make sure everything is up to date.
3. Make Sure Your Tomcat Version Works with the New Code
If you're using an older version of Tomcat (like version 9 or below), it may not work with the updated jakarta.* code. Make sure you're using Tomcat version 10 or higher, which supports this newer format.
4. Check if Your Servlet Supports GET or POST Methods
Earlier, you got a "405" error, which means the servlet was not set up to handle certain requests like GET. You need to make sure that your servlet is set up to handle the right type of requests.
5. Check Apache Proxy Settings
If you're using Apache to forward requests to Tomcat, make sure Apache is set up correctly so that it passes the requests properly. A wrong setting could cause the "404" error you're seeing now.
6. Look at Logs for Clues
Check both the Tomcat and Apache logs. They might give you more details about what's going wrong and help identify the issue.
7. Issues with Code Enhancers
If you're using tools that automatically modify your code (like Hibernate or other libraries), check to make sure they're compatible with the new version (2.12.1). These tools sometimes cause problems when you upgrade versions.


On Sun, Dec 1, 2024, 5:31 AM Jens <jens.ne...@gmail.com> wrote:
GWT doesn't really have any servlet magic so I doubt that the GWT upgrade has caused the issue. Are you double sure you haven't changed anything else except the GWT library? No Tomcat update? No Apache update? No update of Apache proxy rules? 

It sounds like your servlet is a GWT-RPC service because you used the Jakarta migration tool. If that is true you can now use gwt-servlet-jakarta.jar and skip the migration tool.

-- J.

dav...@googlemail.com schrieb am Samstag, 30. November 2024 um 17:27:59 UTC+1:
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 through the jakartaee migration tool to make it work. With everything ok, if you browse to the servlet you get a 405 as the GET method is not supported,  although that confirms the servlet is running.

With unchanged code everything compiles with 2.12.1,  but the servlet will not run. I've tried both the standard compiled class and its byte enhanced version. Both give a 404 and the ip is not available to client code. The client code itself otherwise runs as expected.

Any pointers towards a fix?


--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/dda2b7e2-3565-4f79-ac99-b90f8cac9522n%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 visit https://groups.google.com/d/msgid/google-web-toolkit/2550068c-b12a-441b-9595-ad51450f00d2n%40googlegroups.com.

Re: Servlet problem after upgrade

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 GET is not supported; but I still get a 404.

Prompted by your replies, I saw I had neglected  to update the ant build file with gwt-servlet-jakarta.jar instead of gwt-servlet.jar, but nothing else you suggested seems to apply. The web.xml and <project>.gwt.xml files are unchanged  and nothing else on the production server (apache, tomcat) has changed.

I again tried replacing the server class with a byte enhanced version as I need to do with 2.10.0,  but although it does add a few bytes, still  I get the 404. Nothing in either apache or tomcat logs apart from the 404s and 405s

On Monday, 2 December 2024 at 14:41:12 UTC SHAIK FAYAZ wrote:

Almost path problem it would be or check the path names correctly


On Sun, Dec 1, 2024, 7:05 AM SHAIK FAYAZ <sfay...@gmail.com> wrote:

1. Check How the Servlet is Set Up
Look at the file where your servlet is connected to a URL, like web.xml or in your annotations (comments in the code). Make sure the URL path for your servlet is correct, so it gets triggered when you visit the right link.
2. Ensure You Updated All Java Imports
When you updated from version 2.10.0 to 2.12.1, you need to check if your code is using the updated jakarta.* package instead of javax.*. Some of the old names have changed, so make sure everything is up to date.
3. Make Sure Your Tomcat Version Works with the New Code
If you're using an older version of Tomcat (like version 9 or below), it may not work with the updated jakarta.* code. Make sure you're using Tomcat version 10 or higher, which supports this newer format.
4. Check if Your Servlet Supports GET or POST Methods
Earlier, you got a "405" error, which means the servlet was not set up to handle certain requests like GET. You need to make sure that your servlet is set up to handle the right type of requests.
5. Check Apache Proxy Settings
If you're using Apache to forward requests to Tomcat, make sure Apache is set up correctly so that it passes the requests properly. A wrong setting could cause the "404" error you're seeing now.
6. Look at Logs for Clues
Check both the Tomcat and Apache logs. They might give you more details about what's going wrong and help identify the issue.
7. Issues with Code Enhancers
If you're using tools that automatically modify your code (like Hibernate or other libraries), check to make sure they're compatible with the new version (2.12.1). These tools sometimes cause problems when you upgrade versions.


On Sun, Dec 1, 2024, 5:31 AM Jens <jens.ne...@gmail.com> wrote:
GWT doesn't really have any servlet magic so I doubt that the GWT upgrade has caused the issue. Are you double sure you haven't changed anything else except the GWT library? No Tomcat update? No Apache update? No update of Apache proxy rules? 

It sounds like your servlet is a GWT-RPC service because you used the Jakarta migration tool. If that is true you can now use gwt-servlet-jakarta.jar and skip the migration tool.

-- J.

dav...@googlemail.com schrieb am Samstag, 30. November 2024 um 17:27:59 UTC+1:
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 through the jakartaee migration tool to make it work. With everything ok, if you browse to the servlet you get a 405 as the GET method is not supported,  although that confirms the servlet is running.

With unchanged code everything compiles with 2.12.1,  but the servlet will not run. I've tried both the standard compiled class and its byte enhanced version. Both give a 404 and the ip is not available to client code. The client code itself otherwise runs as expected.

Any pointers towards a fix?


--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/dda2b7e2-3565-4f79-ac99-b90f8cac9522n%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 visit https://groups.google.com/d/msgid/google-web-toolkit/4b67b00a-18be-4a16-97cb-8caffdb80170n%40googlegroups.com.

Monday, December 2, 2024

Re: Firefox - mouse wheel

Yes, that old one. 

Well, there is some recent activity there, so I hope this maybe could be fixed.

Thx.




pá 29. 11. 2024 v 9:01 odesílatel Thomas Broyer <t.broyer@gmail.com> napsal:


On Friday, November 29, 2024 at 8:36:48 AM UTC+1 had...@digitech.cz wrote:
Thanks, 

I am using gwt-openlayers-client 1.1.0, not TDesjardins/gwt-ol.

The one released nearly 8 years ago‽

It apparently doesn't use mousewheel event itself either, like GWT-OL (and I see you opened an issue there)

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/307120d6-87b8-4c28-9fc1-2e68f88d9197n%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 visit https://groups.google.com/d/msgid/google-web-toolkit/CAOvMoHWigrJwZ3hgQ2fSfaDBGujeK3%2BVx98o40N_kvqG8R6pgg%40mail.gmail.com.

Re: A GWT components library - how to organize for Uibinder use?

Not saying this is the correct way, but I just have my simple common widgets in the one package, and specialised widgets in their own package.  Ie:

<ui:UiBinder
  xmlns:ui="urn:ui:com.google.gwt.uibinder"
  xmlns:g="urn:import:com.google.gwt.user.client.ui"
  xmlns:w="urn:import:mypackage.widgets"
  xmlns:s="urn:import:
mypackage.widgets.special">

<w:Button ui:field="myButton" />
<w:Link ui:field="myLink" />
<s:SpecialWidget ui:field="mySpecialWidget" />

On Sunday, 1 December 2024 at 3:59:36 pm UTC+11 cbruno...@gmail.com wrote:
Thanks Jens. This is my first Java project where I am sole architect. I ended up doing what you recommended, although I moved the ui.xml and css files into a sub-package to keep the top level package as clutter free as possible. 



On Saturday, November 30, 2024 at 5:49:08 PM UTC-6 Jens wrote:
UiBinder is XML and you have to import the package as namespace in order to use the components. Personally I would not create another package with classes extending the implementation because both classes would be public and both can be used in UiBinder then. That is likely confusing. I would put all components in the same package. Package private classes supporting a component could have the component name as prefix so they form a group in your IDE through sorting.

-- J.

cbruno...@gmail.com schrieb am Freitag, 29. November 2024 um 20:20:57 UTC+1:
Hello,

Im creating a component library for GWT and I want to be able to use the components in UI binder. However, when implementing my components, each component gets its own package, containing styles, and package private classes needed to build the component. 

However, to use in Uibinder, I need to do something like <m:button.Button text="Click" />

where m points to the package with my components.

Whats is bugging me is the extra "button" in the declaration. Is there anyway to flatten this aside from creating another package with objects simply extending the implementation ?

Thanks

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/8d6bd10a-274a-4581-b01f-e6bf054d9cf9n%40googlegroups.com.

Saturday, November 30, 2024

Re: A GWT components library - how to organize for Uibinder use?

Thanks Jens. This is my first Java project where I am sole architect. I ended up doing what you recommended, although I moved the ui.xml and css files into a sub-package to keep the top level package as clutter free as possible. 



On Saturday, November 30, 2024 at 5:49:08 PM UTC-6 Jens wrote:
UiBinder is XML and you have to import the package as namespace in order to use the components. Personally I would not create another package with classes extending the implementation because both classes would be public and both can be used in UiBinder then. That is likely confusing. I would put all components in the same package. Package private classes supporting a component could have the component name as prefix so they form a group in your IDE through sorting.

-- J.

cbruno...@gmail.com schrieb am Freitag, 29. November 2024 um 20:20:57 UTC+1:
Hello,

Im creating a component library for GWT and I want to be able to use the components in UI binder. However, when implementing my components, each component gets its own package, containing styles, and package private classes needed to build the component. 

However, to use in Uibinder, I need to do something like <m:button.Button text="Click" />

where m points to the package with my components.

Whats is bugging me is the extra "button" in the declaration. Is there anyway to flatten this aside from creating another package with objects simply extending the implementation ?

Thanks

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/6d1ef7bb-7da9-4027-9bb0-2a3d3d2c5d51n%40googlegroups.com.

Re: Servlet problem after upgrade

Almost path problem it would be or check the path names correctly


On Sun, Dec 1, 2024, 7:05 AM SHAIK FAYAZ <sfayazmr@gmail.com> wrote:

1. Check How the Servlet is Set Up
Look at the file where your servlet is connected to a URL, like web.xml or in your annotations (comments in the code). Make sure the URL path for your servlet is correct, so it gets triggered when you visit the right link.
2. Ensure You Updated All Java Imports
When you updated from version 2.10.0 to 2.12.1, you need to check if your code is using the updated jakarta.* package instead of javax.*. Some of the old names have changed, so make sure everything is up to date.
3. Make Sure Your Tomcat Version Works with the New Code
If you're using an older version of Tomcat (like version 9 or below), it may not work with the updated jakarta.* code. Make sure you're using Tomcat version 10 or higher, which supports this newer format.
4. Check if Your Servlet Supports GET or POST Methods
Earlier, you got a "405" error, which means the servlet was not set up to handle certain requests like GET. You need to make sure that your servlet is set up to handle the right type of requests.
5. Check Apache Proxy Settings
If you're using Apache to forward requests to Tomcat, make sure Apache is set up correctly so that it passes the requests properly. A wrong setting could cause the "404" error you're seeing now.
6. Look at Logs for Clues
Check both the Tomcat and Apache logs. They might give you more details about what's going wrong and help identify the issue.
7. Issues with Code Enhancers
If you're using tools that automatically modify your code (like Hibernate or other libraries), check to make sure they're compatible with the new version (2.12.1). These tools sometimes cause problems when you upgrade versions.


On Sun, Dec 1, 2024, 5:31 AM Jens <jens.nehlmeier@gmail.com> wrote:
GWT doesn't really have any servlet magic so I doubt that the GWT upgrade has caused the issue. Are you double sure you haven't changed anything else except the GWT library? No Tomcat update? No Apache update? No update of Apache proxy rules? 

It sounds like your servlet is a GWT-RPC service because you used the Jakarta migration tool. If that is true you can now use gwt-servlet-jakarta.jar and skip the migration tool.

-- J.

dav...@googlemail.com schrieb am Samstag, 30. November 2024 um 17:27:59 UTC+1:
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 through the jakartaee migration tool to make it work. With everything ok, if you browse to the servlet you get a 405 as the GET method is not supported,  although that confirms the servlet is running.

With unchanged code everything compiles with 2.12.1,  but the servlet will not run. I've tried both the standard compiled class and its byte enhanced version. Both give a 404 and the ip is not available to client code. The client code itself otherwise runs as expected.

Any pointers towards a fix?


--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/dda2b7e2-3565-4f79-ac99-b90f8cac9522n%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 visit https://groups.google.com/d/msgid/google-web-toolkit/CAJc24SZSpv%2Btkg0dSw3diQHFEg5GTLn57Uq%2B6WUX%2Bq8oMSJsqQ%40mail.gmail.com.

Re: Servlet problem after upgrade

1. Check How the Servlet is Set Up
Look at the file where your servlet is connected to a URL, like web.xml or in your annotations (comments in the code). Make sure the URL path for your servlet is correct, so it gets triggered when you visit the right link.
2. Ensure You Updated All Java Imports
When you updated from version 2.10.0 to 2.12.1, you need to check if your code is using the updated jakarta.* package instead of javax.*. Some of the old names have changed, so make sure everything is up to date.
3. Make Sure Your Tomcat Version Works with the New Code
If you're using an older version of Tomcat (like version 9 or below), it may not work with the updated jakarta.* code. Make sure you're using Tomcat version 10 or higher, which supports this newer format.
4. Check if Your Servlet Supports GET or POST Methods
Earlier, you got a "405" error, which means the servlet was not set up to handle certain requests like GET. You need to make sure that your servlet is set up to handle the right type of requests.
5. Check Apache Proxy Settings
If you're using Apache to forward requests to Tomcat, make sure Apache is set up correctly so that it passes the requests properly. A wrong setting could cause the "404" error you're seeing now.
6. Look at Logs for Clues
Check both the Tomcat and Apache logs. They might give you more details about what's going wrong and help identify the issue.
7. Issues with Code Enhancers
If you're using tools that automatically modify your code (like Hibernate or other libraries), check to make sure they're compatible with the new version (2.12.1). These tools sometimes cause problems when you upgrade versions.


On Sun, Dec 1, 2024, 5:31 AM Jens <jens.nehlmeier@gmail.com> wrote:
GWT doesn't really have any servlet magic so I doubt that the GWT upgrade has caused the issue. Are you double sure you haven't changed anything else except the GWT library? No Tomcat update? No Apache update? No update of Apache proxy rules? 

It sounds like your servlet is a GWT-RPC service because you used the Jakarta migration tool. If that is true you can now use gwt-servlet-jakarta.jar and skip the migration tool.

-- J.

dav...@googlemail.com schrieb am Samstag, 30. November 2024 um 17:27:59 UTC+1:
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 through the jakartaee migration tool to make it work. With everything ok, if you browse to the servlet you get a 405 as the GET method is not supported,  although that confirms the servlet is running.

With unchanged code everything compiles with 2.12.1,  but the servlet will not run. I've tried both the standard compiled class and its byte enhanced version. Both give a 404 and the ip is not available to client code. The client code itself otherwise runs as expected.

Any pointers towards a fix?


--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/dda2b7e2-3565-4f79-ac99-b90f8cac9522n%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 visit https://groups.google.com/d/msgid/google-web-toolkit/CAJc24SZY4sR0k%3DmDm7YZDNzmaE0Mn_aOxm2J_kkH6m8dW1wNWA%40mail.gmail.com.

Re: Servlet problem after upgrade

GWT doesn't really have any servlet magic so I doubt that the GWT upgrade has caused the issue. Are you double sure you haven't changed anything else except the GWT library? No Tomcat update? No Apache update? No update of Apache proxy rules? 

It sounds like your servlet is a GWT-RPC service because you used the Jakarta migration tool. If that is true you can now use gwt-servlet-jakarta.jar and skip the migration tool.

-- J.

dav...@googlemail.com schrieb am Samstag, 30. November 2024 um 17:27:59 UTC+1:
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 through the jakartaee migration tool to make it work. With everything ok, if you browse to the servlet you get a 405 as the GET method is not supported,  although that confirms the servlet is running.

With unchanged code everything compiles with 2.12.1,  but the servlet will not run. I've tried both the standard compiled class and its byte enhanced version. Both give a 404 and the ip is not available to client code. The client code itself otherwise runs as expected.

Any pointers towards a fix?


--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/dda2b7e2-3565-4f79-ac99-b90f8cac9522n%40googlegroups.com.

Re: A GWT components library - how to organize for Uibinder use?

UiBinder is XML and you have to import the package as namespace in order to use the components. Personally I would not create another package with classes extending the implementation because both classes would be public and both can be used in UiBinder then. That is likely confusing. I would put all components in the same package. Package private classes supporting a component could have the component name as prefix so they form a group in your IDE through sorting.

-- J.

cbruno...@gmail.com schrieb am Freitag, 29. November 2024 um 20:20:57 UTC+1:
Hello,

Im creating a component library for GWT and I want to be able to use the components in UI binder. However, when implementing my components, each component gets its own package, containing styles, and package private classes needed to build the component. 

However, to use in Uibinder, I need to do something like <m:button.Button text="Click" />

where m points to the package with my components.

Whats is bugging me is the extra "button" in the declaration. Is there anyway to flatten this aside from creating another package with objects simply extending the implementation ?

Thanks

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/5186c8d1-ab87-4741-b4f9-54f4d579dd24n%40googlegroups.com.

Servlet problem after upgrade

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 through the jakartaee migration tool to make it work. With everything ok, if you browse to the servlet you get a 405 as the GET method is not supported,  although that confirms the servlet is running.

With unchanged code everything compiles with 2.12.1,  but the servlet will not run. I've tried both the standard compiled class and its byte enhanced version. Both give a 404 and the ip is not available to client code. The client code itself otherwise runs as expected.

Any pointers towards a fix?


--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/cffd13f6-80f3-44fd-9351-5db19d16ce58n%40googlegroups.com.

Friday, November 29, 2024

A GWT components library - how to organize for Uibinder use?

Hello,

Im creating a component library for GWT and I want to be able to use the components in UI binder. However, when implementing my components, each component gets its own package, containing styles, and package private classes needed to build the component. 

However, to use in Uibinder, I need to do something like <m:button.Button text="Click" />

where m points to the package with my components.

Whats is bugging me is the extra "button" in the declaration. Is there anyway to flatten this aside from creating another package with objects simply extending the implementation ?

Thanks

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/5b19f21c-ab5c-4d51-8396-99869b844fc4n%40googlegroups.com.

Re: Firefox - mouse wheel



On Friday, November 29, 2024 at 8:36:48 AM UTC+1 had...@digitech.cz wrote:
Thanks, 

I am using gwt-openlayers-client 1.1.0, not TDesjardins/gwt-ol.

The one released nearly 8 years ago‽

It apparently doesn't use mousewheel event itself either, like GWT-OL (and I see you opened an issue there)

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/307120d6-87b8-4c28-9fc1-2e68f88d9197n%40googlegroups.com.

Thursday, November 28, 2024

Re: Firefox - mouse wheel

Thanks, 

I am using gwt-openlayers-client 1.1.0, not TDesjardins/gwt-ol.



čt 28. 11. 2024 v 12:53 odesílatel Thomas Broyer <t.broyer@gmail.com> napsal:
Most likely culprit from the release notes:
  • The mousewheel event has been deprecated in browsers, its usage in GWT has been replaced with the wheel event. This should be transparent to applications.

That being said, GWT-OL doesn't itself handles those events so possibly unrelated actually.

Wrt permutations, this is due to removal of support for IE 8, 9 and 10 in 2.10.0, leaving only "safari" (for all WebKit or Chromium based browsers) and "gecko1_8" (for Firefox and IE 11)

On Thursday, November 28, 2024 at 12:25:15 PM UTC+1 had...@digitech.cz wrote:
I upgraded GWT from 2.8 to 2.12, and in Firefox mouse wheel scroll stopped  working in some components (notably GwtOpenLayers component). 

I noted that previously my project had 5 permutations, now it is 2 permutations:

Compiling 2 permutations
     Compiling permutation 0...
      Compiling permutation 1...

So, perhaps these iterations are related to various browser engine support, and I have Firefox support disabled (wild guess)? Somebody with similar problem in Firefox?

Mirza

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/1ddc9b3b-348c-43fb-992f-8eb1f677cee5n%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 visit https://groups.google.com/d/msgid/google-web-toolkit/CAOvMoHXqz_p6MxPYaFjG1uy%3Dq_Ms-yNLT%3DtvbYN17jBJK%2BqxOw%40mail.gmail.com.

Re: Firefox - mouse wheel

Most likely culprit from the release notes:
  • The mousewheel event has been deprecated in browsers, its usage in GWT has been replaced with the wheel event. This should be transparent to applications.

That being said, GWT-OL doesn't itself handles those events so possibly unrelated actually.

Wrt permutations, this is due to removal of support for IE 8, 9 and 10 in 2.10.0, leaving only "safari" (for all WebKit or Chromium based browsers) and "gecko1_8" (for Firefox and IE 11)

On Thursday, November 28, 2024 at 12:25:15 PM UTC+1 had...@digitech.cz wrote:
I upgraded GWT from 2.8 to 2.12, and in Firefox mouse wheel scroll stopped  working in some components (notably GwtOpenLayers component). 

I noted that previously my project had 5 permutations, now it is 2 permutations:

Compiling 2 permutations
     Compiling permutation 0...
      Compiling permutation 1...

So, perhaps these iterations are related to various browser engine support, and I have Firefox support disabled (wild guess)? Somebody with similar problem in Firefox?

Mirza

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/1ddc9b3b-348c-43fb-992f-8eb1f677cee5n%40googlegroups.com.

Firefox - mouse scroll

Hello,

I upgraded GWT from 2.8 to 2.12, and in Firefox mouse wheel scroll stopped  working in some components (notably GwtOpenLayers component). 

I noted that previously my project had 5 permutations, now it is 2 permutations:

Compiling 2 permutations
     Compiling permutation 0...
      Compiling permutation 1...

So, perhaps these iterations are related to various browser engine support, and I have Firefox support disabled (wild guess)? Somebody with similar problem in Firefox?

Mirza

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/CAOvMoHXb-uUUYGH8FmdaOKem%2Bj1i%3Dbx4vbUZc_qCSaWTXhPtEA%40mail.gmail.com.

Thursday, November 21, 2024

Re: Issue with enhanced switch statements in GWT 2.12.1

Thanks, this was filed at https://github.com/gwtproject/gwt/issues/10044. The issue is that we misunderstood how the JDT AST handled this case (assumed it was a block ending in a break, rather than a yield with a void expression, which isn't legal in Java), and the tests didn't check for flow in the method after the switch was finished (it is a little awkward to put an assert after a code block and validate not just that it passes but was run at all. We'll get this fixed soon, with better tests as well.

On Thursday, November 21, 2024 at 4:17:32 AM UTC-6 vas...@gmail.com wrote:
lack of caffeine indeed.

Somehow the sentence that was explaining the problem disappeared for me between scrolls..

Sorry

On Thu, Nov 21, 2024 at 10:38 AM Vassilis Virvilis <vas...@gmail.com> wrote:
I must be low on caffeine because I can't see the problem.

Is the problem that it doesn't print:
Test 2 - Done
at the end?

On Thu, Nov 21, 2024 at 10:28 AM Craig Mitchell <ma...@craig-mitchell.com> wrote:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:
Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/d0b4fe79-0571-481a-bf4f-c8ccda40e486n%40googlegroups.com.


--
Vassilis Virvilis


--
Vassilis Virvilis

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/51661537-7faf-4e9f-a6e5-41e331f17e8fn%40googlegroups.com.

Re: Issue with enhanced switch statements in GWT 2.12.1

lack of caffeine indeed.

Somehow the sentence that was explaining the problem disappeared for me between scrolls..

Sorry

On Thu, Nov 21, 2024 at 10:38 AM Vassilis Virvilis <vasvir2@gmail.com> wrote:
I must be low on caffeine because I can't see the problem.

Is the problem that it doesn't print:
Test 2 - Done
at the end?

On Thu, Nov 21, 2024 at 10:28 AM Craig Mitchell <mail@craig-mitchell.com> wrote:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:
Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/d0b4fe79-0571-481a-bf4f-c8ccda40e486n%40googlegroups.com.


--
Vassilis Virvilis


--
Vassilis Virvilis

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/CAKbOjEwsxyVcvfy_7nvPfn%3DYb%2BQr9pDBU6xcOYtOcu1gvk1xFg%40mail.gmail.com.

Re: Issue with enhanced switch statements in GWT 2.12.1

Thanks Thomas.  Yes, that's the same issue.  I've now commented on it.  Cheers.

On Thursday, 21 November 2024 at 8:04:39 pm UTC+11 Thomas Broyer wrote:
Could be related to https://github.com/gwtproject/gwt/issues/10044

Fwiw, the issue fixed in 2.12.1 was not about the "case x -> foo" vs "case x -> { foo }" but about enclosing the whole switch inside a block.

On Thursday, November 21, 2024 at 9:28:51 AM UTC+1 ma...@craig-mitchell.com wrote:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:
Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/813a36c4-81cc-44af-97ab-48cfdb04289fn%40googlegroups.com.

Re: Issue with enhanced switch statements in GWT 2.12.1

Could be related to https://github.com/gwtproject/gwt/issues/10044

Fwiw, the issue fixed in 2.12.1 was not about the "case x -> foo" vs "case x -> { foo }" but about enclosing the whole switch inside a block.

On Thursday, November 21, 2024 at 9:28:51 AM UTC+1 ma...@craig-mitchell.com wrote:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:
Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/2ce64938-712b-4d56-902a-5a922a5d158dn%40googlegroups.com.

Re: Issue with enhanced switch statements in GWT 2.12.1

I must be low on caffeine because I can't see the problem.

Is the problem that it doesn't print:
Test 2 - Done
at the end?

On Thu, Nov 21, 2024 at 10:28 AM Craig Mitchell <mail@craig-mitchell.com> wrote:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:
Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/d0b4fe79-0571-481a-bf4f-c8ccda40e486n%40googlegroups.com.


--
Vassilis Virvilis

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/CAKbOjEytjRYrFc4FDmgwagH_CpWCPkW6eWf2F_pW_ywqmAXb-g%40mail.gmail.com.

Issue with enhanced switch statements in GWT 2.12.1

The release notes for 2.12.1 ( https://www.gwtproject.org/release-notes.html#Release_Notes_2_12_1 ) say:

> Switch statements can correctly compile without being contained in braces

For me, they compile, but they don't work.  Eg.  This code:

GWT.log("Test 1 - Start");
switch (1) {
  case 1 -> {
    GWT.log("Test 1 - 1");
  }
  case 2 -> {
    GWT.log("Test 1 - 2");
  }
  case 3 -> {
    GWT.log("Test 1 - 3");
  }
}
GWT.log("Test 1 - Done");

GWT.log("Test 2 - Start");
switch (1) {
  case 1 -> GWT.log("Test 2 - 1");
  case 2 -> GWT.log("Test 2 - 2");
  case 3 -> GWT.log("Test 2 - 3");
}
GWT.log("Test 2 - Done");

Will never get to the last "Test 2 - Done" line.  The output will be:
Test 1 - Start
Test 1 - 1
Test 1 - Done
Test 2 - Start
Test 2 - 1

Is this a known issue?

Thanks.

--
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 visit https://groups.google.com/d/msgid/google-web-toolkit/d0b4fe79-0571-481a-bf4f-c8ccda40e486n%40googlegroups.com.