Re: java.lang.ClassNotFoundException: javax.sql.DataSource when using GWT 2.9.0 + Java 11 combination

[Rob Newton]

Yes it seems that you need to run it in a separate servlet container, but 
it doesn't have to be Tomcat.  You can use Jetty so long as it is fairly 
recent (unlike the old version embedded in GWT dev mode).

On Friday, July 1, 2022 at 4:57:50 AM UTC+10 ora...@gmail.com wrote:

> I am not sure if it is the same issue but when  I switched to Java 11 I 
> had the following: 
>
> "Server class 'javax.sql.DataSource' could not be found in the web app, 
> but was found on the system classpath
> [ERROR] Found resouce but unrecognized URL format: '
> jrt:/java.sql/javax/sql/DataSource.class 
> '"
>
> In according to https://github.com/gwtproject/gwt/issues/9582 there is an 
> issue with JettyLauncher. And it is recommended to use "CodeServer and a 
> separate servlet container." Here is a discussion on Jetty in GWT: 
> https://groups.google.com/g/google-web-toolkit-contributors/c/iU9hckIab2o?pli=1
> .
>
> It means that one needs to run the application under Tomcat (a separate 
> servlet container) instead of the embedded Jetty.
>
> On Thursday, June 30, 2022 at 7:48:35 AM UTC-4 m.conr...@gmail.com wrote:
>
>> I didn't think that java.sql.DataSource is emulated by GWT. Looks like 
>> you are pulling in server side only type stuff from somewhere?
>>
>> On Thu, Jun 30, 2022 at 3:30 AM Thomas Broyer  wrote:
>>
>>> Didn't legacy devmode also only work with JDK 8?
>>>
>>> On Wednesday, June 29, 2022 at 10:46:30 PM UTC+2 Jens wrote:
>>>
 Without being able to see the project setup this is tough to answer.

 However regardless of the exception you are seeing: Classic/Legacy 
 DevMode will not work with GWT 2.9.0 correctly, because GWT 2.9.0 already 
 uses JsInterop internally in its Java SDK emulation (e.g. java.util.Date 
 uses it). JsInterop is not supported by classic/legacy DevMode. With GWT 
 2.9.0 you have to use SuperDevMode to have a functional Java SDK emulation 
 during development.

 -- J.

 abhiy...@gmail.com schrieb am Mittwoch, 29. Juni 2022 um 21:58:40 
 UTC+2:

> Hi Team,
>
> I am trying to start classic DEV mode in eclipse through GWT eclipse 
> plugin .
> I am using GWT 2.9.0 + Java 11 combination.
> I am getting below error. Can you help me in resolving the below error:
>
> [b]Caused by: java.lang.ClassNotFoundException: javax.sql.DataSource
> at 
> com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload$WebAppClassLoaderExtension.findClass(JettyLauncher.java:478)
>  
> ~[gwt-dev-2.9.0.jar:?]
> at 
> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:441)
>  
>
 -- 
>>> 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/6d3569b5-b7f0-4c2e-918c-c342b6803441n%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/8905067b-8bae-466f-8754-441beb2c4263n%40googlegroups.com.

Re: Upgrading from 2.8.1 to 2.9.0 yields "...type not found, or there are compile errors..."?!?

[Rob Newton]

It looks like the GWT compiler cannot find the source .java file for that 
class, which it will need.  Perhaps it is in a directory that is not 
covered by the  tag in your module.gwt.xml file?

On Tuesday, December 7, 2021 at 3:02:09 AM UTC+11 mmo wrote:

