Friday, October 15, 2021

Re: GWT 2.9 compatiblity with GXT 2.3.1a

The short answer is yes, you need to do this for each such bug you find, and if you have a commercial license, you need to do it yourself - the only way to distribute fixes for things like this is under GPLv2, which may not be something you want in your project as a dependency.

If this is a gwt compiler error, editing bytecode is not sufficient, as GWT consumes the source each time it builds. You probably should also update the bytecode if you update the source files. Only the file in question needs to be edited in this way (HtmlEditor, ListField are the ones I know of).

Do not replace with a .toString() call, in case the model holds an explicit null value, casting to object will use StringBuilder.append(Object), which will be null safe, or pick some other null safe approach.

Sencha's release policy at the time was that they supported the last major release - this means that until GXT 4 was released, GXT 2 was supported, and got updates, but once 4.0.0 was available, GXT 2 was no longer supported. To my knowledge, GXT isn't receiving any updates at all any more. Combined with the license issues, it is hard to do more than discuss the possible fixes and how they could be applied.

On Thursday, October 14, 2021 at 11:08:14 PM UTC-5 RT wrote:
Yes, I agree changing the line in the GXT 2.3.1a ListField.java file from:
sb.append(m.get(prop));

To this:
sb.append(m.get(prop).toString());

Would seemingly fix the issue. However I would then need to compile this to a .class file to replace the one in the gxt-2.3.1a-gwt22,jar that I reference in my project and therein lies the problem.  Must I track down all the dependencies for GXT and GWT so that I can do a full recompile from source just for this one line change? Or can I use a java byte code editor to simply insert the .toString() at the right place in the .class file for ListField? I'm not sure how to do that, so I'll have to read up on byte code editors as that seems easier than a full recompile - if I knew where and how to inject the .toString()

However if the OP already had GXT 2.3.1a working with GWT 2.8.2 then I'm guessing they already had to do this operation, and may be able to provide some insight. Unless they were using Java 7 and this is only a Java 8 issue perhaps.

On Wednesday, October 13, 2021 at 5:48:47 PM UTC-5 nilo...@gmail.com wrote:
The updated JDT probably caused this (so that gwt 2.8.2 can support Java 8 language features) - at a guess you'll need to cast the result of m.get(prop) on that line to Object so that StringBuilder.append correctly uses the Object overload.

On Wednesday, October 13, 2021 at 3:41:52 PM UTC-5 RT wrote:
Hi, I am attempting to update to GWT 2.8.2 from 2.7.0 using GXT 2.3.1a however I get the following error:
Errors in 'jar:file:/war/WEB-INF/lib/gxt-2.3.1a-gwt22.jar!/com/extjs/gxt/ui/client/widget/form/ListField.java'
         Line 322: The method append(boolean) is ambiguous for the type StringBuffer

How were you able to get 2.8.2 working with 2.3.1a?  I'm running Java 8 with compiler compliance set to 1.7

On Thursday, June 11, 2020 at 7:13:31 AM UTC-5 priyako...@gmail.com wrote:
Hi All,

Currently our application has below versions -
1. GWT - 2.8.2
2. GXT - 2.3.1a

We are planning to upgrade GWT from 2.8.2 to 2.9.0. But have query regarding its compatibility towards GXT 2.3.1a.
I have gone through GXT Compatiblity version matrix page, but found nowhere officially mentioned that its supported.
So can you please confirm that GWT 2.9 is officially supported with GXT 2.3.1a?

--
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/82fcc7c6-9397-470c-b76e-0c29dbf7ccdan%40googlegroups.com.

Thursday, October 14, 2021

Re: GWT 2.9 compatiblity with GXT 2.3.1a

Yes, I agree changing the line in the GXT 2.3.1a ListField.java file from:
sb.append(m.get(prop));

To this:
sb.append(m.get(prop).toString());

Would seemingly fix the issue. However I would then need to compile this to a .class file to replace the one in the gxt-2.3.1a-gwt22,jar that I reference in my project and therein lies the problem.  Must I track down all the dependencies for GXT and GWT so that I can do a full recompile from source just for this one line change? Or can I use a java byte code editor to simply insert the .toString() at the right place in the .class file for ListField? I'm not sure how to do that, so I'll have to read up on byte code editors as that seems easier than a full recompile - if I knew where and how to inject the .toString()

However if the OP already had GXT 2.3.1a working with GWT 2.8.2 then I'm guessing they already had to do this operation, and may be able to provide some insight. Unless they were using Java 7 and this is only a Java 8 issue perhaps.

On Wednesday, October 13, 2021 at 5:48:47 PM UTC-5 nilo...@gmail.com wrote:
The updated JDT probably caused this (so that gwt 2.8.2 can support Java 8 language features) - at a guess you'll need to cast the result of m.get(prop) on that line to Object so that StringBuilder.append correctly uses the Object overload.