> We are trying to migrate a GWT application that is running fine with GWT 
> 2.8.1 to GWT 2.9.0.
> When we do a gwt:run the usual Jetty dialog comes up and without errors 
> nor exceptions and comes to the point where it offers to copy the URL or 
> launch the default browser.
>
> When we copy/paste the URL to the browser we get a ""Compiling SSt" 
> message and then the browser hangs ("SSt" is the name of the application).
>
> On the console we get the output:
> ...
> GET /recompile/sstweb
>Job ch.zh.ksta.sst.SstWebDevelopment_1_2
>   starting job: ch.zh.ksta.sst.SstWebDevelopment_1_2
>   binding: gxt.device=desktop
>   binding: gxt.user.agent=ie11
>   binding: user.agent=gecko1_8
>   binding: user.agent.os=windows
>   Compiling module ch.zh.ksta.sst.SstWebDevelopment
>  Ignored 20 units with compilation errors in first pass.
> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all 
> errors.
>  Computing all possible rebind results for 
> 'com.gwtplatform.mvp.client.ApplicationController'
> Rebinding com.gwtplatform.mvp.client.ApplicationController
>Invoking generator 
> com.gwtplatform.mvp.rebind.ApplicationControllerGenerator
>   [ERROR] The type 'ch.zh.ksta.sst.client.SstBootstrapper' 
> was not found, either the class name is wrong or there are compile errors 
> in your code.
>   [ERROR] The type 'ch.zh.ksta.sst.client.SstBootstrapper' 
> was not found, either the class name is wrong or there are compile errors 
> in your code.
>   [ERROR] There was a problem generating the 
> ApplicationController, this can be caused by bad GWT module configuration 
> or compile errors in your source code.
>  [WARN] For the following type(s), generated source was never 
> committed (did you forget to call commit()?)
> [WARN] com.gwtplatform.mvp.client.ApplicationControllerImpl
>  Unification traversed 29116 fields and methods and 2736 types. 
> 2699 are considered part of the current module and 2699 had all of their 
> fields and methods traversed.
>  Compiling 1 permutation
> Compiling permutation 0...
> Linking per-type JS with 2678 new/changed types.
> Source Maps Enabled
>  Compile of permutations succeeded
>  Compilation succeeded -- 6,609s
> ...
>
> We don't understand why the client boots trapper class is not found 
> (assuming the message is correct). It *is* contained in both, the classes 
> folder as well as in the generated .war file and the class' name is 
> correct. We also don't see any compile errors in the code (at least 
> IntelliJ doesn't display any...). 
> Any idea or hint, what might be wrong here? Or in which direction we could 
> search?
> Or any info that might be helpful here to pinpoint this issue?
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/833ddb4e-8423-4df2-98c8-ca6a255cba34n%40googlegroups.com.

looking for JsInterop information

[Rob Newton]

Hi,

I am looking for info on how to use JsInterop where arrays [], Lists and 
other collections are involved.

Besides this section of the GWTProject.org site:
  http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsJsInterop.html 


and this jsinterop-by-example page from google:
  https://github.com/google/j2cl/blob/master/docs/jsinterop-by-example.md

which don't mention arrays or other collections, are there other good 
sources of information around?

If I search this group there are postings where things like JsArray or the 
jsinterop-base utilities are mentioned, but I am hoping there is some 
definitive site with collection examples that I have missed?

Thanks,
Rob

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/b7427fd7-e9b1-48d8-9643-187a43bb9c47%40googlegroups.com.

Re: GWT goodies!

[Rob Newton]

Hristo,  Thanks for that.  I had not heard of Tabulator -- it could be 
useful.  Cheers!

On Friday, October 18, 2019 at 4:56:27 AM UTC+11, Hristo Stoyanov wrote:
>
> Hello all,
> I have been maintaining a few GWT projects, mostly JsInterop wrappers 
> around popular and useful JS libs that I think others can find useful. All 
> is Apache 2.0 licensed, at various state of maturity. Contributions welcome!
>
> https://github.com/peruncs/gwt
>
>
>
> GWT goodies
>
> This repository provides GWT/JSInterop/JACL wrappers for useful and 
> popular JS libraries and utility projects. All projects are Apache 2.0 
> licensed, contributions are welcome!
>
>
> JS-Cookie
>
> A wrapper for JS Cookie 
>  JS 
> library for easy handling of cookies. More ... 
> 
>
>
> Tabulator
>
> A wrapper for the Tabulator 
>  JS grid 
> component. More ... 
> 
>
> Stripe
>
> A Stripe API wrapper. More ... 
> 
>
> UIKIT
>
> A wrapper for the very nice UiKit  web site 
> framework. More ... 
> 
>
> reCaptcha
>
> A wrapper for Google reCaptcha. More ... 
> 
>
> JWT
>
> A JWT wrapper for various providers (Auth0 for now, Okta and Keycloak to 
> come ...) More ... 
> 
>
> Utils
>
> Utility code used in some of the other modules More ... 
> 
>
>  
>  
>  
>  
>  
>  
> 
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/b2d7e4ca-186f-49dd-8bc0-dbe81e4f1a20%40googlegroups.com.

Re: [ANN] (Unofficial) Elemental2 2.26 release

[Rob Newton]

OK I was wrong.  I thought I was using 2.26, but I am using other maven 
dependencies (elemento) which depend on 1.0.0-RC1, and that is having 
precedence over 2.26.

On Thursday, October 17, 2019 at 12:49:27 PM UTC+11, Rob Newton wrote:
>
> Hristo,
>
> I am using realityforge's elemental2 version 2.26 with GWT 2.8.2 and it is 
> fine.
>
> I understand what you would use jsinterop_base_version for (the 
> jsinterop-base artifact version), but what are you using jsinterop_version 
> for?  1.0.2-p1 looks too recent, and will require GWT 2.9 when it comes out.
>
> -Rob
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/0dbc7ee1-6442-4893-9fa1-39c34ce22fbb%40googlegroups.com.

Re: [ANN] (Unofficial) Elemental2 2.26 release

[Rob Newton]

Hristo,

I am using realityforge's elemental2 version 2.26 with GWT 2.8.2 and it is 
fine.

I understand what you would use jsinterop_base_version for (the 
jsinterop-base artifact version), but what are you using jsinterop_version 
for?  1.0.2-p1 looks too recent, and will require GWT 2.9 when it comes out.

-Rob

On Thursday, October 17, 2019 at 12:07:38 PM UTC+11, Hristo Stoyanov wrote:
>
> Peter,
> Getting this error with Elemental 2.26 and GWT 2.8.2:
>
> elemental2_version=2.26
> jsinterop_base_version=1.0.0-b2-e6d791f
> jsinterop_version=1.0.2-p1
>
> ...
>
> Compiling module com.recres.web.MainDev
>Tracing compile failure path for type 'elemental2.core.JsArray'
>   [ERROR] Errors in 
> 'jar:file:/C:/g/caches/modules-2/files-2.1/org.realityforge.com.google.elemental2/elemental2-core/2.26/1c407ef9a7e45ecc39be56283e9fe8d677060257/elemental2-core-2.26.jar!/elemental2/core/JsArray.java'
>  [ERROR] Line 3: The type javaemul.internal.ArrayStamper is not 
> visible
>  [ERROR] Line 258: ArrayStamper cannot be resolved
>[ERROR] Aborting compile due to errors in some input files
>
>
> Downgrading to 2.25 fixes the issue. Any clue?
>
> On Sunday, August 25, 2019 at 5:25:29 PM UTC-7, Peter Donald wrote:
>>
>> Elemental2 provides type-checked access to browser APIs for Java
>> code. This is done by using closure extern files and generating
>> JsTypes, which are part of the new JsInterop specification that
>> is implemented in both GWT and J2CL.
>>
>> https://github.com/google/elemental2
>>
>> This is an unofficial release to Maven Central under a different groupId.
>> Please don't bug the original authors. Versions are released on demand.
>>
>> API Changes relative to Elemental2 version 2.25
>>
>> elemental2-core:
>>   API Differences: 
>> https://jsinterop.github.io/api-diff/?key=elemental2-core=2.25=2.26
>>   - 1 non breaking changes.
>>   - 3 potentially breaking changes.
>>   - 1 breaking changes.
>> elemental2-dom:
>>   API Differences: 
>> https://jsinterop.github.io/api-diff/?key=elemental2-dom=2.25=2.26
>>   - 33 non breaking changes.
>>   - 65 potentially breaking changes.
>>   - 30 breaking changes.
>>
>> The complete set of Elemental2 API differences is available at
>>
>>   https://jsinterop.github.io/api-diff/?key=elemental2=2.25=2.26
>>
>> The Maven dependencies can be added to your pom.xml via
>>
>> 
>>   org.realityforge.com.google.elemental2
>>   ${artifact-id}
>>   2.26
>> 
>>
>> where artifact-id is one of
>>
>> * elemental2-core
>> * elemental2-dom
>> * elemental2-promise
>> * elemental2-indexeddb
>> * elemental2-svg
>> * elemental2-webgl
>> * elemental2-media
>> * elemental2-webstorage
>> * elemental2-webassembly
>>
>> Hope this helps,
>>
>> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2ab3805b-18a9-437f-90ed-935187f82514%40googlegroups.com.