On Wednesday, October 13, 2021 at 3:41:52 PM UTC-5 RT wrote:
Hi, I am attempting to update to GWT 2.8.2 from 2.7.0 using GXT 2.3.1a however I get the following error:
Errors in 'jar:file:/war/WEB-INF/lib/gxt-2.3.1a-gwt22.jar!/com/extjs/gxt/ui/client/widget/form/ListField.java'
         Line 322: The method append(boolean) is ambiguous for the type StringBuffer

How were you able to get 2.8.2 working with 2.3.1a?  I'm running Java 8 with compiler compliance set to 1.7

On Thursday, June 11, 2020 at 7:13:31 AM UTC-5 priyako...@gmail.com wrote:
Hi All,

Currently our application has below versions -
1. GWT - 2.8.2
2. GXT - 2.3.1a

We are planning to upgrade GWT from 2.8.2 to 2.9.0. But have query regarding its compatibility towards GXT 2.3.1a.
I have gone through GXT Compatiblity version matrix page, but found nowhere officially mentioned that its supported.
So can you please confirm that GWT 2.9 is officially supported with GXT 2.3.1a?

--
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/907adbec-b7e9-4ff5-98f5-adfa86159679n%40googlegroups.com.

Wednesday, October 13, 2021

Re: GWT 2.9 compatiblity with GXT 2.3.1a

The updated JDT probably caused this (so that gwt 2.8.2 can support Java 8 language features) - at a guess you'll need to cast the result of m.get(prop) on that line to Object so that StringBuilder.append correctly uses the Object overload.

On Wednesday, October 13, 2021 at 3:41:52 PM UTC-5 RT wrote:
Hi, I am attempting to update to GWT 2.8.2 from 2.7.0 using GXT 2.3.1a however I get the following error:
Errors in 'jar:file:/war/WEB-INF/lib/gxt-2.3.1a-gwt22.jar!/com/extjs/gxt/ui/client/widget/form/ListField.java'
         Line 322: The method append(boolean) is ambiguous for the type StringBuffer

How were you able to get 2.8.2 working with 2.3.1a?  I'm running Java 8 with compiler compliance set to 1.7

On Thursday, June 11, 2020 at 7:13:31 AM UTC-5 priyako...@gmail.com wrote:
Hi All,

Currently our application has below versions -
1. GWT - 2.8.2
2. GXT - 2.3.1a

We are planning to upgrade GWT from 2.8.2 to 2.9.0. But have query regarding its compatibility towards GXT 2.3.1a.
I have gone through GXT Compatiblity version matrix page, but found nowhere officially mentioned that its supported.
So can you please confirm that GWT 2.9 is officially supported with GXT 2.3.1a?

--
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/fc89baa3-122c-4f34-a1dd-278e64980bbbn%40googlegroups.com.

Re: porting older app from 2.5.0 to 2.8.2

Were you able to resolve the error in ListField?  I have the same error trying to get GWT 2.8.2 working with GXT 2.3.1a.

On Sunday, August 11, 2019 at 2:14:35 PM UTC-5 Blaze wrote:
Hi all,