Re: A Short GWT JsInterop Article for Beginners

[Rob Newton]

Nice!

On Tuesday, June 4, 2019 at 6:21:32 AM UTC+10, Dr. Lofi Dewanto wrote:
>
> Hi All,
>
> I wrote a short article to introduce GWT and JsInterop for beginners, hope 
> to see more people using GWT: http://bit.ly/WebJavaStory
>
> Enjoy, thanks,
> Lofi
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/3d76a880-3646-42d3-8a1e-dfc19ee7bee0%40googlegroups.com.

Re: Is this project active?

[Rob Newton]

I can sympathise with some of what Bob is saying.

>From what I can gather there is actually a great flux of activity going on 
behind the scenes by parts of the community.  The main players in moving 
GWT forward appear to be half-a-dozen or so companies who use GWT greatly, 
and some individuals, often doing it on their own personal time.

As Bob says, the gwtproject.org site makes it appear that GWT is in limbo.  
If a newcomer or existing user puts some time into searching posts in this 
group and the contributors one, or the occasional blog post somewhere, they 
start to see a rough roadmap, and some progress is being made towards it by 
the community.  But as he says, there needs to be some defacto site 
explaining the roadmap, and make some recommendations on what parts of 
traditional GWT 2 to keep using or not, and what new stuff is available 
(elemental2, jsinterop, etc), and some basics on how to use the new stuff.

It was only by searching the newsgroups that I learnt about the existance 
of jsinterop-base, and only through more searching that I saw a few 
examples of using it (and also looking at the API).  This is a pretty 
important/useful package.

Further research uncovers that much of the gwt-user package is being split 
out into individual packages, org.gwtproject.* , to not depend on JSNI and 
generators.  Quite a few are done, according to 
https://docs.google.com/spreadsheets/d/1b1D9fEqRh5lZ8cqMJtYoc_25rfTRvsuJkTtS2vjgi3o
 
.  They are scattered all around github it seems, not ready for maven 
central?

A contributor may develop something new or port something, and then 
announce it to the community that it is available for use, but there is no 
central site listing/promoting these wares.

Perhaps things are in too much flux to attract new developers to using 
GWT.  Perhaps the goal should be to retain existing GWT users?  The more 
users there are, the more contributors there will be, and the better GWT 
will be for all of us.  Conversely, the fewer users there are, ... .

(It's easy for me (a non-contributor) to list some shortcomings, but am I 
going to volunteer my personal time to improve things?  Or do I expect 
Google to do everything, and I just use it and give nothing back?)


On Friday, May 31, 2019 at 5:31:38 AM UTC+10, Bob Lacatena wrote:
>
> GWT is suffering from a very serious publicity debacle.  I'm actively 
> doing GWT development, and regretting every moment of it right now.  Years 
> ago I loved GWT.  Today, I'm dreading it.
>
> My biggest problem for the past year has been the fact that unless one 
> hunts for threads like this, GWT does appear to be dead.  I don't know what 
> the developers are doing.  I just know there were occasional hints that 
> something was coming (a year ago), with not a sound since then.
>
> Update gwtproject.org!  Put a few news items on it a month, at least.  
> Let people know you are working.  No matter how good your work is, more and 
> more developers like me are going to abandon it as time drags on.
>
> Or create a GWT 3.0 blog.  Something.  Anything other than the black hole 
> of silence you have now.
>
> I'm also very concerned that with the rewrite, every bit of code I'm 
> working on now will be useless.  GWT before 3.0, from a developer who uses 
> it, was and still is a nightmare if you don't want to use every widget, as 
> it exists, out of the box, because too many of the classes use private 
> members and methods, making them completely impossible to extend (which, I 
> believe, is sort of the point of a lot of OOP concepts).
>
> With GWT getting old, this is becoming painful, because GWT did cool 
> things, like animation and date pickers and rich text editors, by brute 
> force back when that was necessary.  Now, however, HTML5 and other things 
> have evolved to offer better, cleaner solutions, but often it's difficult 
> to impossible to make GWT work with those solutions, because of the private 
> members.
>
> I've even gotten into vicious cycles; copy the source for class X, to be 
> able to fix it, but that requites a copy of private class Y, which requires 
> a copy of private class Z, and on and on until I give up.
>
> Instead, I have to "roll my own", which takes too much effort that could 
> be spend on more productive pursuits.  I'd rather use a framework with 
> working widgets.
>
> I didn't start out intending this to be a rant, but the bottom line is 
> that I like GWT, I like being able to work exclusively in one 
> language/framework instead of four at one time (Java + Angular + TypeScript 
> + JQuery), but as a professional who is paid to make decisions that will 
> have a decade-long impact on my company, I am very hard-pressed not to 
> advise my company to immediately abandon all efforts using GWT.
>
> *Put some effort into communication! * [Which should be tattooed on the 
> backs of every software engineer's hands, because as a species they seem to 
> be oblivious to the concept.]
>
> I am somewhat 

Re: DisclosurePanel

[Rob Newton]

When you create the DisclosurePanel you can provide the text for the header:

DisclosurePanel(java.lang.String headerText)




On Wednesday, May 22, 2019 at 3:59:16 PM UTC+10, naaser ahmed wrote:
>
> Hello, 
>
> I am trying to make my website compatible with Accessibility and running 
> into "Links must have discernible text" error. On inspecting, the error is 
> being generated by Links being generated by Disclosure Panel. The link 
> being created is this -- "". Can someone please let me know how I can add 
> title to the link. 
>
> I appreciate all the help. 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/e921ddc3-d6d8-4e6c-af19-497f62981984%40googlegroups.com.

Re: UnableToCompleteException

[Rob Newton]

I wonder if the GWT unit cache is corrupted?  Try removing directories 
named gwt-unitCache and/or /tmp/gwt-cache-* (linux).

On Tuesday, April 2, 2019 at 6:32:10 AM UTC+11, Andrew Buck wrote:
>
> I am getting an exception when trying to use super dev mode that I don't 
> understand. Stack trace is below.
>
>
> Compiling 1 permutation
> Compiling permutation 0...
> [ERROR] Unexpected internal compiler error
> java.lang.NullPointerException
> at com.google.gwt.dev.jjs.ast.HasName$1.compare(HasName.java:33)
> at com.google.gwt.dev.jjs.ast.HasName$1.compare(HasName.java:30)
>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: issue with gwt RPC

[Rob Newton]

Fred,
It's not a problem during compile time.  It's a runtime issue.  You need to 
configure Tomcat to start with more memory.

For example, in my installation, there is a file /opt/tomcat/bin/setenv.sh, 
with the following line:
CATALINA_OPTS=" -server -Xms128M -Xmx512M"

On Wednesday, January 25, 2012 at 1:13:15 AM UTC+11, fceransky wrote:
>
> But I compile my webapps under netbeans with Xmx512m. It's not enough? 
>
> On 24 jan, 11:56, Daniel Kurka  wrote: 
> > Your server is running out of memory. Give your sever some more RAM at 
> startup. 
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Elemento, maven config to force template implementation class regen

[Rob Newton]

Thankyou Thomas, that is good to know.

On Tuesday, March 27, 2018 at 8:36:22 PM UTC+11, Thomas Broyer wrote:
>
>
>
> On Monday, March 26, 2018 at 10:19:26 AM UTC+2, Rob Newton wrote:
>>
>> Hi,
>>
>> When I edit an Elemento template HTML file and do a mvn compile it won't 
>> regenerate the template implementation class source file.   Is there some 
>> maven pom config and/or command I can use to say rerun the elemento 
>> annotation processor without doing a mvn clean or touching the template 
>> abstract class source file ?
>>
>
> I don't use Elemento, but AFAIU the problem lies in how annotation 
> processors work and how Elemento uses them, and how the 
> maven-compiler-plugin works (it would be the same with other build tools 
> though).
> Build tools don't expect that the result of compilation changes based on a 
> resource file (because resources are meant to be bundled with the compiled 
> classes, with side-effects at runtime rather than compile-time), and 
> annotation processors can indicate which Java element triggered the 
> generation of some file, and only Java elements, not resources. 
> Consequently, the maven-compiler-plugin (rightfully) thinks it has nothing 
> to do if Java source files haven't changed.
>
> Annotation processors are *not* a good fit for this kind of work; 
> non-Java templates should be processed by generators to generate Java 
> source that will then be fed to the Java compiler (and possibly trigger 
> annotation processing).
>
> In the mean time, you'll have to "touch" the class responsible for the 
> processing of the template to trigger a recompile.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Elemento, maven config to force template implementation class regen