I was wondering if some one can help me on this one...
I have a older app which uses gxt.2.2.5-gwt22.jar, and when compiling with gwt 2.8.2 Im getting some errors like this:

 [ERROR] Errors in 'jar:file:/xxxxx/gxt-2.2.5-gwt22.jar!/com/extjs/gxt/ui/client/widget/form/ListField.java'
     [java]                [ERROR] Line 322: The method append(boolean) is ambiguous for the type StringBuffer


  [ERROR] Errors in 'jar:file:/xxxxxx/gxt-2.2.5-gwt22.jar!/com/extjs/gxt/ui/client/widget/form/HtmlEditor.java'
     [java]                [ERROR] Line 548: Type mismatch: cannot convert from com.google.gwt.dom.client.Element to com.google.gwt.user.client.Element
     [java]          [ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly
    

Im guessing other gxt.jar file needs to be used, which adopts the small changes.
I searched on the net, found some but not sure if this are the one to go with. e.g a jar called gxt-2.3.1a-gwt22.jar, also this one on git: https://github.com/bedatadriven/gxt

Can some one give me some insides on this one, that would be great!!

Tnx in advance,
Blaze

        

--
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/7606987e-0a9e-4831-9944-47fb92540c41n%40googlegroups.com.

Re: GWT 2.9 compatiblity with GXT 2.3.1a

Hi, I am attempting to update to GWT 2.8.2 from 2.7.0 using GXT 2.3.1a however I get the following error:
Errors in 'jar:file:/war/WEB-INF/lib/gxt-2.3.1a-gwt22.jar!/com/extjs/gxt/ui/client/widget/form/ListField.java'
         Line 322: The method append(boolean) is ambiguous for the type StringBuffer

How were you able to get 2.8.2 working with 2.3.1a?  I'm running Java 8 with compiler compliance set to 1.7

On Thursday, June 11, 2020 at 7:13:31 AM UTC-5 priyako...@gmail.com wrote:
Hi All,

Currently our application has below versions -
1. GWT - 2.8.2
2. GXT - 2.3.1a

We are planning to upgrade GWT from 2.8.2 to 2.9.0. But have query regarding its compatibility towards GXT 2.3.1a.
I have gone through GXT Compatiblity version matrix page, but found nowhere officially mentioned that its supported.
So can you please confirm that GWT 2.9 is officially supported with GXT 2.3.1a?

--
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/a3091108-734e-471e-829c-7473b3fb65f1n%40googlegroups.com.

Re: 2/? Pbs with GWT + Eclipse + Jetty + Neo4J

Hi David,

For your last remark:
Another one is that you seem to want to use java introspection to dynamically load classes in GWT, which is not supported (Class.forName).
I think it's not a pb because this part is executed on the server side and all Java in this case is available.

Thanks for your help
Antonio



Le mer. 13 oct. 2021 à 12:03, David Nouls <david.nouls@gmail.com> a écrit :

I see multiple problems with your code. The most important being that you are ignoring the fact that an rpc call is asynchronous. So the load method will ralways return null because the request has not been executed when the method returns.

Another problem is the fact that the async is returning List<Object>, which would mean gwt needs to generate serializers for all object types in you application at compile time.

Another one is that you seem to want to use java introspection to dynamically load classes in GWT, which is not supported (Class.forName).
On 13 Oct 2021, 09:58 +0200, Guillen Antonio <tonio.guillen@gmail.com>, wrote:
HI all,

I am not comfortable with client-server and RPC and HTTPServlet operation at all.
I get the following message after my request:

200 - POST /spotgwt/spotData (127.0.0.1) 496 bytes
   Request headers
      Host: 127.0.0.1:8887
      User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0
      Accept: */*
      Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3
      Accept-Encoding: gzip, deflate
      Content-Type: text/x-gwt-rpc; charset=utf-8
      X-GWT-Permutation: A082E84D087467DED16699006D694A7B
      X-GWT-Module-Base: http://127.0.0.1:8887/spotgwt/
      Content-Length: 228
      Origin: http://127.0.0.1:8887
      DNT: 1
      Connection: keep-alive
      Referer: http://127.0.0.1:8887/SpotGWT.html
      Sec-Fetch-Dest: empty
      Sec-Fetch-Mode: cors
      Sec-Fetch-Site: same-origin
   Response headers
      Date: Wed, 13 Oct 2021 07:40:08 GMT
      Content-Encoding: gzip
      Content-Length: 496
      Content-Type: application/json; charset=utf-8
      Content-Disposition: attachment

Can you tell me what this means. Because at first glance I understand that my request is successful, and  the content of the response is in a zip and that the length of the zip is 496 bytes in json format. Attachment ?????

The problem is that my RPC call tells me that it has failed in the following piece of code:


<image.png>
I look forward to your reply.
Thanks a lot for your help
Antonio

--
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/CAKULUq_jF_Z96s43u_Gm7Z6omqU6H7fQ8758DmTX8yavu1mBMg%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/48970e18-bc80-4df0-b8d7-84adde1c63cb%40Spark.

--
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/CAKULUq9StShWVmmRKvDqccgoqE670BNcSHfdkz-5b5EmTuxNpw%40mail.gmail.com.

Wednesday, September 15, 2021

Re: [ANN] Akasha: Typed Browser API version 0.24 released

Hi,

On Wed, Sep 15, 2021 at 6:27 PM Jens <jens.nehlmeier@gmail.com> wrote:
really interesting work, but don't you think something like feature detection should be handled by a dedicated library like Modernizr for example? You likely want to check for vendor prefixed support when you do feature detection.

It depends upon the actual feature detection that is taking place. All the akasha stuff does is check whether a property/function is present on an object. So mostly it allows you to replace something like:

if (Js.global().has("indexedDB")) { /* perform logic requiring indexDB */ }

with:

if (WindowGlobal.isIndexedDBSupported()) { /* perform logic requiring indexDB */ }

Largely Akasha assumes that browsers conform with the HTML Living document (or whatever it is called) or the underlying spec and only presents the prefixes that are declared as part of the living document. If you want to perform more complex feature detection and polyfills (i.e. assigning prefixed version to unprefixed property or adding polyfills or detecting non-code related features such as css properties) then going with a dedicated library is a better option. 

Mostly we have found that our needs are served with pretty simple feature detection but YMMV
 
--
Cheers,

Peter Donald

--
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/CACiKNc6Yrhv1E_oMKiP8TBzMHOhHkj%2BULXNnh98Sup8NmG5rMw%40mail.gmail.com.