[Rob Newton]

Trying mvn process-sources or mvn generate-sources does not help.  

On Monday, March 26, 2018 at 8:25:18 PM UTC+11, Ahmad Bawaneh wrote:
>
> try *mvn process-sources*
>
> On Monday, March 26, 2018 at 10:19:26 AM UTC+2, Rob Newton wrote:
>>
>> Hi,
>>
>> When I edit an Elemento template HTML file and do a mvn compile it won't 
>> regenerate the template implementation class source file.   Is there some 
>> maven pom config and/or command I can use to say rerun the elemento 
>> annotation processor without doing a mvn clean or touching the template 
>> abstract class source file ?
>>
>> Thanks,
>> Rob
>>
>>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Elemento, maven config to force template implementation class regen

[Rob Newton]

Hi,

When I edit an Elemento template HTML file and do a mvn compile it won't 
regenerate the template implementation class source file.   Is there some 
maven pom config and/or command I can use to say rerun the elemento 
annotation processor without doing a mvn clean or touching the template 
abstract class source file ?

Thanks,
Rob

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: CellList refreshed only after mouse move

[Rob Newton]

I have encountered this problem myself.  When the new data arrives, rather 
than updating the CellList/Grid immediately, defer the update until the 
current event loop has completed.  For example:

private static void setRowDataDeferred(
final DataGrid grid, final int start, final List<
Consign> values)
{
Scheduler.get().scheduleDeferred(new ScheduledCommand() {
@Override
public void execute() {
grid.setRowCount(values.size(), true);
grid.setRowData(start, values);
}
});
}




-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Production build takes 25% longer on 2.8 compared to 2.7

[Rob Newton]

I have been having a similar experience.  GWT 2.8 production builds take 
roughly 25% longer compared to 2.7.

On Wednesday, March 15, 2017 at 12:02:12 AM UTC+11, shimmeri...@gmail.com 
wrote:
>
> Hi,
>
> I am migrating our GWT projects from 2.7 to 2.8 and noticed that on 
> average production builds now take 25% longer, is this expected ?
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: module.nocache.js generated with same timestamp as module.gwt.xml

[Rob Newton]

I have just noticed this same issue, and am glad to have found Dop Sun's 
post here.

Thanks Thomas for the link to the proposed path.  I notice on Jan 6 the 
patch was merged, but then reverted later that day, because *need to 
update some tests before committing this change*.

I hope this hasn't been forgotten and it will make the next release of GWT?

Thanks,
Rob

On Wednesday, December 31, 2014 at 5:47:19 PM UTC+11, Dop Sun wrote:

 Thanks Thomas.

 On Wednesday, December 31, 2014 2:33:59 AM UTC+8, Thomas Broyer wrote:

 This is actually a known issue with a proposed patch: 
 https://gwt-review.googlesource.com/10520

 On Tuesday, December 30, 2014 5:04:05 PM UTC+1, Dop Sun wrote:

 Hi,

 In previous versions, e.g. 2.6.1, module.nocache.js file generated 
 with timestamp when the files generated. But in version 2.7.0, the 
 module.nocache.js file generated with the same timestamp of 
 module.gwt.xml.

 Is this by design? 

 I'm raising this question because it causes Safari ignores latest 
 compiled module.nocache.js (which is same timestamp as module.gwt.xml), 
 and using previously cached file, which is compiled by 2.6.1, and causing 
 application not working in Safari.

 And yes, suggestions of this page 
 http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#DevGuideCompilerOptions,
  
 section [Perfect Cache] can help. Change .htaccess file with suggested 
 expiry settings.

 I'm using Mac OS X Yosemite.

 Thanks,
 Regards,
 Dop



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.