Re: GWT Java Interview at JCON 2024 Cologne

2024-05-28 Thread Craig Mitchell
Nice one.  I can't believe you agreed with the presentor that you missed 
writing Swing apps.  Nobody misses Swing.  

On Saturday 25 May 2024 at 8:23:14 pm UTC+10 lofid...@gmail.com wrote:

> At JCON 2024 in Cologne, I had the opportunity to talk about GWT and Java. 
>
> I was interviewed by Brian Demers, a Java Champion. Pardon me as we forgot 
> to unmute the first minute  - Enjoy
>
> https://bit.ly/jcongwt
>

-- 
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/a7820fa7-460d-4990-b5f3-917503b70bf8n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-05-23 Thread Craig Mitchell
When Thomas said:

> *Out of curiosity, any specific reason you don't automate a "mvn clean 
verify" to validate the generated project?*

I suspect he was talking about a Git pre-push hook that automatically did a 
mvn verify: https://git-scm.com/docs/githooks#_pre_push  Unless I 
misunderstood.

On Friday 24 May 2024 at 2:32:12 am UTC+10 Frank Hossfeld wrote:

> Thanks for contributing, Craig, LGTM, so already merged. :-)
>
> Craig Mitchell schrieb am Mittwoch, 22. Mai 2024 um 03:48:18 UTC+2:
>
>> Thanks Frank.  I was misunderstanding and didn't know about 
>> the basic-webapp in the target.
>>
>> I revamped the readme.md:  
>> https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/17
>>
>> Hopefully made it better not worse.  
>>
>> On Wednesday 22 May 2024 at 2:07:30 am UTC+10 Thomas Broyer wrote:
>>
>>> On Tuesday, May 21, 2024 at 6:02:31 PM UTC+2 frank.h...@googlemail.com 
>>> wrote:
>>>
>>> Ok, got it, was thinking, we were talking about the generated project 
>>> ... Yep correct, usually, running the verify goal, will compare the 
>>> generated sources with the ones stored under test resources. There is no 
>>> test were the generated project gets started/tested, if it works.
>>>
>>>
>>> Out of curiosity, any specific reason you don't automate a "mvn clean 
>>> verify" to validate the generated project?
>>> (of course testing that devmode works, or that the built artifact 
>>> actually works is trickier and probably not worth it, but a simple build 
>>> would still be better than nothing IMO)
>>>
>>

-- 
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/88c30284-56b4-4885-b4cf-ff796e1348e7n%40googlegroups.com.


Re: JSInterop and "JSON.stringify" method return "Converting circular structure to JSON"

2024-05-22 Thread Craig Mitchell
Would it not be easier to just create your JSON object manually with the 
classes in com.google.gwt.json.client?  Ie: JSONObject, JSONArray, ...

On Thursday 23 May 2024 at 1:42:29 am UTC+10 Thomas Broyer wrote:

> On Wednesday, May 22, 2024 at 12:43:56 PM UTC+2 tenti...@gmail.com wrote:
>
> I misunderstood the documentation... ty for the clarification Thomas can 
> you give me some confirmations.
>
> The Date issue, When you say to use the JsDate do you mean the one in the 
> elemental2 package (elemental2.core.JsDate) or in the gwt core (
> com.google.gwt.core.client.JsDate) ?
>
> Any one of them, anything that directly maps to a native JS Date object.
>  
>
> So for the Date issue i just enough to replace this code :
>
> @JsProperty *public* *native* *Date* getDataRepertorioDocumento();
>
>  
>
> @JsProperty *public* *native* *void* setDataRepertorioDocumento(*Date* 
> dataRepertorioDocumento);
>
>  
>
> With:
>
> @JsProperty *public* *native* Js*Date* getDataRepertorioDocumento();
>
>  
>
> @JsProperty *public* *native* *void* setDataRepertorioDocumento(*JsDate* 
> dataRepertorioDocumento);
>
>  
>
> Right ?
>
> Yes.
> (note that it works for serializing because a JS Date object has a 
> toJSON() method that returns its toISOString(), but it won't work for 
> parsing JSON, for that you will have to pass a *reviver* function to 
> JSON.parse() that will have to be aware of your object structure to know 
> that the dataRepertorioDocumento property value needs to be parsed to a 
> Date object, or use a @JsOverlay getter/setter pair that will 
> serialize/parse the java.util.Date or JsDate value to/from the JSON 
> representation you want, same as List and Map)
>
> I also missed an instance of Integer in your objects, this will have to be 
> changed to Double.
>  
>
> For the "List" and "Map" problem, i will probably try to use some 
> @JsOverlay instead to use a second argument  on the JSON.stringify by the 
> way can you point me out some example (i'm not very skilled with this 
> library) ?
>
>
> Could be as simple as (note that a copy is made each time the getter or 
> setter is called):
> ReferenzaDTOGWT[] nodeIdAllegatti;
> // This could also use Elemental's JsArrayLike.asList()
> @JsOverlay public List getNodeIdAllegatti() { return 
> List.of(this.nodeIdAllegatti); }
> @JsOverlay public void setNodeIdAllegatti(List 
> nodeIdAllegatti) { this.nodeIdAllegatti = nodeIdAllegatti.toArray(new 
> ReferenzaDTOGWT[nodeAllegatti.size()]); }
>
> JsPropertyMap errors;
> @JsOverlay public Map getErrors() {
>   var ret = new HashMap();
>   errors.forEach(key -> ret.put(ret, errors.get(key)));
>   return ret;
> }
> @JsOverlay public setErrors(Map errors) {
>   var obj = JsPropertyMap.of();
>   errors.forEach((key, value) -> obj.set(key, value));
>   this.errors = obj;
> }
>
> Of course for the Map> mappaAltriMetadati 
> you'd have to also transform each List.
>
> The JSON.stringify replacer could look like:
> JSONType.StringifyReplacerFn replacer = (key, value) -> {
>   if (value instanceof List) {
> return ((List) value).toArray();
>   }
>   if (value instanceof Map) {
> var obj = JsPropertyMap.of();
> ((Map) value).forEach((k, v) -> obj.set(k, v));
> return obj;
>   }
>   if (value instanceof Date) {
> return ((Date) value).getTime(); // pass that to JsDate.create() if 
> you prefer an ISO-formatted String rather than the timestamp
>   }
>   if (value instanceof Integer) {
> return ((Integer) value).doubleValue();
>   }
>   return value;
> };
>  
> This is all totally untested (also note that I haven't actually written 
> GWT code for years, this is all based on memory and the javadocs)
>
> Also I found this project updated for GWT 2.9.0 and java 11  
> https://github.com/jp-solutions/gwt-interop-utils . it’s seem goof enough 
> for my use case,  i’ll try out and let you know it.
>
> Not sure what it actually brings on top of plain old JsInterop Base or 
> Elemental Core…
>

-- 
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/c88b2e0c-0883-4ff1-b9a0-1d52d9040158n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-05-21 Thread Craig Mitchell
Thanks Frank.  I was misunderstanding and didn't know about 
the basic-webapp in the target.

I revamped the readme.md:  
https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/17

Hopefully made it better not worse.  

On Wednesday 22 May 2024 at 2:07:30 am UTC+10 Thomas Broyer wrote:

> On Tuesday, May 21, 2024 at 6:02:31 PM UTC+2 frank.h...@googlemail.com 
> wrote:
>
> Ok, got it, was thinking, we were talking about the generated project ... 
> Yep correct, usually, running the verify goal, will compare the generated 
> sources with the ones stored under test resources. There is no test were 
> the generated project gets started/tested, if it works.
>
>
> Out of curiosity, any specific reason you don't automate a "mvn clean 
> verify" to validate the generated project?
> (of course testing that devmode works, or that the built artifact actually 
> works is trickier and probably not worth it, but a simple build would still 
> be better than nothing IMO)
>

-- 
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/42002fd9-40db-4c1d-ac76-81531e1f0bffn%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-05-21 Thread Craig Mitchell
Sorry, I think I wasn't clear.  Yes, I can make changes to the 
gwt-maven-springboot-archetype project, and do a mvn compile on it to make 
sure there are no syntax errors with my changes.

The problem is, if I want to test to make sure my modified version of 
gwt-maven-springboot-archetype actually generates a new project correctly 
(Ie: Run mvn archetype:generate ...), this doesn't work unless I do a mvn 
install. as maven doesn't see the HEAD-SNAPSHOT version, as (I'm guessing a 
bit here, I'm not a maven expert), I think maven only looks in its 
repositories (local and remote), and there isn't any HEAD-SNAPSHOT version, 
as it's not installed.  Thus, I get the "The desired archetype does not 
exist (com:modular-springboot-webapp:HEAD-SNAPSHOT)" error.

fyi:  At no point are there any GWT compilations.  That comes later when I 
compile the project that was generated.

On Monday 20 May 2024 at 11:07:45 pm UTC+10 Frank Hossfeld wrote:

> Thanks for you PR. Your PR is merged and a new release is done. New 
> version should be available soon. 
>
> doing a `mvn clean compile` is usually enough to generate all necessary 
> sources and run the project. It's much faster cause it avoids a GWT compile 
> during build. In case you need a war, run `mvn clean verify`- not sure, if 
> install is really needed. So, for develpment, `mvn clean compile`  Is all 
> you need to do. And it save a lot of time especially when the project gets 
> more classes.
>
>
> Craig Mitchell schrieb am Montag, 20. Mai 2024 um 05:00:07 UTC+2:
>
>> Just tried a mvn install, and it seems to have worked.
>>
>> So I think the instructions 
>> https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation
>>  
>> :
>> cd gwt-maven-springboot-archetype && mvn clean compile
>>
>> should be:
>> cd gwt-maven-springboot-archetype && mvn clean install
>>
>> And my PR looks good.  
>>
>> On Monday 20 May 2024 at 12:40:45 pm UTC+10 Craig Mitchell wrote:
>>
>>> Hi Frank.  Unfortunately, that didn't work.  I raised an issue:  
>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/15
>>>
>>> I've also submitted a fix:  
>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/16
>>>
>>> However, I couldn't test my fix with the generation.  The instructions 
>>> here:  
>>> https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation
>>>  
>>> say to test, you do:
>>>
>>> cd gwt-maven-springboot-archetype && mvn clean compile
>>>
>>> And then I should be able to do:
>>>
>>> mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype 
>>> -DarchetypeVersion=HEAD-SNAPSHOT 
>>> -DarchetypeArtifactId=modular-springboot-webapp
>>>
>>> But that fails with:
>>>
>>> *The desired archetype does not exist 
>>> (com:modular-springboot-webapp:HEAD-SNAPSHOT)*
>>>
>>> I suspect I'm supposed to do a mvn install?  Or mvn deploy?  Something 
>>> that makes HEAD-SNAPSHOT available?
>>>
>>> On Sunday 19 May 2024 at 2:17:17 am UTC+10 Frank Hossfeld wrote:
>>>
>>>> I'll added some additional code to avoid adding the launcherDir as 
>>>> document root in production mode. 
>>>> New version should be soon available.
>>>>
>>>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2:
>>>>
>>>>> The issue seems to be the launcherDir directory doesn't exist.  I've 
>>>>> raised a an issue with the full stack trace:  
>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13
>>>>>
>>>>> On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote:
>>>>>
>>>>>> please can you post the error message: Thanks
>>>>>>
>>>>>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2:
>>>>>>
>>>>>>> I spoke to soon.  Adding the EmbeddedServletContainerConfig fixes 
>>>>>>> the serialization policy when running locally, but if you do a build 
>>>>>>> and 
>>>>>>> try to run.  Ie:  mvn clean package and then java -jar 
>>>>>>> myserver/myapp.war, 
>>>>>>> it crashes.
>>>>>>>
>>>>>>> I'll investigate.  Any ideas/help most welcome.
>>>>>>>
>>>>>>> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote:
>>>>>>>
>>>>>>>> > *New version available ... This one fixes the 
>>>>>>>> serializationPolicyFilePath issue ... *
>>>>>>>>
>>>>>>>> Awesome, thanks!  I've closed 
>>>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7  
>>>>>>>> 
>>>>>>>>
>>>>>>>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote:
>>>>>>>>
>>>>>>>>> Bott -> Boot ...  (spelling correction  arrrgh)
>>>>>>>>>
>>>>>>>>>

-- 
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/2b94c080-fe7f-4120-a1e7-4dd2a7286c5dn%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-05-19 Thread Craig Mitchell
Just tried a mvn install, and it seems to have worked.

So I think the 
instructions 
https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation
 
:
cd gwt-maven-springboot-archetype && mvn clean compile

should be:
cd gwt-maven-springboot-archetype && mvn clean install

And my PR looks good.  

On Monday 20 May 2024 at 12:40:45 pm UTC+10 Craig Mitchell wrote:

> Hi Frank.  Unfortunately, that didn't work.  I raised an issue:  
> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/15
>
> I've also submitted a fix:  
> https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/16
>
> However, I couldn't test my fix with the generation.  The instructions 
> here:  
> https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation
>  
> say to test, you do:
>
> cd gwt-maven-springboot-archetype && mvn clean compile
>
> And then I should be able to do:
>
> mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype 
> -DarchetypeVersion=HEAD-SNAPSHOT 
> -DarchetypeArtifactId=modular-springboot-webapp
>
> But that fails with:
>
> *The desired archetype does not exist 
> (com:modular-springboot-webapp:HEAD-SNAPSHOT)*
>
> I suspect I'm supposed to do a mvn install?  Or mvn deploy?  Something 
> that makes HEAD-SNAPSHOT available?
>
> On Sunday 19 May 2024 at 2:17:17 am UTC+10 Frank Hossfeld wrote:
>
>> I'll added some additional code to avoid adding the launcherDir as 
>> document root in production mode. 
>> New version should be soon available.
>>
>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2:
>>
>>> The issue seems to be the launcherDir directory doesn't exist.  I've 
>>> raised a an issue with the full stack trace:  
>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13
>>>
>>> On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote:
>>>
>>>> please can you post the error message: Thanks
>>>>
>>>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2:
>>>>
>>>>> I spoke to soon.  Adding the EmbeddedServletContainerConfig fixes the 
>>>>> serialization policy when running locally, but if you do a build and try 
>>>>> to 
>>>>> run.  Ie:  mvn clean package and then java -jar myserver/myapp.war, it 
>>>>> crashes.
>>>>>
>>>>> I'll investigate.  Any ideas/help most welcome.
>>>>>
>>>>> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote:
>>>>>
>>>>>> > *New version available ... This one fixes the 
>>>>>> serializationPolicyFilePath issue ... *
>>>>>>
>>>>>> Awesome, thanks!  I've closed 
>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7  
>>>>>> 
>>>>>>
>>>>>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote:
>>>>>>
>>>>>>> Bott -> Boot ...  (spelling correction  arrrgh)
>>>>>>>
>>>>>>>

-- 
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/a1aff7cf-f86e-449c-a687-2bae830f828fn%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-05-19 Thread Craig Mitchell
Hi Frank.  Unfortunately, that didn't work.  I raised an 
issue:  https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/15

I've also submitted a 
fix:  https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/16

However, I couldn't test my fix with the generation.  The instructions 
here:  
https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation
 
say to test, you do:

cd gwt-maven-springboot-archetype && mvn clean compile

And then I should be able to do:

mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype 
-DarchetypeVersion=HEAD-SNAPSHOT 
-DarchetypeArtifactId=modular-springboot-webapp

But that fails with:

*The desired archetype does not exist 
(com:modular-springboot-webapp:HEAD-SNAPSHOT)*

I suspect I'm supposed to do a mvn install?  Or mvn deploy?  Something that 
makes HEAD-SNAPSHOT available?

On Sunday 19 May 2024 at 2:17:17 am UTC+10 Frank Hossfeld wrote:

> I'll added some additional code to avoid adding the launcherDir as 
> document root in production mode. 
> New version should be soon available.
>
> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2:
>
>> The issue seems to be the launcherDir directory doesn't exist.  I've 
>> raised a an issue with the full stack trace:  
>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13
>>
>> On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote:
>>
>>> please can you post the error message: Thanks
>>>
>>> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2:
>>>
>>>> I spoke to soon.  Adding the EmbeddedServletContainerConfig fixes the 
>>>> serialization policy when running locally, but if you do a build and try 
>>>> to 
>>>> run.  Ie:  mvn clean package and then java -jar myserver/myapp.war, it 
>>>> crashes.
>>>>
>>>> I'll investigate.  Any ideas/help most welcome.
>>>>
>>>> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote:
>>>>
>>>>> > *New version available ... This one fixes the 
>>>>> serializationPolicyFilePath issue ... *
>>>>>
>>>>> Awesome, thanks!  I've closed 
>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7  
>>>>>
>>>>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote:
>>>>>
>>>>>> Bott -> Boot ...  (spelling correction  arrrgh)
>>>>>>
>>>>>>

-- 
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/a05f1900-ba3e-447b-a056-c9fca4ccc5bbn%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-05-18 Thread Craig Mitchell
The issue seems to be the launcherDir directory doesn't exist.  I've raised 
a an issue with the full stack 
trace:  https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13

On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote:

> please can you post the error message: Thanks
>
> Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2:
>
>> I spoke to soon.  Adding the EmbeddedServletContainerConfig fixes the 
>> serialization policy when running locally, but if you do a build and try to 
>> run.  Ie:  mvn clean package and then java -jar myserver/myapp.war, it 
>> crashes.
>>
>> I'll investigate.  Any ideas/help most welcome.
>>
>> On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote:
>>
>>> > *New version available ... This one fixes the 
>>> serializationPolicyFilePath issue ... *
>>>
>>> Awesome, thanks!  I've closed 
>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7  
>>>
>>> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote:
>>>
>>>> Bott -> Boot ...  (spelling correction  arrrgh)
>>>>
>>>>

-- 
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/caa4a474-3612-429c-a147-3bec9c788261n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-05-18 Thread Craig Mitchell
I spoke to soon.  Adding the EmbeddedServletContainerConfig fixes the 
serialization policy when running locally, but if you do a build and try to 
run.  Ie:  mvn clean package and then java -jar myserver/myapp.war, it 
crashes.

I'll investigate.  Any ideas/help most welcome.

On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote:

> > *New version available ... This one fixes the 
> serializationPolicyFilePath issue ... *
>
> Awesome, thanks!  I've closed 
> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7  
>
> On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote:
>
>> Bott -> Boot ...  (spelling correction  arrrgh)
>>
>>

-- 
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/e8ecb6f8-fcdc-42f1-a94f-bdd42e50c9c0n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-05-18 Thread Craig Mitchell
> *New version available ... This one fixes the serializationPolicyFilePath 
issue ... *

Awesome, thanks!  I've closed 
https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7  

On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote:

> Bott -> Boot ...  (spelling correction  arrrgh)
>
>

-- 
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/59963153-ef79-41aa-bde8-6bfece30b30fn%40googlegroups.com.


Re: Unable to Access GWT CodeServer Outside of WSL Environment

2024-05-08 Thread Craig Mitchell
I haven't used that old plugin for awhile, but I think you need to set the  
bindAddress to 
0.0.0.0:  
https://gwt-maven-plugin.github.io/gwt-maven-plugin/eclipse-mojo.html#bindAddress

You might like to do a test with generating a sample app 
with https://github.com/tbroyer/gwt-maven-archetypes which will use 
https://github.com/tbroyer/gwt-maven-plugin instead, and see if that 
works.  More instructions 
here:  https://www.gwtproject.org/gettingstarted-v2.html

On Thursday 9 May 2024 at 1:36:30 am UTC+10 Anders Kobberup wrote:

> I am encountering an issue with accessing the GWT CodeServer from outside 
> the Windows Subsystem for Linux (WSL) environment. I'm hoping to get some 
> guidance or assistance on resolving this issue.
>
> The problem arises when attempting to access the GWT CodeServer running 
> within the WSL environment from a browser outside of WSL. 
> Specifically, I can access the GWT application's main page from my browser 
> by navigating to localhost:8001, but I cannot connect to the CodeServer 
> at http://localhost:8501.
>
> From within the WSL terminal i can telnet the port and it looks good, but 
> i cannot from the outside host.
>
> My theory is that the codeserver only accepts connections from localhost - 
> but i do not know how to set a host="0.0.0.0" or something like that on the 
> jetty running the codeserver.
>
> We use the org.codehaus.mojo gwt-maven-plugin with these settings:
> 
> org.codehaus.mojo
> gwt-maven-plugin
> 2.10.0
> 
> 1
> true
> true
> true
> false
> INFO
> OBF
> auto
> -Xmx7G --add-opens 
> java.base/java.lang=ALL-UNNAMED
> 
> com.toh.manager.ManagerclientDev
> true
> 8001
> 8010
> 8501
> managerclient.html
> ${project.basedir}/src/main/webapp
> true
> 
> /tmp/gwt-${project.build.finalName}
> 
> 
>
> Please let me know if you need anymore information
>
>

-- 
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/d4bfca14-1d70-4b0e-b09e-964fa8568caan%40googlegroups.com.


Re: Seeking Advice on Legacy Application Migration Strategy

2024-04-25 Thread Craig Mitchell
It'd be hard to answer that question, as we don't have all the details.  As 
this is a GWT forum, I'd say, migrate GWT to the latest version first.  But 
that might actually be bad advice, just depends on your project.

My gut feel is you'd be best to decouple the front end and back end first.

On Friday 26 April 2024 at 2:32:17 am UTC+10 Wejden Mrabti wrote:

> Hello GWT Users Community,
>
> I'm currently working on a large legacy application stack, using Java 8, 
> Hibernate version 5.3.20.Final, and Hibernate Search 5.11.5.Final. Our 
> frontend technology stack includes GWT version 2.8.2 and GXT version 
> 2.3.1a-gwt22. Fontend and backend arent well de-coupled.
>
> In my initial approach to modernize the application, I began by migrating 
> Hibernate to version 6.2, assuming it would be the easiest step. However, I 
> encountered an issue where Hibernate 6.2 requires transitioning to Jakarta 
> Persistence. When attempting to compile parts of my codebase, I received 
> the following error:
>
> java.lang.UnsupportedClassVersionError: jakarta/persistence/Transient has 
> been compiled by a more recent version of the Java Runtime (class file 
> version 55.0), this version of the Java Runtime only recognizes class file 
> versions up to 52.0
>
> This suggests that I need to execute my code with JDK 11. However, when 
> attempting to do so, I encountered the following issue:
>
> [ERROR] Found resouce but unrecognized URL format: 
> 'jrt:/java.sql/javax/sql/DataSource.class' java.lang.NoClassDefFoundError: 
> javax/sql/DataSource
>
> After reviewing your discussions in the GWT contributors group, I'm 
> questioning whether starting with the Hibernate migration is the right 
> approach. Should I instead prioritize migrating Java or perhaps GWT? I 
> would greatly appreciate your insights and advice based on your experiences.
>
> Thank you,
>
> WM
>

-- 
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/e72ddd8b-24f3-41dd-b4fa-52d2f860f07cn%40googlegroups.com.


Re: How to unescape a JSONString?

2024-04-10 Thread Craig Mitchell
Sorry, figured it out.  I needed a namespace:

@JsType(isNative = true, namespace = JsPackage.GLOBAL)
public class RTCPeerConnection {
  public RTCPeerConnection(JavaScriptObject iceServersJsoArray) {
super();
  }
  public native void close();
}

Now working great!  

On Wednesday 10 April 2024 at 7:27:42 pm UTC+10 Craig Mitchell wrote:

> You weren't kidding.  I checked the compiled JS, and there it is (with 
> some smarts to minimise the JS it looks like):
> this.a = new U2b(d,c,(n = {
> iceServers: m
> },
> new RTCPeerConnection(n)));
>
> Thanks for letting me know about JsonUtils.safeEval(...)  That is a better 
> option.
>
> I never had much luck with JsInterop.  I just tried it again, trying to 
> map the RTCPeerConnection 
> <https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/RTCPeerConnection>,
>  
> but it doesn't work giving me "TypeError: Cannot read properties of 
> undefined" when I try to instanciate it.  I also can't debug it, as I can't 
> step into the constructor to see what's going wrong.
>
> This was my failed attempt:
>
> @JsType(isNative = true)
> public class RTCPeerConnection {
>   @JsConstructor
>   public RTCPeerConnection(JavaScriptObject iceServersJsoArray) {
> super();
>   }
>   public native void close();
> }
>
>
> On Sunday 7 April 2024 at 4:20:48 am UTC+10 Thomas Broyer wrote:
>
>> There's no escaping. You have a string value, it stays a string value. If 
>> its content is JSON representing an array and you want that array, then 
>> indeed you have to parse the JSON.
>>
>> It looks like there's a major misunderstanding about what GWT does with 
>> your code, and/or possibly where/when the code runs or something.
>> GWT "only" translates the Java syntax to JS (and also optimizes 
>> everything), and therefore comes with a library of classes that emulates 
>> the Java runtime core classes so they can also be translated the same way 
>> as your code. JSNI is an escape hatch to be able to "put JS syntax inside 
>> your Java syntax", but that's all.
>> In other words, if you have a string "[ 42, true, null ]" in a variable 
>> (that you retrieved from your server), if you call that method, it's 
>> exactly equivalent to this JS:
>> var iceServersJson = "[ 42, true, null ]";
>> var peerConnectionConfig = {
>>   iceServers: iceServersJson
>> };
>> i.e. the peerConnectionConfig object has an iceServers property whose 
>> value is just the iceServersJson string value.
>> GWT won't "magically" generate JS code at runtime replacing the value 
>> as-is to form some new JS each time, i.e. it *won't* become:
>> var peerConnectionConfig = {
>>   iceServers: [ 42, true, null ]
>> };
>> No, really, that Java/JSNI function is transformed to this JS function:
>> function createPeerConnection(iceServersJson) {
>>   var peerConnectionConfig = {
>> iceServers: iceServersJson
>>   };
>>   return new RTCPeerConnection(peerConnectionConfig);
>> }
>> and then at one point you call it. It's your job to give it either a 
>> string value or parse the string value as JSON and passe the result.
>>
>> Kudos to resurrecting a 15 years old post though! 藍
>>
>> BTW, you may want to prefer JsonUtils.safeEval(iceServersJson) here: 
>> https://www.gwtproject.org/javadoc/latest/com/google/gwt/core/client/JsonUtils.html
>>  
>> (and actually you may want to move to using JsInterop rather than JSNI, and 
>> maybe Elemental 2)
>>
>> On Saturday, April 6, 2024 at 8:01:13 AM UTC+2 ma...@craig-mitchell.com 
>> wrote:
>>
>>> I ran into this.  GWT is too smart sometimes.  :)
>>>
>>> For my example, I was querying an API for WebRTC ICE servers, which 
>>> returned a string which was a JSON array.
>>>
>>> When I had:
>>>
>>> private static native JavaScriptObject createPeerConnection(String 
>>> iceServersJson) /*-{
>>>   var peerConnectionConfig = {
>>> iceServers: iceServersJson
>>>   };
>>>   return new RTCPeerConnection(peerConnectionConfig);
>>> }-*/;
>>>
>>> GWT excaped the quotes, so iceServers switched from an array, to just a 
>>> string, exactly like I asked it to.
>>>
>>> So, really, I needed what Thomas suggested:
>>>
>>> JavaScriptObject iceServersObj = ((JSONArray)JSONParser.parseStrict(
>>> iceServersJson)).getJavaScriptObject();
>>>
>>> private static native JavaScriptObject 
>>> createPeerConnecti

Re: How to unescape a JSONString?

2024-04-10 Thread Craig Mitchell
You weren't kidding.  I checked the compiled JS, and there it is (with some 
smarts to minimise the JS it looks like):
this.a = new U2b(d,c,(n = {
iceServers: m
},
new RTCPeerConnection(n)));

Thanks for letting me know about JsonUtils.safeEval(...)  That is a better 
option.

I never had much luck with JsInterop.  I just tried it again, trying to map 
the RTCPeerConnection 
<https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/RTCPeerConnection>,
 
but it doesn't work giving me "TypeError: Cannot read properties of 
undefined" when I try to instanciate it.  I also can't debug it, as I can't 
step into the constructor to see what's going wrong.

This was my failed attempt:

@JsType(isNative = true)
public class RTCPeerConnection {
  @JsConstructor
  public RTCPeerConnection(JavaScriptObject iceServersJsoArray) {
super();
  }
  public native void close();
}


On Sunday 7 April 2024 at 4:20:48 am UTC+10 Thomas Broyer wrote:

> There's no escaping. You have a string value, it stays a string value. If 
> its content is JSON representing an array and you want that array, then 
> indeed you have to parse the JSON.
>
> It looks like there's a major misunderstanding about what GWT does with 
> your code, and/or possibly where/when the code runs or something.
> GWT "only" translates the Java syntax to JS (and also optimizes 
> everything), and therefore comes with a library of classes that emulates 
> the Java runtime core classes so they can also be translated the same way 
> as your code. JSNI is an escape hatch to be able to "put JS syntax inside 
> your Java syntax", but that's all.
> In other words, if you have a string "[ 42, true, null ]" in a variable 
> (that you retrieved from your server), if you call that method, it's 
> exactly equivalent to this JS:
> var iceServersJson = "[ 42, true, null ]";
> var peerConnectionConfig = {
>   iceServers: iceServersJson
> };
> i.e. the peerConnectionConfig object has an iceServers property whose 
> value is just the iceServersJson string value.
> GWT won't "magically" generate JS code at runtime replacing the value 
> as-is to form some new JS each time, i.e. it *won't* become:
> var peerConnectionConfig = {
>   iceServers: [ 42, true, null ]
> };
> No, really, that Java/JSNI function is transformed to this JS function:
> function createPeerConnection(iceServersJson) {
>   var peerConnectionConfig = {
> iceServers: iceServersJson
>   };
>   return new RTCPeerConnection(peerConnectionConfig);
> }
> and then at one point you call it. It's your job to give it either a 
> string value or parse the string value as JSON and passe the result.
>
> Kudos to resurrecting a 15 years old post though! 藍
>
> BTW, you may want to prefer JsonUtils.safeEval(iceServersJson) here: 
> https://www.gwtproject.org/javadoc/latest/com/google/gwt/core/client/JsonUtils.html
>  
> (and actually you may want to move to using JsInterop rather than JSNI, and 
> maybe Elemental 2)
>
> On Saturday, April 6, 2024 at 8:01:13 AM UTC+2 ma...@craig-mitchell.com 
> wrote:
>
>> I ran into this.  GWT is too smart sometimes.  :)
>>
>> For my example, I was querying an API for WebRTC ICE servers, which 
>> returned a string which was a JSON array.
>>
>> When I had:
>>
>> private static native JavaScriptObject createPeerConnection(String 
>> iceServersJson) /*-{
>>   var peerConnectionConfig = {
>> iceServers: iceServersJson
>>   };
>>   return new RTCPeerConnection(peerConnectionConfig);
>> }-*/;
>>
>> GWT excaped the quotes, so iceServers switched from an array, to just a 
>> string, exactly like I asked it to.
>>
>> So, really, I needed what Thomas suggested:
>>
>> JavaScriptObject iceServersObj = ((JSONArray)JSONParser.parseStrict(
>> iceServersJson)).getJavaScriptObject();
>>
>> private static native JavaScriptObject createPeerConnection(JavaScriptObject 
>> iceServersJson) /*-{
>>   var peerConnectionConfig = {
>> iceServers: iceServersJson
>>   };
>>   return new RTCPeerConnection(peerConnectionConfig);
>> }-*/;
>>
>> Now I'm telling GWT it's a JSO, and GWT knows not to escape it.
>>
>> On Monday 9 November 2009 at 10:25:24 pm UTC+11 Thomas Broyer wrote:
>>
>>>
>>>
>>> On Nov 9, 11:47 am, peterk  wrote: 
>>> > I'm having some trouble dealing with escaping and unescaping of Java 
>>> > strings for encoding in JSON. 
>>> > 
>>> > I use JSONString to encode a Java string and that seems to work ok. 
>>> > For example, newlines turn into \n, tabs turn into 

Re: How to unescape a JSONString?

2024-04-06 Thread Craig Mitchell
I ran into this.  GWT is too smart sometimes.  :)

For my example, I was querying an API for WebRTC ICE servers, which 
returned a string which was a JSON array.

When I had:

private static native JavaScriptObject createPeerConnection(String 
iceServersJson) /*-{
  var peerConnectionConfig = {
iceServers: iceServersJson
  };
  return new RTCPeerConnection(peerConnectionConfig);
}-*/;

GWT excaped the quotes, so iceServers switched from an array, to just a 
string, exactly like I asked it to.

So, really, I needed what Thomas suggested:

JavaScriptObject iceServersObj = ((JSONArray)JSONParser.parseStrict(
iceServersJson)).getJavaScriptObject();

private static native JavaScriptObject createPeerConnection(JavaScriptObject 
iceServersJson) /*-{
  var peerConnectionConfig = {
iceServers: iceServersJson
  };
  return new RTCPeerConnection(peerConnectionConfig);
}-*/;

Now I'm telling GWT it's a JSO, and GWT knows not to escape it.

On Monday 9 November 2009 at 10:25:24 pm UTC+11 Thomas Broyer wrote:

>
>
> On Nov 9, 11:47 am, peterk  wrote:
> > I'm having some trouble dealing with escaping and unescaping of Java
> > strings for encoding in JSON.
> >
> > I use JSONString to encode a Java string and that seems to work ok.
> > For example, newlines turn into \n, tabs turn into \t and so on.
> >
> > However, given this escaped sequence back, how to I turn this back
> > into an unescaped javastring wheren \n is turned into a newline and so
> > on?
> >
> > If I use stringvalue() on the JSONString it just gives back the same
> > json encoded string with the \n and \t encoding etc.
> >
> > Anyone have any ideas? :)
>
> JSONParser.parse? ;-)

-- 
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/a57c3d85-8385-4021-bdd9-0082f8deffa8n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-03-04 Thread Craig Mitchell
Thank you Frank for making the excellent tool!  Just checked the changes, 
working perfectly.  

On Monday 4 March 2024 at 7:55:58 pm UTC+11 Frank Hossfeld wrote:

> Thanks Craig for contributing. New version is online.
>
> Frank Hossfeld schrieb am Dienstag, 6. Februar 2024 um 08:11:15 UTC+1:
>
>> new version is online ... 
>>
>> Craig Mitchell schrieb am Montag, 5. Februar 2024 um 02:13:45 UTC+1:
>>
>>> Done:  
>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/4  
>>> Cheers.
>>>
>>> On Monday 5 February 2024 at 3:59:55 am UTC+11 Frank Hossfeld wrote:
>>>
>>>> Please can you open an issue regarding the gwt-servlet-jakarta problem 
>>>> ...
>>>>
>>>> Thanks
>>>>
>>>> Craig Mitchell schrieb am Sonntag, 4. Februar 2024 um 04:57:34 UTC+1:
>>>>
>>>>> I noticed that it always logs the error:
>>>>>
>>>>> ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not 
>>>>> found; did you forget to include it in this deployment?
>>>>>
>>>>> on the first RPC call.  The RPC still seems to work fine, but 
>>>>> wondering if this is an issue or not?
>>>>>
>>>>> Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"?  
>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16
>>>>>  
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell wrote:
>>>>>
>>>>>> Just realised you can also set it in your server pom.xml, in the 
>>>>>> Spring Boot Maven plugin (configuration > jvmArguments), instead of the 
>>>>>> launcher:
>>>>>>
>>>>>> 
>>>>>>   org.springframework.boot
>>>>>>   spring-boot-maven-plugin
>>>>>>   
>>>>>> 
>>>>>>   
>>>>>> repackage
>>>>>>   
>>>>>> 
>>>>>>   
>>>>>>   
>>>>>> false
>>>>>> 
>>>>>>   
>>>>>> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000
>>>>>> 
>>>>>>   
>>>>>> 
>>>>>>
>>>>>> On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote:
>>>>>>
>>>>>>> Thanks Thomas.  Now switched to:
>>>>>>>
>>>>>>>
>>>>>>> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000
>>>>>>>
>>>>>>> [image: Screen.png]
>>>>>>>
>>>>>>> Which also works great.  
>>>>>>>
>>>>>>> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote:
>>>>>>>
>>>>>>>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) 
>>>>>>>> rather than the legacy -Xdebug -Xrunjdwp (and then you no longer need 
>>>>>>>> the 
>>>>>>>> quotes )
>>>>>>>>
>>>>>>>> And when I say legacy, I really mean it: already in Java 8 -Xdebug 
>>>>>>>> does nothing (
>>>>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI)
>>>>>>>>  
>>>>>>>> and Xrunjdwp is superceded by agentlib (
>>>>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG
>>>>>>>> )
>>>>>>>>
>>>>>>>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 
>>>>>>>> ma...@craig-mitchell.com wrote:
>>>>>>>>
>>>>>>>>> Thank you!  Working great now (quotes were important).  
>>>>>>>>>
>>>>>>>>> [image: Screen.png]
>>>>>>>>>
>>>>>>>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld 
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Mmmh, it might be worth adding this information to the archetype 
>>>>>>>>>> docs.
>>>>>>>>>>
>>>>>>>>>>

-- 
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/bec9bbcc-741f-4e49-be12-8dd572abd2ecn%40googlegroups.com.


Re: Deobfuscated stack trace message and line-specific stack traces

2024-02-28 Thread Craig Mitchell
Thanks again Thomas.  


  

  net.ltgt.gwt.maven
  gwt-maven-plugin
  
com.mycompany.mywebapp.App
mywebapp
${project.build.directory}/${project.build.finalName}/WEB-INF/deploy
  

  


On Tuesday 27 February 2024 at 4:06:12 am UTC+11 Thomas Broyer wrote:

> On Monday, February 26, 2024 at 11:56:45 AM UTC+1 ma...@craig-mitchell.com 
> wrote:
>
> Thanks Thomas, now working great!
>
> For anyone coming from the Eclipse GWT plugin, you can do this to keep it 
> consistant with how it used to work:
>
> In your client pom.  Add the  like this:
> 
>   
> 
>   net.ltgt.gwt.maven
>   gwt-maven-plugin
>   
> com.mycompany.mywebapp.App
> mywebapp
>  >${project.build.directory}/mywebapp-client-HEAD-SNAPSHOT/WEB-INF/deploy deploy>
>
>
> nit: use ${project.build.finalName} rather than hard-coding the 
> "mywebapp-client-HEAD-SNAPSHOT"
>
> https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html#webappDirectory
>
>

-- 
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/c3eddfb9-5590-4be4-9db5-a4ff22cd4e61n%40googlegroups.com.


Re: Deobfuscated stack trace message and line-specific stack traces

2024-02-26 Thread Craig Mitchell
Thanks Thomas, now working great!

For anyone coming from the Eclipse GWT plugin, you can do this to keep it 
consistant with how it used to work:

In your client pom.  Add the  like this:

  

  net.ltgt.gwt.maven
  gwt-maven-plugin
  
com.mycompany.mywebapp.App
mywebapp
${project.build.directory}/mywebapp-client-HEAD-SNAPSHOT/WEB-INF/deploy
  

  


And then instead of reading the symbol maps directly like this:
  String path = config.getServletContext().getRealPath(
"/WEB-INF/deploy//symbolMaps/");
  StackTraceDeobfuscator deobfuscator = StackTraceDeobfuscator.
fromFileSystem(path);

You now read them from inside the war like this:
  StackTraceDeobfuscator deobfuscator = StackTraceDeobfuscator.fromResource(
"/WEB-INF/deploy//symbolMaps/");

Cheers.

On Monday 26 February 2024 at 8:03:27 am UTC+11 Thomas Broyer wrote:

> On Sunday, February 25, 2024 at 12:34:44 AM UTC+1 ma...@craig-mitchell.com 
> wrote:
>
> Sorry, I do see them in  
> mywebapp-client\target\gwt\deploy\mywebapp\symbolMaps
>
> How do I get them from there, into the war?
>
>
> Configure  to somewhere inside the  (preferably 
> inside WEB-INF so they won't be served)
> https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html#deploy
>

-- 
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/6ae923cb-f73f-41f6-bbd8-67879122e8cfn%40googlegroups.com.


Re: Deploy to Google App Engine (GAE)

2024-02-24 Thread Craig Mitchell
> *My question is: what do you expect from such an archetype?*

It would be great to have an example for a minimum viable product.  So how 
to do a mvn package on an app created 
with https://github.com/tbroyer/gwt-maven-archetypes to get an executable 
jar that doesn't need an existing web server.

> *I could easily write a Main class that runs an embedded Jetty server 
with the configured GWT-RPC servlet and serving static resources from 
multiple dirs.*

If that's what we need to get an executable jar, yes please!  

On Sunday 25 February 2024 at 9:40:35 am UTC+11 Thomas Broyer wrote:

> In retrospect, I think the GWT BOM (to avoid managing non-GWT dependencies 
> where there's no need to) possibly either should only be used in the client 
> module, or should really only list GWT artifacts. That being said, if you 
> use the Jetty BOM in the server module (and you should), it should override 
> the GWT BOM.
>
> On Saturday, February 24, 2024 at 8:11:38 PM UTC+1 tim_mac...@yahoo.co.uk 
> wrote:
>
>> The gwt artifact is indeed in dependency management, but when the 
>> jetty-main jar for jetty 11 is a dependency of server module it draws in 
>> jetty 9 dependencies and and also gwt-servlet leading to a no javax-servlet 
>> error. Remove gwt from the root fixes it.  Maybe this will cause problems 
>> beyond this sample.
>>
>>
>> Sent from Yahoo Mail on Android 
>> <https://mail.onelink.me/107872968?pid=nativeplacement=Global_Acquisition_YMktg_315_Internal_EmailSignature_sub1=Acquisition_sub2=Global_YMktg_sub3=_sub4=10604_sub5=EmailSignature__Static_>
>>
>> On Sat, Feb 24, 2024 at 12:14, Thomas Broyer
>>  wrote:
>> I could easily write a Main class that runs an embedded Jetty server 
>> jagwtvax(
>> https://eclipse.dev/jetty/documentation/jetty-12/programming-guide/index.html#pg-server-http-handler-use-servlet-context)
>>  
>> with the configured GWT-RPC servlet and serving static resources from 
>> multiple dirs (
>> https://eclipse.dev/jetty/documentation/jetty-12/programming-guide/index.html#pg-server-http-handler-use-resource),
>>  
>> but then there would still be a whole lot of questions either unanswered or 
>> with an necessarily opinionated answer:
>>
>>
>>- how to set "dev mode" for the Main class? (to add the codeserver's 
>>launcherDir to the resource bases; I would personally use a system 
>> property 
>>with the launcherDir's path and react to its presence/absence)
>>- how to package/deploy the static resources? as resources in the 
>>JAR? (that's what I'd do if I'd wanted my deliverable to be a single JAR) 
>>as a directory alongside the JAR? (that's what I'd do if my deliverable 
>>were a native deb/rpm/whatever package or a Docker image)
>>- that Main class would likely not be production-ready (should it use 
>>the QoSHandler? GzipHandler? how about the CrossOriginHandler? the 
>>ForwardedRequestCustomizer 
>>
>> <https://eclipse.dev/jetty/javadoc/jetty-12/org/eclipse/jetty/server/ForwardedRequestCustomizer.html>
>>?)
>>- you'd probably want to refactor the Main class anyway to add 
>>command-line arguments and/or configuration files, a logging framework, 
>>possibly dependency-injection, etc.
>>
>> My question is: *what do you expect from such an archetype?*
>>
>> The initial goal was to show how to cleanly/clearly separate 
>> client/shared/server classpaths, which involves some configuration for how 
>> to run the server so it serves the codeserver's launcherDir. As soon as you 
>> go "custom" on the server, you have to handle that specific "dev mode" 
>> configuration, but then it's custom to your custom code, and necessarily 
>> becomes somewhat opinionated. This means that the archetype can't really 
>> "show you how to do things" without being opinionated, and I don't want to 
>> go that road (I specifically don't want to *maintain* such an 
>> opinionated thing). Feel free to create opinionated archetypes though, and 
>> I'll happily review them and help you set them up (this will bring my own 
>> opinions into the mix though)
>>
>>
>> On Friday, February 23, 2024 at 12:05:22 AM UTC+1 
>> ma...@craig-mitchell.com wrote:
>>
>> I know it's outside of its scope, but it would be great if 
>> https://github.com/tbroyer/gwt-maven-archetypes had an example of "If 
>> you want to create an executable jar with Jetty, this is how you could do 
>> it".  
>>
>> On Thursday 22 February 2024 at 5:30:51 am UTC+11 Tim Macpherson wrote:
>>
>

Re: Deobfuscated stack trace message and line-specific stack traces

2024-02-24 Thread Craig Mitchell
Sorry, I do see them in  
mywebapp-client\target\gwt\deploy\mywebapp\symbolMaps

How do I get them from there, into the war?

On Sunday 25 February 2024 at 10:30:14 am UTC+11 Craig Mitchell wrote:

> Hi George,
>
> What I did was:
>
>1. Run https://github.com/tbroyer/gwt-maven-archetypes to generate the 
>sample app.
>2. Modify module.gwt.xml to have: value="native" />
>3. Run mvn clean package.
>
> Then when I look inside 
> mywebapp-server\target\mywebapp-server-HEAD-SNAPSHOT.war I see the mywebapp 
> folder with all the compiled javascript, but no symbolMaps.
>
> I also tried with:
> 
>  value="true" />
>  value="true"/>
>
> Still no symbol maps.
>
> Any ideas on what I'm missing would be great.  Thanks.
>
> On Sunday 25 February 2024 at 12:45:57 am UTC+11 George Paret wrote:
>
>> I see the symbolmaps generated in ` 
>> target/gwt/deploy//symbolMaps ` 
>>
>> I believe it is generated by default. 
>>
>> On Friday, February 23, 2024 at 10:27:12 PM UTC-6 Craig Mitchell wrote:
>>
>>> The symbol maps worked great with the Eclipse GWT plugin compiler.
>>>
>>> Now switched to use the Maven compiler (with the 
>>> https://github.com/tbroyer/gwt-maven-archetypes architecture), I don't 
>>> see the symbol maps anywhere when doing a mvn clean package.
>>>
>>> Do I need to do something extra to get them?
>>>
>>> Thanks.
>>>
>>> On Saturday 18 May 2019 at 8:48:47 am UTC+10 Craig Mitchell wrote:
>>>
>>>> Thank you Alexander!  That's what I was missing.
>>>>
>>>> Called:
>>>> exception = SerializableThrowable.fromThrowable(exception);
>>>>
>>>> before sending to the server, and now the stack traces show perfectly.  
>>>> :-)
>>>>
>>>

-- 
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/ae4ca692-8890-406a-8b6b-44eaa5412e3cn%40googlegroups.com.


Re: Deobfuscated stack trace message and line-specific stack traces

2024-02-24 Thread Craig Mitchell
Hi George,

What I did was:

   1. Run https://github.com/tbroyer/gwt-maven-archetypes to generate the 
   sample app.
   2. Modify module.gwt.xml to have: 
   3. Run mvn clean package.

Then when I look inside 
mywebapp-server\target\mywebapp-server-HEAD-SNAPSHOT.war I see the mywebapp 
folder with all the compiled javascript, but no symbolMaps.

I also tried with:




Still no symbol maps.

Any ideas on what I'm missing would be great.  Thanks.

On Sunday 25 February 2024 at 12:45:57 am UTC+11 George Paret wrote:

> I see the symbolmaps generated in ` 
> target/gwt/deploy//symbolMaps ` 
>
> I believe it is generated by default. 
>
> On Friday, February 23, 2024 at 10:27:12 PM UTC-6 Craig Mitchell wrote:
>
>> The symbol maps worked great with the Eclipse GWT plugin compiler.
>>
>> Now switched to use the Maven compiler (with the 
>> https://github.com/tbroyer/gwt-maven-archetypes architecture), I don't 
>> see the symbol maps anywhere when doing a mvn clean package.
>>
>> Do I need to do something extra to get them?
>>
>> Thanks.
>>
>> On Saturday 18 May 2019 at 8:48:47 am UTC+10 Craig Mitchell wrote:
>>
>>> Thank you Alexander!  That's what I was missing.
>>>
>>> Called:
>>> exception = SerializableThrowable.fromThrowable(exception);
>>>
>>> before sending to the server, and now the stack traces show perfectly.  
>>> :-)
>>>
>>

-- 
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/693aea27-01f7-4bde-92df-2a8faa8fbbc2n%40googlegroups.com.


Re: Deobfuscated stack trace message and line-specific stack traces

2024-02-23 Thread Craig Mitchell
The symbol maps worked great with the Eclipse GWT plugin compiler.

Now switched to use the Maven compiler (with 
the https://github.com/tbroyer/gwt-maven-archetypes architecture), I don't 
see the symbol maps anywhere when doing a mvn clean package.

Do I need to do something extra to get them?

Thanks.

On Saturday 18 May 2019 at 8:48:47 am UTC+10 Craig Mitchell wrote:

> Thank you Alexander!  That's what I was missing.
>
> Called:
> exception = SerializableThrowable.fromThrowable(exception);
>
> before sending to the server, and now the stack traces show perfectly.  :-)
>

-- 
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/27634127-7067-4bc7-b958-2043b61f3f46n%40googlegroups.com.


Re: Deploy to Google App Engine (GAE)

2024-02-23 Thread Craig Mitchell
>  *Could try moving the gwt dependency out of the root pom, keeping it 
only for the client, just gwt-servlet for sever and shared ( unless anyone 
knows better). That will clean up the server dependencies but may cause 
other problems *

I believe that's how it works now.  The root pom just has the 
dependencyManagement ( 
https://github.com/tbroyer/gwt-maven-archetypes/blob/main/modular-webapp/src/test/resources/projects/basic-webapp/reference/pom.xml#L17
 
).  It doesn't actaully include it as a dependency.

The server and shared module poms include the gwt-servlet lib, and the 
client pom includes the gwt-user + gwt-dev libs.

On Saturday 24 February 2024 at 4:29:28 am UTC+11 Tim Macpherson wrote:

> Could try moving the gwt dependency out of the root pom, keeping it only 
> for the client, just gwt-servlet for sever and shared ( unless anyone knows 
> better). That will clean up the server dependencies but may cause other 
> problems 
>
> Sent from Yahoo Mail on Android 
> <https://mail.onelink.me/107872968?pid=nativeplacement=Global_Acquisition_YMktg_315_Internal_EmailSignature_sub1=Acquisition_sub2=Global_YMktg_sub3=_sub4=10604_sub5=EmailSignature__Static_>
>
> On Fri, Feb 23, 2024 at 6:44, Ralph Fiergolla
>  wrote:
>
> Don’t want to build up pressure, but yeah that would come in very handy 
>
> Craig Mitchell  schrieb am Fr. 23. Feb. 2024 um 
> 00:05:
>
> I know it's outside of its scope, but it would be great if 
> https://github.com/tbroyer/gwt-maven-archetypes had an example of "If you 
> want to create an executable jar with Jetty, this is how you could do it".  
> 
>
> On Thursday 22 February 2024 at 5:30:51 am UTC+11 Tim Macpherson wrote:
>
> I tried starting with the tbroyer archetype & to the server project I 
> added the app engine stuff from the Google sample to build the 
> appengine-staging dependencies directory.
> Maybe all that should be in a separate project ?
>
> Sent from Yahoo Mail on Android 
> <https://mail.onelink.me/107872968?pid=nativeplacement=Global_Acquisition_YMktg_315_Internal_EmailSignature_sub1=Acquisition_sub2=Global_YMktg_sub3=_sub4=10604_sub5=EmailSignature__Static_>
>
> On Wed, Feb 21, 2024 at 17:42, Thomas Broyer
>  wrote:
>
>
>
> On Wednesday, February 21, 2024 at 3:11:54 PM UTC+1 tim_mac...@yahoo.co.uk 
> wrote:
>
> I've been trying this app engine sample for Java 11+ which uses a JAR 
> packaged artifact that is installed locally:
> it provides a Main class to instantiate an HTTP server to run an embedded 
> web application WAR file.
>
> github.com/GoogleCloudPlatform/java-docs-samples/tree/main/appengine-java11/appengine-simple-jetty-main
> It has explicit jetty 11 dependencies.
>
> The WAR project is
>
> github.com/GoogleCloudPlatform/java-docs-samples/tree/master/appengine-java11/helloworld-servlet
> The WAR is run in a local server with:
> mvn exec:java -Dexec.args="../helloworld-servlet/target/helloworld.war"
>
> The problem I have is when I include GWT in the WAR project this draws in 
> Jetty 9 & other dependencies
> which get copied to the cloud-deployment dependencies directory.
>
>
> This means you WAR have dependencies on gwt-user and/or gwt-dev, that you 
> never want to deploy to a server. The WAR should have a dependency on 
> gwt-servlet only (or requestfactory-server).
>
> …and this is exactly what https://github.com/tbroyer/gwt-maven-archetypes 
> were meant to solve.
>
> -- 
>
> 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/c04ab91a-b898-489d-a509-6fafb9a363can%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/google-web-toolkit/c04ab91a-b898-489d-a509-6fafb9a363can%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> -- 
> 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/b4234f67-24c8-4028-8d27-be044a29c733n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/google-web-toolkit/b4234f67-24c8-4028-8d27-be044a29c733n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "GWT Users" group.
> To unsubscribe f

Re: Deploy to Google App Engine (GAE)

2024-02-22 Thread Craig Mitchell
I know it's outside of its scope, but it would be great 
if https://github.com/tbroyer/gwt-maven-archetypes had an example of "If 
you want to create an executable jar with Jetty, this is how you could do 
it".  

On Thursday 22 February 2024 at 5:30:51 am UTC+11 Tim Macpherson wrote:

> I tried starting with the tbroyer archetype & to the server project I 
> added the app engine stuff from the Google sample to build the 
> appengine-staging dependencies directory.
> Maybe all that should be in a separate project ?
>
> Sent from Yahoo Mail on Android 
> 
>
> On Wed, Feb 21, 2024 at 17:42, Thomas Broyer
>  wrote:
>
>
>
> On Wednesday, February 21, 2024 at 3:11:54 PM UTC+1 tim_mac...@yahoo.co.uk 
> wrote:
>
> I've been trying this app engine sample for Java 11+ which uses a JAR 
> packaged artifact that is installed locally:
> it provides a Main class to instantiate an HTTP server to run an embedded 
> web application WAR file.
>
> github.com/GoogleCloudPlatform/java-docs-samples/tree/main/appengine-java11/appengine-simple-jetty-main
> It has explicit jetty 11 dependencies.
>
> The WAR project is
>
> github.com/GoogleCloudPlatform/java-docs-samples/tree/master/appengine-java11/helloworld-servlet
> The WAR is run in a local server with:
> mvn exec:java -Dexec.args="../helloworld-servlet/target/helloworld.war"
>
> The problem I have is when I include GWT in the WAR project this draws in 
> Jetty 9 & other dependencies
> which get copied to the cloud-deployment dependencies directory.
>
>
> This means you WAR have dependencies on gwt-user and/or gwt-dev, that you 
> never want to deploy to a server. The WAR should have a dependency on 
> gwt-servlet only (or requestfactory-server).
>
> …and this is exactly what https://github.com/tbroyer/gwt-maven-archetypes 
> were meant to solve.
>
> -- 
>
> 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/c04ab91a-b898-489d-a509-6fafb9a363can%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/b4234f67-24c8-4028-8d27-be044a29c733n%40googlegroups.com.


Re: Deploy to Google App Engine (GAE)

2024-02-20 Thread Craig Mitchell
Now I have it all working.  This is what I found:

Google App Engine Standard no longer gives you a web server, so you need to 
provide your own.

   - If you use https://github.com/tbroyer/gwt-maven-archetypes you get 
   Jetty when running in dev, but nothing when doing a mvn package (just a war 
   file that can be deployed to an existing web server - no good for Google 
   App Engine).
   - If you use https://github.com/NaluKit/gwt-maven-springboot-archetype 
   you get Embedded Tomcat, both in dev, and also when packaging to a war.  So 
   you can run java -jar myapp.war and it'll start using the embedded Tomcat 
   web server.

If you want to run on the cheap F1 Google App Engine instances, Tomcat is 
too heavy, and you'll run out of memory.  You can easily switch Spring Boot 
to use Undertow, which is a lightweight web server, and runs great on the 
F1 instances.

Cheers.
On Wednesday 27 December 2023 at 4:15:34 am UTC+11 tim_mac...@yahoo.co.uk 
wrote:

> Maybe this thread is gettig a bit off-topic for gwt ? maybe more suitable 
> for Stackoverflow
> or
> https://groups.google.com/g/google-appengine
> & https://groups.google.com/g/google-cloud-dev
> now superceded by
> https://www.googlecloudcommunity.com/gc/Serverless/bd-p/cloud_serverless.
>
> On Tuesday, December 26, 2023 at 12:21:05 AM UTC Craig Mitchell wrote:
>
>> Odd, my message was deleted.  Maybe it was too boring.  :-D
>>
>> The highlights:
>>
>>- I'm not sure if you get a Jetty server bundled or not if you use 
>>the legacy bundled services.  The documentation is a little ambiguous to 
>> me.
>>- You do get a stand alone server "dev server" that you can deploy a 
>>war to.  Great for final testing, but it's unclear if you'll be able to 
>>debug on it.
>>- Your static files worked because the legacy version allows a war 
>>file, and you have the maven-war-plugin in your POM.
>>- If I switch to SpringBoot, I'll move my static files to either 
>>a /public or /static directory.
>>
>> Personally, I'm going to skip the legacy bundled services, and just use 
>> the second-generation Java runtime with my own web server.
>>
>> Cheers!
>>
>> On Monday 25 December 2023 at 3:48:23 am UTC+11 tim_mac...@yahoo.co.uk 
>> wrote:
>>
>>> Looks like Cloud CLI provides a dev server if  using the legacy bundled 
>>> services (App Engine API JAR)?
>>>  
>>> https://cloud.google.com/appengine/docs/standard/java-gen2/services/access
>>> If you are using the legacy bundled services, the second-generation Java 
>>> runtimes provide the Jetty web-serving framework.
>>>
>>> https://cloud.google.com/appengine/migration-center/standard/migrate-to-second-gen/java-differences#framework_flexibility
>>> The Google Cloud CLI for Java includes a local development server for 
>>> testing your application on your computer. The local development server 
>>> emulates the App Engine Java runtime environment and all of its services, 
>>> including Datastore.
>>>
>>> https://cloud.google.com/appengine/docs/standard/tools/using-local-server?tab=java
>>> What do you think ?
>>>
>>> Re. static files: in my setup appengine:deploy at base directory server 
>>> project deploys  SNAPSHOT.war. 
>>> Static files in \src\main\webapp end up in its root directory. 
>>> This:  
>>> https://stackoverflow.com/questions/71673962/while-running-as-a-jar-application-not-able-to-access-static-files-in-springboo
>>> says in the case of a JAR-file, src/main/webapp has no special meaning 
>>> and goes on about jar directories that work with Springboot.
>>>
>>>
>>>

-- 
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/2f8c2654-3a31-49ac-bb7f-761e173b08e4n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-02-04 Thread Craig Mitchell
Done:  https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/4  
Cheers.

On Monday 5 February 2024 at 3:59:55 am UTC+11 Frank Hossfeld wrote:

> Please can you open an issue regarding the gwt-servlet-jakarta problem ...
>
> Thanks
>
> Craig Mitchell schrieb am Sonntag, 4. Februar 2024 um 04:57:34 UTC+1:
>
>> I noticed that it always logs the error:
>>
>> ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not 
>> found; did you forget to include it in this deployment?
>>
>> on the first RPC call.  The RPC still seems to work fine, but wondering 
>> if this is an issue or not?
>>
>> Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"?  
>> https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16
>>  
>>
>> Thanks.
>>
>> On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell wrote:
>>
>>> Just realised you can also set it in your server pom.xml, in the Spring 
>>> Boot Maven plugin (configuration > jvmArguments), instead of the launcher:
>>>
>>> 
>>>   org.springframework.boot
>>>   spring-boot-maven-plugin
>>>   
>>> 
>>>   
>>> repackage
>>>   
>>> 
>>>   
>>>   
>>> false
>>> 
>>>   
>>> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000
>>> 
>>>   
>>> 
>>>
>>> On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote:
>>>
>>>> Thanks Thomas.  Now switched to:
>>>>
>>>>
>>>> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000
>>>>
>>>> [image: Screen.png]
>>>>
>>>> Which also works great.  
>>>>
>>>> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote:
>>>>
>>>>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather 
>>>>> than the legacy -Xdebug -Xrunjdwp (and then you no longer need the 
>>>>> quotes )
>>>>>
>>>>> And when I say legacy, I really mean it: already in Java 8 -Xdebug 
>>>>> does nothing (
>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI)
>>>>>  
>>>>> and Xrunjdwp is superceded by agentlib (
>>>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG
>>>>> )
>>>>>
>>>>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 
>>>>> ma...@craig-mitchell.com wrote:
>>>>>
>>>>>> Thank you!  Working great now (quotes were important).  
>>>>>>
>>>>>> [image: Screen.png]
>>>>>>
>>>>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote:
>>>>>>
>>>>>>> Mmmh, it might be worth adding this information to the archetype 
>>>>>>> docs.
>>>>>>>
>>>>>>>

-- 
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/240ba6fb-e55e-4130-850e-c558f7ae5f93n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-02-03 Thread Craig Mitchell
I noticed that it always logs the error:

ERROR: The serialization policy file '/mywebapp/xxx.gwt.rpc' was not found; 
did you forget to include it in this deployment?

on the first RPC call.  The RPC still seems to work fine, but wondering if 
this is an issue or not?

Also, should this be "gwt-servlet-jakarta", not "gwt-servlet"?  
https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/basic-webapp-shared/pom.xml#L16
 

Thanks.

On Saturday 3 February 2024 at 11:10:34 am UTC+11 Craig Mitchell wrote:

> Just realised you can also set it in your server pom.xml, in the Spring 
> Boot Maven plugin (configuration > jvmArguments), instead of the launcher:
>
> 
>   org.springframework.boot
>   spring-boot-maven-plugin
>   
> 
>   
> repackage
>   
> 
>   
>   
> false
> 
>   -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000
> 
>   
> 
>
> On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote:
>
>> Thanks Thomas.  Now switched to:
>>
>>
>> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000
>>
>> [image: Screen.png]
>>
>> Which also works great.  
>>
>> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote:
>>
>>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather 
>>> than the legacy -Xdebug -Xrunjdwp (and then you no longer need the 
>>> quotes )
>>>
>>> And when I say legacy, I really mean it: already in Java 8 -Xdebug does 
>>> nothing (
>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI)
>>>  
>>> and Xrunjdwp is superceded by agentlib (
>>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG
>>> )
>>>
>>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 
>>> ma...@craig-mitchell.com wrote:
>>>
>>>> Thank you!  Working great now (quotes were important).  
>>>>
>>>> [image: Screen.png]
>>>>
>>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote:
>>>>
>>>>> Mmmh, it might be worth adding this information to the archetype docs.
>>>>>
>>>>>

-- 
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/3e0a9e6d-3481-4565-948f-21fb3f6a75b4n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-02-02 Thread Craig Mitchell
Just realised you can also set it in your server pom.xml, in the Spring 
Boot Maven plugin (configuration > jvmArguments), instead of the launcher:


  org.springframework.boot
  spring-boot-maven-plugin
  

  
repackage
  

  
  
false

  -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000

  


On Friday 2 February 2024 at 9:54:46 am UTC+11 Craig Mitchell wrote:

> Thanks Thomas.  Now switched to:
>
>
> -Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000
>
> [image: Screen.png]
>
> Which also works great.  
>
> On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote:
>
>> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather 
>> than the legacy -Xdebug -Xrunjdwp (and then you no longer need the 
>> quotes )
>>
>> And when I say legacy, I really mean it: already in Java 8 -Xdebug does 
>> nothing (
>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI)
>>  
>> and Xrunjdwp is superceded by agentlib (
>> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG
>> )
>>
>> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 
>> ma...@craig-mitchell.com wrote:
>>
>>> Thank you!  Working great now (quotes were important).  
>>>
>>> [image: Screen.png]
>>>
>>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote:
>>>
>>>> Mmmh, it might be worth adding this information to the archetype docs.
>>>>
>>>>

-- 
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/103b2e21-3427-476d-bda8-d6c38766d7f7n%40googlegroups.com.


Re: Question about setting GWT RPC timeout

2024-02-01 Thread Craig Mitchell
You could just create a generic method to do is for all your 
GWT.create(service) services.  Eg:

public static void setTimeout(ServerAsync myService) {
  myService.setRpcRequestBuilder(new RpcRequestBuilder() {
@Override
protected RequestBuilder doCreate(String serviceEntryPoint) { 
  RequestBuilder builder = new RequestBuilder(RequestBuilder.POST, 
serviceEntryPoint);
builder.setTimeoutMillis(3); // 30 second timeout
return builder;
}
  });
  return myService;
}

ServerAsync myService1 = setTimeout(GWT.create(service1));
ServerAsync myService2 = setTimeout(GWT.create(service2));

On Friday 2 February 2024 at 10:06:24 am UTC+11 Blaze wrote:

> Hi all,
>
> I came across this thread, I have searched if there is some "global" 
> request timeout that we can set on a RPC calls, not RequestBuilder, but the 
> one from RemoteService created via GWT.create(service) ? 
> I coudnt find anything, any idea?
>
> Tnx
>
> On Thursday, April 6, 2023 at 2:16:47 PM UTC+2 Colin Alworth wrote:
>
>> What you're looking for is a way to re-try requests in the case where the 
>> server is unreachable, which is not something that HTTP or the browser 
>> gives you automatically. If you had a proxy, but the server itself was 
>> down, the proxy would likely return a 503 service unavailable status, which 
>> the client could use to retry until the service was available (which might 
>> only happen for a certain number of seconds or a certain number of tries). 
>> It might also be possible for a proxy to wait and retry the upstream server 
>> until it was available, but I can't think of a proxy right now with that 
>> feature.
>>
>> HTTP itself doesn't have a timeout feature at all either. The timeout 
>> that you're setting on the client side is a simple GWT Timer, if the 
>> request hasn't finished (either in success or failure), it cancels the 
>> upstream request and presents the failure you're seeing to the client.
>>
>> Be a little careful when implementing a retry mechanism, as it is 
>> possible that the call made it to the server, and the server performed the 
>> action, but the client lost internet connection while the response was on 
>> its way to the client - that is, retrying a non-idempotent or expensive 
>> action may cause problems you weren't expecting. A status code of 0 is 
>> usually the client's way of saying "I wasn't able to get any reply from the 
>> server for some reason" - taking that information and trying to do 
>> something simple and idempotent until a server connection can be 
>> reestablished lets you know that the server and network are both working 
>> again, followed by some "did my last action succeed" before trying again 
>> (or just let the user dismiss the message and try again) will help mitigate 
>> this class of issues. A proxy sending back a 503 is a safer way to be sure 
>> that the network connection is good, but only the server is down, so you 
>> can retry - but be aware that technically there might be a network issue 
>> between the proxy and server, though this is much less likely.
>>
>> Good luck,
>> Colin
>>
>> On Thursday, April 6, 2023 at 7:05:53 AM UTC-5 Dmitri wrote:
>>
>>> Dear Colin
>>>
>>> Thank you so much for your advice. I'll take a closer look at those 
>>> areas.
>>>
>>> Just a little clarification: The server is not running at all. Both 
>>> exceptions are generated from the client only with different timeout 
>>> settings when it cannot reach the server.
>>> When the server is running - no problems in both cases. The purpose of 
>>> the code is to make the client wait longer when the server is unreachable 
>>> due to temporary communication problems.
>>>
>>> PS there are some typos in the codes I provide which I made when 
>>> clean-up for posting., Please ignore them.
>>> Thank you again
>>>
>>> Best regards
>>> Dmitri
>>>
>>>
>>> On Thu, Apr 6, 2023 at 9:49 PM Colin Alworth  wrote:
>>>
 I believe you're experiencing different timeouts in different cases. 
 That is, the problem you're facing of a short timeout before you use your 
 RPC_TIMEOUT_MS is a server-side timeout (or potentially a proxy?), but 
 after you set a client-side timeout, the client is observing that the 
 server is taking too long, and terminating the call from its side, 
 resulting in the RequestTimeoutException.

 To confirm this, try setting the client-side timeout to something like 
 one minute, 60_000, and see that the error returns to the old message you 
 were seeing. A timeout set like this does not guarantee that the server 
 stops processing the request, only that the client stops waiting for it, 
 and it may not be appropriate for your use case at all.

 With the client-side timeout set to a reasonable amount or entirely 
 removed, take a closer look at the error message you're getting from the 
 server, and any server or proxy logs you're getting. If there is a proxy, 
 see if you 

Re: Question about setting GWT RPC timeout

2024-02-01 Thread Craig Mitchell
You can set the request builder on the GWT.create(service).  Ie:

ServerAsync myService = GWT.create(service);
myService.setRpcRequestBuilder(new RpcRequestBuilder() {
@Override
protected RequestBuilder doCreate(String serviceEntryPoint) {
RequestBuilder builder = new RequestBuilder(RequestBuilder.POST, 
serviceEntryPoint); 
builder.setTimeoutMillis(3); // 30 second timeout
return builder;
}
});

On Friday 2 February 2024 at 10:06:24 am UTC+11 Blaze wrote:

> Hi all,
>
> I came across this thread, I have searched if there is some "global" 
> request timeout that we can set on a RPC calls, not RequestBuilder, but the 
> one from RemoteService created via GWT.create(service) ? 
> I coudnt find anything, any idea?
>
> Tnx
>
> On Thursday, April 6, 2023 at 2:16:47 PM UTC+2 Colin Alworth wrote:
>
>> What you're looking for is a way to re-try requests in the case where the 
>> server is unreachable, which is not something that HTTP or the browser 
>> gives you automatically. If you had a proxy, but the server itself was 
>> down, the proxy would likely return a 503 service unavailable status, which 
>> the client could use to retry until the service was available (which might 
>> only happen for a certain number of seconds or a certain number of tries). 
>> It might also be possible for a proxy to wait and retry the upstream server 
>> until it was available, but I can't think of a proxy right now with that 
>> feature.
>>
>> HTTP itself doesn't have a timeout feature at all either. The timeout 
>> that you're setting on the client side is a simple GWT Timer, if the 
>> request hasn't finished (either in success or failure), it cancels the 
>> upstream request and presents the failure you're seeing to the client.
>>
>> Be a little careful when implementing a retry mechanism, as it is 
>> possible that the call made it to the server, and the server performed the 
>> action, but the client lost internet connection while the response was on 
>> its way to the client - that is, retrying a non-idempotent or expensive 
>> action may cause problems you weren't expecting. A status code of 0 is 
>> usually the client's way of saying "I wasn't able to get any reply from the 
>> server for some reason" - taking that information and trying to do 
>> something simple and idempotent until a server connection can be 
>> reestablished lets you know that the server and network are both working 
>> again, followed by some "did my last action succeed" before trying again 
>> (or just let the user dismiss the message and try again) will help mitigate 
>> this class of issues. A proxy sending back a 503 is a safer way to be sure 
>> that the network connection is good, but only the server is down, so you 
>> can retry - but be aware that technically there might be a network issue 
>> between the proxy and server, though this is much less likely.
>>
>> Good luck,
>> Colin
>>
>> On Thursday, April 6, 2023 at 7:05:53 AM UTC-5 Dmitri wrote:
>>
>>> Dear Colin
>>>
>>> Thank you so much for your advice. I'll take a closer look at those 
>>> areas.
>>>
>>> Just a little clarification: The server is not running at all. Both 
>>> exceptions are generated from the client only with different timeout 
>>> settings when it cannot reach the server.
>>> When the server is running - no problems in both cases. The purpose of 
>>> the code is to make the client wait longer when the server is unreachable 
>>> due to temporary communication problems.
>>>
>>> PS there are some typos in the codes I provide which I made when 
>>> clean-up for posting., Please ignore them.
>>> Thank you again
>>>
>>> Best regards
>>> Dmitri
>>>
>>>
>>> On Thu, Apr 6, 2023 at 9:49 PM Colin Alworth  wrote:
>>>
 I believe you're experiencing different timeouts in different cases. 
 That is, the problem you're facing of a short timeout before you use your 
 RPC_TIMEOUT_MS is a server-side timeout (or potentially a proxy?), but 
 after you set a client-side timeout, the client is observing that the 
 server is taking too long, and terminating the call from its side, 
 resulting in the RequestTimeoutException.

 To confirm this, try setting the client-side timeout to something like 
 one minute, 60_000, and see that the error returns to the old message you 
 were seeing. A timeout set like this does not guarantee that the server 
 stops processing the request, only that the client stops waiting for it, 
 and it may not be appropriate for your use case at all.

 With the client-side timeout set to a reasonable amount or entirely 
 removed, take a closer look at the error message you're getting from the 
 server, and any server or proxy logs you're getting. If there is a proxy, 
 see if you can connect directly to the server to rule out the proxy 
 setting 
 this short timeout. Very likely this is a configuration on the 
 server/proxy 
 that can be change to suit your requirements.

 On 

Re: gwt-maven-springboot-archetype updated ...

2024-02-01 Thread Craig Mitchell
Thanks Thomas.  Now switched to:

-Dspring-boot.run.jvmArguments=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8000

[image: Screen.png]

Which also works great.  

On Thursday 1 February 2024 at 7:44:19 pm UTC+11 Thomas Broyer wrote:

> You may want to use -agentlib:jdwp (as given by IntelliJ IDEA) rather than 
> the legacy -Xdebug -Xrunjdwp (and then you no longer need the quotes )
>
> And when I say legacy, I really mean it: already in Java 8 -Xdebug does 
> nothing (
> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABHDABI)
>  
> and Xrunjdwp is superceded by agentlib (
> https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html#BABDCEGG
> )
>
> On Wednesday, January 31, 2024 at 10:49:41 PM UTC+1 
> ma...@craig-mitchell.com wrote:
>
>> Thank you!  Working great now (quotes were important).  
>>
>> [image: Screen.png]
>>
>> On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote:
>>
>>> Mmmh, it might be worth adding this information to the archetype docs.
>>>
>>>

-- 
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/6429293d-9a59-427a-b627-aadb2f3c75c5n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-01-31 Thread Craig Mitchell
Thank you!  Working great now (quotes were important).  

[image: Screen.png]

On Thursday 1 February 2024 at 6:38:47 am UTC+11 Frank Hossfeld wrote:

> Mmmh, it might be worth adding this information to the archetype docs.
>
>

-- 
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/9b1b1eac-276b-41ba-affd-cfb2d57e64c8n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-01-31 Thread Craig Mitchell
Hi,

I'm able to debug the GWT client okay (in Chrome).  However, debugging the 
SpringBoot server in IntelliJ isn't working.

I already have the code server running, and then I start the server with:

mvnDebug spring-boot:run -pl mywebapp-server -am

The server then waits for the debugger to attach, so I start up a remote 
JVM debug in IntelliJ:

[image: Screen.png]

And it attaches to the server, which then triggers the server to continue 
its start.

Everything is now up and running great.

However, putting breakpoints in the server code in IntelliJ, the 
breakpoints never get hit.  Any suggestions as to why?

This might not be a GWT issue, so apologies if it isn't.

Thanks.

On Thursday 25 January 2024 at 5:55:48 pm UTC+11 Ralph Fiergolla wrote:

> Finally! Thanks a lot!
>
> Thomas Broyer  schrieb am Mi. 24. Jan. 2024 um 19:57:
>
>> oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at least 
>> Java 11.
>>
>> On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer wrote:
>>
>>> I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in 
>>> version 2024.1.24)
>>>
>>> On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 
>>> ma...@craig-mitchell.com wrote:
>>>
>>>> Ignore my post.  Just realised the doco uses net.ltgt.gwt.archetypes 
>>>> and not the springboot com.github.nalukit.archetype.
>>>>
>>>> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta 
>>>> stuff.
>>>>
>>>> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote:
>>>>
>>>>> I was going to suggest the GWT doco gets updated to use this, but I 
>>>>> see you already have!  
>>>>> https://www.gwtproject.org/gettingstarted-v2.html
>>>>>
>>>>> Excellent stuff!  
>>>>>
>>>>> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> both archetypes have been updated to the latest GWT (2.11.0) & Spring 
>>>>>> Boot version (3.2.2).
>>>>>> Happy generating ... 
>>>>>>
>>>>>> cu Frank
>>>>>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1:
>>>>>>
>>>>>>> Hi Grayson,
>>>>>>>
>>>>>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. 
>>>>>>> I'll try to take a look today.
>>>>>>>
>>>>>>> cu Frank
>>>>>>>
>>>>>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 
>>>>>>> UTC+1:
>>>>>>>
>>>>>>>> Hi Frank,
>>>>>>>>
>>>>>>>> Would you please also publish the new version for 
>>>>>>>> "modular-springboot-webapp" (the one that generates a gwt project with 
>>>>>>>> sample code)? The lastest verison of "modular-springboot-webapp" is 
>>>>>>>> still "
>>>>>>>> 2022.9.14 
>>>>>>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>"
>>>>>>>>  
>>>>>>>> which is more than a year old.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Grayson
>>>>>>>>
>>>>>>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Happy new year! I just released a new version of the 
>>>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The 
>>>>>>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 
>>>>>>>> 17) 
>>>>>>>> with GWT 2.10.0 multi module project. Happy coding!
>>>>>>>>
>>>>>>>> -- 
>> 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/0c06d897-5654-49d8-871a-f10d8ea2d171n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-web-toolkit/0c06d897-5654-49d8-871a-f10d8ea2d171n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/4574c03c-8a5f-44f3-9b4b-8cab305e491cn%40googlegroups.com.


Re: Create an executable JAR

2024-01-27 Thread Craig Mitchell
Apologies.  I've now realised I don't need to create an executable JAR.  I 
can just run the WAR directly, like this:
java -jar mywebapp-server/target/mywebapp.war

And I can tell Google App Engine to do the same in the app.yaml:
entrypoint: java -jar mywebapp.war

And woohoo!  GWT running in Google App 
Engine:  https://gae-gwt-412604.appspot.com/

On Sunday 28 January 2024 at 12:54:48 pm UTC+11 Craig Mitchell wrote:

> Hi,
>
> Using the SpringBoot archetype ( 
> https://github.com/NaluKit/gwt-maven-springboot-archetype ), I can happy 
> run mvn clean package and get a war file that has everything and runs 
> nicely on a web server.
>
> If I then modify mywebapp-server/pom.xml to have:
> jar 
> (instead of war)
>
> I then get an executable jar, which I can run:
> java -jar mywebapp-server/target/mywebapp.jar
>
> The executable JAR runs the embedded Tomcat server, which contains the 
> index.html + css (inside the mywebapp.jar in BOOT-INF\classes\public), 
> however, all the GWT files are 
> in BOOT-INF\lib\mywebapp-client-HEAD-SNAPSHOT.war) so it never sees them.  
> As a result, the app only shows the html, and nothing else works.
>
> Has anyone made a GWT app as an executable JAR?  Or any suggestions how to 
> do it?
>
> The reason I need an executable JAR, is because that's all Google App 
> Engine standard supports: 
> https://cloud.google.com/appengine/docs/standard/testing-and-deploying-your-app?tab=java
>
> Thanks in advance.
>

-- 
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/b209137d-862b-4efd-b232-7f9d5b08c12fn%40googlegroups.com.


Create an executable JAR

2024-01-27 Thread Craig Mitchell
Hi,

Using the SpringBoot archetype ( 
https://github.com/NaluKit/gwt-maven-springboot-archetype ), I can happy 
run mvn clean package and get a war file that has everything and runs 
nicely on a web server.

If I then modify mywebapp-server/pom.xml to have:
jar 
(instead of war)

I then get an executable jar, which I can run:
java -jar mywebapp-server/target/mywebapp.jar

The executable JAR runs the embedded Tomcat server, which contains the 
index.html + css (inside the mywebapp.jar in BOOT-INF\classes\public), 
however, all the GWT files are 
in BOOT-INF\lib\mywebapp-client-HEAD-SNAPSHOT.war) so it never sees them.  
As a result, the app only shows the html, and nothing else works.

Has anyone made a GWT app as an executable JAR?  Or any suggestions how to 
do it?

The reason I need an executable JAR, is because that's all Google App 
Engine standard 
supports: 
https://cloud.google.com/appengine/docs/standard/testing-and-deploying-your-app?tab=java

Thanks in advance.

-- 
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/0f35cedb-1e98-4c82-b9bc-704109abd598n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-01-24 Thread Craig Mitchell
Awesome stuff!  Thank you both.  Makes starting a new GWT project a breeze!

On Thursday 25 January 2024 at 6:08:27 am UTC+11 Frank Hossfeld wrote:

> Thanks!
>
> Thomas Broyer schrieb am Mittwoch, 24. Januar 2024 um 19:57:12 UTC+1:
>
>> oh, and GWT 2.11 with Jakarta Servlet and Jetty 11; so requiring at least 
>> Java 11.
>>
>> On Wednesday, January 24, 2024 at 7:55:33 PM UTC+1 Thomas Broyer wrote:
>>
>>> I updated modular-webapp (and modular-requestfactory) to GWT 2.11 (in 
>>> version 2024.1.24)
>>>
>>> On Wednesday, January 24, 2024 at 10:58:45 AM UTC+1 
>>> ma...@craig-mitchell.com wrote:
>>>
>>>> Ignore my post.  Just realised the doco uses net.ltgt.gwt.archetypes 
>>>> and not the springboot com.github.nalukit.archetype.
>>>>
>>>> And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta 
>>>> stuff.
>>>>
>>>> On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote:
>>>>
>>>>> I was going to suggest the GWT doco gets updated to use this, but I 
>>>>> see you already have!  
>>>>> https://www.gwtproject.org/gettingstarted-v2.html
>>>>>
>>>>> Excellent stuff!  
>>>>>
>>>>> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> both archetypes have been updated to the latest GWT (2.11.0) & Spring 
>>>>>> Boot version (3.2.2).
>>>>>> Happy generating ... 
>>>>>>
>>>>>> cu Frank
>>>>>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1:
>>>>>>
>>>>>>> Hi Grayson,
>>>>>>>
>>>>>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. 
>>>>>>> I'll try to take a look today.
>>>>>>>
>>>>>>> cu Frank
>>>>>>>
>>>>>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 
>>>>>>> UTC+1:
>>>>>>>
>>>>>>>> Hi Frank,
>>>>>>>>
>>>>>>>> Would you please also publish the new version for 
>>>>>>>> "modular-springboot-webapp" (the one that generates a gwt project with 
>>>>>>>> sample code)? The lastest verison of "modular-springboot-webapp" is 
>>>>>>>> still "
>>>>>>>> 2022.9.14 
>>>>>>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>"
>>>>>>>>  
>>>>>>>> which is more than a year old.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Grayson
>>>>>>>>
>>>>>>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Happy new year! I just released a new version of the 
>>>>>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The 
>>>>>>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 
>>>>>>>> 17) 
>>>>>>>> with GWT 2.10.0 multi module project. Happy coding!
>>>>>>>>
>>>>>>>>

-- 
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/41cd4bba-4cab-4883-8864-7c37bff163ben%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-01-24 Thread Craig Mitchell
Ignore my post.  Just realised the doco uses net.ltgt.gwt.archetypes and 
not the springboot com.github.nalukit.archetype.

And thus, it's still on GWT 2.10.0, and not 2.11.0 with the jakarta stuff.

On Wednesday 24 January 2024 at 8:39:07 pm UTC+11 Craig Mitchell wrote:

> I was going to suggest the GWT doco gets updated to use this, but I see 
> you already have!  https://www.gwtproject.org/gettingstarted-v2.html
>
> Excellent stuff!  
>
> On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote:
>
>> Hi,
>>
>> both archetypes have been updated to the latest GWT (2.11.0) & Spring 
>> Boot version (3.2.2).
>> Happy generating ... 
>>
>> cu Frank
>> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1:
>>
>>> Hi Grayson,
>>>
>>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. I'll 
>>> try to take a look today.
>>>
>>> cu Frank
>>>
>>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 UTC+1:
>>>
>>>> Hi Frank,
>>>>
>>>> Would you please also publish the new version for 
>>>> "modular-springboot-webapp" (the one that generates a gwt project with 
>>>> sample code)? The lastest verison of "modular-springboot-webapp" is still "
>>>> 2022.9.14 
>>>> <https://mvnrepository.com/artifact/com.github.nalukit.archetype/modular-springboot-webapp/2022.9.14>"
>>>>  
>>>> which is more than a year old.
>>>>
>>>> Thanks,
>>>> Grayson
>>>>
>>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote:
>>>>
>>>> Happy new year! I just released a new version of the 
>>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The 
>>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) 
>>>> with GWT 2.10.0 multi module project. Happy coding!
>>>>
>>>>

-- 
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/29f805cb-ac40-4bd5-86f3-0cd5d78c1d83n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-01-24 Thread Craig Mitchell
I was going to suggest the GWT doco gets updated to use this, but I see you 
already have!  https://www.gwtproject.org/gettingstarted-v2.html

Excellent stuff!  

On Tuesday 23 January 2024 at 11:05:48 pm UTC+11 Frank Hossfeld wrote:

> Hi,
>
> both archetypes have been updated to the latest GWT (2.11.0) & Spring Boot 
> version (3.2.2).
> Happy generating ... 
>
> cu Frank
> Frank Hossfeld schrieb am Montag, 22. Januar 2024 um 14:29:41 UTC+1:
>
>> Hi Grayson,
>>
>> it's on my To-Do-list. I had to wait until GWT 2.11.0 is released. I'll 
>> try to take a look today.
>>
>> cu Frank
>>
>> grays...@gmail.com schrieb am Montag, 22. Januar 2024 um 07:47:52 UTC+1:
>>
>>> Hi Frank,
>>>
>>> Would you please also publish the new version for 
>>> "modular-springboot-webapp" (the one that generates a gwt project with 
>>> sample code)? The lastest verison of "modular-springboot-webapp" is still "
>>> 2022.9.14 
>>> "
>>>  
>>> which is more than a year old.
>>>
>>> Thanks,
>>> Grayson
>>>
>>> On Tuesday, January 2, 2024 at 4:46:30 PM UTC+7 Frank Hossfeld wrote:
>>>
>>> Happy new year! I just released a new version of the 
>>> https://github.com/NaluKit/gwt-maven-springboot-archetype. The 
>>> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) 
>>> with GWT 2.10.0 multi module project. Happy coding!
>>>
>>>

-- 
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/5b539b3c-18fc-4c3b-a573-a8a48c1bcf3an%40googlegroups.com.


Re: The GWT application hangs on the loading screen

2024-01-13 Thread Craig Mitchell
I use a servlet filter to tell the browser not to cache the nocache files:

public class ServletFilter implements Filter {
  private static final String NO_CACHE = ".nocache.js";

  @Override
  public void doFilter(ServletRequest request, ServletResponse response, 
FilterChain 
chain) throws IOException, ServletException {
String requestURI = ((HttpServletRequest)request).getRequestURI();

// Don't cache the nocache
if (requestURI.endsWith(NO_CACHE)) {
  setNoCache((HttpServletResponse)response);
}
chain.doFilter(request, response);
  }

  private void setNoCache(HttpServletResponse httpResponse) {
Date now = new Date();
httpResponse.setDateHeader("Date", now.getTime());
httpResponse.setDateHeader("Expires", now.getTime() - 8640L);
httpResponse.setHeader("Pragma", "no-cache");
httpResponse.setHeader("cache-control", "public, max-age=0, 
must-revalidate");
  }
}

On Saturday 13 January 2024 at 2:54:08 am UTC+11 Jeff Hill wrote:

> There may have been some Chrome updates in the last few months; 
> occasionally, I must hard refresh to get the latest code from nocache.js.  
> (That did not happen in  years past)
>
> Anyway, I always check in Developer Tools in Chrome to make sure there are 
> no errors in the "Console" and all the necessary files are being loaded in 
> the "Network" tab.
> On Thursday, January 11, 2024 at 6:42:14 AM UTC-7 Frank Hossfeld wrote:
>
>> Check if the nochache.js gets loaded at a applicaiton staert or if it got 
>> a 404. In this case something with the URI is not ok.
>>
>> Antonio Capone schrieb am Donnerstag, 11. Januar 2024 um 10:56:55 UTC+1:
>>
>>> Hi all. I deployed an app using GWT on Cloud. It's deployed and working, 
>>> but when you log in, the browser window just says "Loading" and seems to 
>>> hang indefinitely. Works fine locally in Eclipse.
>>> Has this ever happened to you? Is there anyone who can help me 
>>> understand why this happens?
>>> Many 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/76e39f7a-8df0-4a7d-9d81-e14467b3764an%40googlegroups.com.


Re: Announcing GWT 2.10.1 and 2.11 releases

2024-01-13 Thread Craig Mitchell
Thank you Colin!  You're spot on, found 
it:  
https://mvnrepository.com/artifact/org.gwtproject/gwt-servlet-jakarta/2.11.0

> *Note that this is not compatible with running your jakarta-servlet app 
inside dev mode, but you will need to run your own server separately from 
dev mode. *

Thanks again.  Yep, I'm (now) running with SpringBoot 3 with Embedded 
Tomcat 10.

Cheers.

On Sunday 14 January 2024 at 1:12:03 pm UTC+11 Colin Alworth wrote:

> Craig, you’ll need to change to the -jakarta artifacts. That is, for 
> RemoteServiceServlet, instead of gwt-servlet.jar, use 
> gwt-servlet-jakarta.jar, and the class is in the .rpc.jakarta package to 
> ensure there is no possibility of referencing the wrong type. Change both 
> the jar and your imports to use it. 
>
> Note that this is not compatible with running your jakarta-servlet app 
> inside dev mode, but you will need to run your own server separately from 
> dev mode. 
>
> -- 
>   Colin Alworth
>   co...@colinalworth.com
>
>
> On Sat, Jan 13, 2024, at 7:54 PM, Craig Mitchell wrote:
>
> Awesome!  Thank you GWT team!
>
> Regarding:
>
> *> Added release artifacts for jakarta.servlet packages for both 
> RequestFactory and GWT-RPC.*
>
> When I look at com.google.gwt.user.server.rpc.RemoteServiceServlet, it's 
> still using javax.servlet.http.HttpServlet.  So calls 
> like getThreadLocalRequest() return javax.servlet.http.HttpServletRequest 
> and not jakarta.servlet.http.HttpServletRequest.  Is there another version 
> of RemoteServiceServlet I can use that uses the jakarta classes?
>
> Thanks.
> On Friday 12 January 2024 at 1:28:05 am UTC+11 Filipe Sousa wrote:
>
> 
>
> On Tuesday, January 9, 2024 at 9:36:08 PM UTC Colin Alworth wrote:
>
> I'm excited to announce the release of 2.10.1 and 2.11.0! This is our 
> second release under the new groupId, be sure when you update to change 
> away from "com.google.gwt", as it will not get more updates.
>
> If you use GWT-RPC and JPA/JDO annotations in your project, we strongly 
> suggest updating at least to 2.10.1 as soon as possible. To ensure that 
> vulnerable projects are aware of any problem, compile warnings will be 
> emitted if a problem is detected, and the server will default to not 
> allowing any vulnerable RemoteService instances. See 
> https://github.com/gwtproject/gwt/issues/9709 for information on the 
> issue, how we're responding to it, and how any additional follow-up might 
> look.
>
> Other highlights:
>
>- Transitioned to GitHub pull requests for new contributions, with 
>nightly builds running on GitHub Actions.
>- Added release artifacts for jakarta.servlet packages for both 
>RequestFactory and GWT-RPC.
>- Tested support for running on Java 21. This is likely to be the 
>final minor release series to support running on Java 8.
>- Updated JRE emulation to support Java 11 for Collections, streams, 
>and more.
>
> See https://github.com/gwtproject/gwt/releases/tag/2.11.0 or 
> https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0 for 
> complete release notes.
>
> This release wouldn't have been possible without help from so many 
> contributors, including developers, testers, and sponsors. A short list of 
> the teams and individuals that directly brought us this release: Juan Pablo 
> Gardella, Rocco De Angelis, Frank Hossfeld, Manfred Tremmel, Jim Douglas, 
> Zbynek Konecny, Piotr Lewandowski, Axel Uhl, Thomas Broyer, Filipe Sousa, 
> Sandra Parsick, Jens Nehlmeier, Schubec GmbH, Tom Sawyer Software, 
> Insurance Insight Inc. Join us on the issue tracker 
> <https://github.com/gwtproject/gwt/issues> or at our OpenCollective page 
> <https://opencollective.com/gwt-project> to help make future releases 
> possible.
>
>
> -- 
> 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/cc9f18b3-1bfd-43f0-b2bc-e694a04f6fb5n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/google-web-toolkit/cc9f18b3-1bfd-43f0-b2bc-e694a04f6fb5n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
>

-- 
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/2b4f5616-d5a3-45aa-b248-c2defddf056bn%40googlegroups.com.


Re: Announcing GWT 2.10.1 and 2.11 releases

2024-01-13 Thread Craig Mitchell
Awesome!  Thank you GWT team!

Regarding:

*> Added release artifacts for jakarta.servlet packages for both 
RequestFactory and GWT-RPC.*

When I look at com.google.gwt.user.server.rpc.RemoteServiceServlet, it's 
still using javax.servlet.http.HttpServlet.  So calls 
like getThreadLocalRequest() return javax.servlet.http.HttpServletRequest 
and not jakarta.servlet.http.HttpServletRequest.  Is there another version 
of RemoteServiceServlet I can use that uses the jakarta classes?

Thanks.

On Friday 12 January 2024 at 1:28:05 am UTC+11 Filipe Sousa wrote:

> 
>
> On Tuesday, January 9, 2024 at 9:36:08 PM UTC Colin Alworth wrote:
>
>> I'm excited to announce the release of 2.10.1 and 2.11.0! This is our 
>> second release under the new groupId, be sure when you update to change 
>> away from "com.google.gwt", as it will not get more updates.
>>
>> If you use GWT-RPC and JPA/JDO annotations in your project, we strongly 
>> suggest updating at least to 2.10.1 as soon as possible. To ensure that 
>> vulnerable projects are aware of any problem, compile warnings will be 
>> emitted if a problem is detected, and the server will default to not 
>> allowing any vulnerable RemoteService instances. See 
>> https://github.com/gwtproject/gwt/issues/9709 for information on the 
>> issue, how we're responding to it, and how any additional follow-up might 
>> look.
>>
>> Other highlights:
>>
>>- Transitioned to GitHub pull requests for new contributions, with 
>>nightly builds running on GitHub Actions.
>>- Added release artifacts for jakarta.servlet packages for both 
>>RequestFactory and GWT-RPC.
>>- Tested support for running on Java 21. This is likely to be the 
>>final minor release series to support running on Java 8.
>>- Updated JRE emulation to support Java 11 for Collections, streams, 
>>and more.
>>
>> See https://github.com/gwtproject/gwt/releases/tag/2.11.0 or 
>> https://www.gwtproject.org/release-notes.html#Release_Notes_2_11_0 for 
>> complete release notes.
>>
>> This release wouldn't have been possible without help from so many 
>> contributors, including developers, testers, and sponsors. A short list of 
>> the teams and individuals that directly brought us this release: Juan Pablo 
>> Gardella, Rocco De Angelis, Frank Hossfeld, Manfred Tremmel, Jim Douglas, 
>> Zbynek Konecny, Piotr Lewandowski, Axel Uhl, Thomas Broyer, Filipe Sousa, 
>> Sandra Parsick, Jens Nehlmeier, Schubec GmbH, Tom Sawyer Software, 
>> Insurance Insight Inc. Join us on the issue tracker 
>>  or at our OpenCollective page 
>>  to help make future releases 
>> possible.
>>
>

-- 
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/cc9f18b3-1bfd-43f0-b2bc-e694a04f6fb5n%40googlegroups.com.


Re: gwt-maven-springboot-archetype updated ...

2024-01-05 Thread Craig Mitchell
Thank you!  I was struggling to get Springboot to work with GWT, and this 
did it beautifully!

One thing I messed up:

> Define value for property 'package' teamdrift: : jar

I thought it meant how did I want to package the output, as I need an 
executable jar, not a war.  But it meant what did I want my Java package to 
be.  lol.

One small error, the top level pom.xml has 3 blank lines between every XML 
line.  Just like 
this:  
https://github.com/NaluKit/gwt-maven-springboot-archetype/blob/main/clean-modular-springboot-webapp/src/test/resources/projects/basic-webapp/reference/pom.xml
  
Easy to fix up, so only a very minor error.

Thank you for making this awesome tool!

On Tuesday 2 January 2024 at 8:46:30 pm UTC+11 Frank Hossfeld wrote:

> Happy new year! I just released a new version of the 
> https://github.com/NaluKit/gwt-maven-springboot-archetype. The 
> clean-modular-springboot-webapp generates now a Spring Boot 3 (Java 17) 
> with GWT 2.10.0 multi module project. Happy coding!
>

-- 
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/df5b13e2-8bf0-4586-ac16-3b103464c54cn%40googlegroups.com.


Re: Deploy to Google App Engine (GAE)

2023-12-25 Thread Craig Mitchell
Odd, my message was deleted.  Maybe it was too boring.  :-D

The highlights:

   - I'm not sure if you get a Jetty server bundled or not if you use the 
   legacy bundled services.  The documentation is a little ambiguous to me.
   - You do get a stand alone server "dev server" that you can deploy a war 
   to.  Great for final testing, but it's unclear if you'll be able to debug 
   on it.
   - Your static files worked because the legacy version allows a war file, 
   and you have the maven-war-plugin in your POM.
   - If I switch to SpringBoot, I'll move my static files to either 
   a /public or /static directory.

Personally, I'm going to skip the legacy bundled services, and just use the 
second-generation Java runtime with my own web server.

Cheers!

On Monday 25 December 2023 at 3:48:23 am UTC+11 tim_mac...@yahoo.co.uk 
wrote:

> Looks like Cloud CLI provides a dev server if  using the legacy bundled 
> services (App Engine API JAR)?
>  
> https://cloud.google.com/appengine/docs/standard/java-gen2/services/access
> If you are using the legacy bundled services, the second-generation Java 
> runtimes provide the Jetty web-serving framework.
>
> https://cloud.google.com/appengine/migration-center/standard/migrate-to-second-gen/java-differences#framework_flexibility
> The Google Cloud CLI for Java includes a local development server for 
> testing your application on your computer. The local development server 
> emulates the App Engine Java runtime environment and all of its services, 
> including Datastore.
>
> https://cloud.google.com/appengine/docs/standard/tools/using-local-server?tab=java
> What do you think ?
>
> Re. static files: in my setup appengine:deploy at base directory server 
> project deploys  SNAPSHOT.war. 
> Static files in \src\main\webapp end up in its root directory. 
> This:  
> https://stackoverflow.com/questions/71673962/while-running-as-a-jar-application-not-able-to-access-static-files-in-springboo
> says in the case of a JAR-file, src/main/webapp has no special meaning 
> and goes on about jar directories that work with Springboot.
>
>
>

-- 
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/1d958b8c-9fee-4c7f-9387-cf7aca3a6e22n%40googlegroups.com.


Re: Deploy to Google App Engine (GAE)

2023-12-23 Thread Craig Mitchell
Thanks again Tim!



*> Afaik gwt:devmode is launching  a GWT Jetty, rather than the GAE Jetty.> 
The latter requires appengine:run*

This is no longer an option.  appengine:run no longer works with Java17.  
You have to provide your own web server.  
See 
https://cloud.google.com/appengine/migration-center/standard/migrate-to-second-gen/java-differences#key-differences

I'm still trying to figure out if I can just use the bundled GWT Jetty 
server, or do I include my own Jetty / Embedded Tomcat / ... server.

*> As you say: for IDE debugging: we need a Remote Java Application & 
jvmFlags, discussed at length here:*

Thank you!  Those options work much better.  In IntelliJ, I've now setup a 
"compound" launcher that launches both the gwt:devmode and the remote JVM 
debug at the same time.





*> With this setup the dev GAE server uses the cloud datastore (& blobstore 
I think).> To fix, in the gloud CLI app run:> gcloud components install 
cloud-datastore-emulator> before launch of GAE server run:> gcloud beta 
emulators datastore start --project='prjname' --host-port=localhost:8081 
--data-dir=C:\Users\tim_m\eclipse-workspace\Snptn\Snptn-server\src\main\webapp*

I tried this, and the emulator starts no problem.  However, I still get the 
"No API environment is registered for this thread.".

I might switch to use SpringBoot, then it'll use its Jetty server, and I'll 
switch away from the GWT Jetty server (and just use the GWT code server), 
and then it'll hopefully magically work.


*> Re  copying src/main/webapp files to the target folder: afaik that is 
done by> maven-jar-plugin jar goal (jar:jar) which is invoked by calling 
package (phase)*

I figured it out.  It's because GAE wants an executable JAR 
( 
https://cloud.google.com/appengine/docs/standard/testing-and-deploying-your-app?tab=java#other_deployment_options
 
), however, the src/main/webapp files are only copied when creating a war 
with the maven-war-plugin.

I'll need to figure out how to include the static files with an executable 
JAR, or if I switch to SpringBoot, I think SpringBoot handles this for me.

*> Btw I often read that the tbroyer multi-project pattern is better 
because it keeps server & client dependencies separated, but its a more 
complex pattern.*

I might end up changing to this structure.  I wanted to keep it as simple 
as possible, as my project isn't complicated, but might still be a better 
option.

Cheers!

On Sunday 24 December 2023 at 5:28:35 am UTC+11 tim_mac...@yahoo.co.uk 
wrote:

> Afaik gwt:devmode is launching  a GWT Jetty, rather than the GAE Jetty.
> The latter requires appengine:run 
> with a launch profile env property & name
> appengine:run -Denv=haslistener
>
> As you say: for IDE debugging: we need a Remote Java Application & 
> jvmFlags, discussed at length here:
>
> https://stackoverflow.com/questions/138511/what-are-java-command-line-options-to-set-to-allow-jvm-to-be-remotely-debugged
> someone says:
> For Java 5 and above, run it with:
> -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=1044
> rather than
> Xrunjdwp:transport=dt_socket,address=1044,server=y,suspend=n
> I havent tried this yet.
>
> With this setup the dev GAE server uses the cloud datastore (& blobstore I 
> think).
> To fix, in the gloud CLI app run:
> gcloud components install cloud-datastore-emulator
> If you didnt install beta commands, it will prompt for that.
> cloud-datastore-emulator 2.3.1
> before launch of GAE server run:
> gcloud beta emulators datastore start --project='prjname' 
> --host-port=localhost:8081 
> --data-dir=C:\Users\tim_m\eclipse-workspace\Snptn\Snptn-server\src\main\webapp
>
> Set environment variable in the eclipse launch to attach this 
> DATASTORE_EMULATOR environment 
> Last time I looked: the local datastore viewer cant show objectify 
> entities, only blobstore files.
>
> Re  copying src/main/webapp files to the target folder: afaik that is done 
> by 
> maven-jar-plugin jar goal (jar:jar) which is invoked by calling package 
> (phase)
>  
> Btw I often read that the tbroyer multi-project pattern is better because 
> it keeps server & client dependencies separated, but its a more complex 
> pattern.
> Re the poms I attached here: 1 problem is inconsistencies in:
> 
> 
>
> 
> 
>
> On Saturday, December 23, 2023 at 7:35:42 AM UTC Craig Mitchell wrote:
>
>> Managed to get server debugging working by adding:
>>
>> -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005> jvmArg>
>>
>> to the gwt-maven-plugin.
>>
>> And then creating a Remote JVM Debug launcher in IntelliJ (on port 5005), 
>> that I run after running gwt:devmode.
>>
>> I'm surprised IntelliJ can't just automaticall

Re: Deploy to Google App Engine (GAE)

2023-12-22 Thread Craig Mitchell
Managed to get server debugging working by adding:

-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005

to the gwt-maven-plugin.

And then creating a Remote JVM Debug launcher in IntelliJ (on port 5005), 
that I run after running gwt:devmode.

I'm surprised IntelliJ can't just automatically attach to the running 
server.  Is this what everyone does that uses gwt:devmode?

On Saturday 23 December 2023 at 3:28:36 pm UTC+11 Craig Mitchell wrote:

> Thanks Tim!  Looking at your POM files, I see I missed adding:
>
>  >${project.build.directory}/${project.artifactId}-${project.version}/WEB-INF/classes outputDirectory>
>
> I also needed to:
>
>- Convert all my servlets to @WebServlet (as the GWT Jetty server 
>didn't pick up my web.xml like the GAE server used to).
>- Give the GWT plugin the JVM arg 
>"--add-opens java.base/java.lang=ALL-UNNAMED" for execeptions to be 
>returned to the client.
>
> Strangely, Maven isn't copying my src/main/webapp files to the target 
> folder, so I'm doing that manually with the maven-resources-plugin.
>
> So now GWT starts, dev compiles (including source maps), and runs 
> beautifully, including RPC calls.  Java17 runtime with a Java11 source 
> level.  Happy days!  New POM attached.
>
> I've switched from using Eclipse to IntelliJ (because I no longer will be 
> using any of the Eclipse plugins, and wanted a fresh start).  However, 
> debugging my server never hits the breakpoints.
>
> Do you use IntelliJ, do we need any special params to enable debug?
>
> [image: debug.png]
>
> I'm yet to get Google App Engine to work.  When I try to access any of the 
> GAE calls, I just get "No API environment is registered for this thread.".  
> I think I need to setup the enviroment somehow now I no longer have a GAE 
> server.
>
> Cheers!
>
> On Friday 22 December 2023 at 4:41:07 am UTC+11 tim_mac...@yahoo.co.uk 
> wrote:
>
>> These are my current poms, based on the tbroyer archetype.
>> Probably best to look at the latter first if youre not familiar with it.
>>
>> The launch is configured in the server pom:
>>
>> 
>>   env-dev-gae1
>>   
>>   
>>   env
>>   haslistener
>> ...
>>   
>> 
>>   ...
>>
>>   com.google.cloud.tools
>>   appengine-maven-plugin
>>
>> A version of Jetty is attached by the appengine-maven-plugin config here 
>> (afaik)
>> The eclipse launch goal is: appengine:run -Denv=haslistener
>>
>> Re GWT 2.10 : it can use JRE 17 but can only compile Java 11 source, iirc.
>>
>> Poms are a bit messy but should help if you want to take this approach
>>
>> On Thursday, December 21, 2023 at 11:36:51 AM UTC Craig Mitchell wrote:
>>
>>> Forgot to mention.  My target is Java 17, but my source is Java 1.8.
>>>
>>> So:
>>> 
>>> 1.8
>>> 17
>>> 
>>>
>>> And:
>>> 
>>> 
>>> 
>>> org.apache.maven.plugins
>>> maven-compiler-plugin
>>> 3.11.0
>>> 
>>> ${maven.compiler.source}
>>> ${maven.compiler.target}
>>> 
>>> 
>>> 
>>> org.apache.maven.plugins
>>> maven-resources-plugin
>>> 3.3.1
>>> 
>>> 
>>> 
>>>
>>> I've attached my current POM (which isn't working, so don't copy it ), 
>>> but if you can see my mistake, please let me know.
>>>
>>> Thanks again!
>>> On Thursday 21 December 2023 at 10:27:01 pm UTC+11 Craig Mitchell wrote:
>>>
>>>> Hi Tim,
>>>>
>>>> I thought GWT 2.10.0 supported Java17.  From the release notes:   
>>>> https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
>>>> *Tested support for running on Java 17, dropped remaining support for 
>>>> running on Java 7.*
>>>>
>>>> I'm also using appengine-maven-plugin 2.5.0.
>>>> 
>>>> com.google.cloud.tools
>>>> appengine-maven-plugin
>>>> 2.5.0
>>>> 
>>>> headtoheaddrifting
>>>> GCLOUD_CONFIG
>>>> 
>>>> 
>>>>
>>>> Along with GWT plugin:
>>>> 
>>>> net.ltgt.gwt.maven
>>>> gwt-maven-plugin
>>>> 1.1.0
>>>> true
>>>> 
>>>> team.drift.DriftTeam
>>>> dt
>>>> gwt-lib
>>>> ${project.build.directory}/gwt/launcherDir
>>>> ${project.build.

Re: Deploy to Google App Engine (GAE)

2023-12-22 Thread Craig Mitchell
Thanks Tim!  Looking at your POM files, I see I missed adding:

${project.build.directory}/${project.artifactId}-${project.version}/WEB-INF/classes

I also needed to:

   - Convert all my servlets to @WebServlet (as the GWT Jetty server didn't 
   pick up my web.xml like the GAE server used to).
   - Give the GWT plugin the JVM arg 
   "--add-opens java.base/java.lang=ALL-UNNAMED" for execeptions to be 
   returned to the client.

Strangely, Maven isn't copying my src/main/webapp files to the target 
folder, so I'm doing that manually with the maven-resources-plugin.

So now GWT starts, dev compiles (including source maps), and runs 
beautifully, including RPC calls.  Java17 runtime with a Java11 source 
level.  Happy days!  New POM attached.

I've switched from using Eclipse to IntelliJ (because I no longer will be 
using any of the Eclipse plugins, and wanted a fresh start).  However, 
debugging my server never hits the breakpoints.

Do you use IntelliJ, do we need any special params to enable debug?

[image: debug.png]

I'm yet to get Google App Engine to work.  When I try to access any of the 
GAE calls, I just get "No API environment is registered for this thread.".  
I think I need to setup the enviroment somehow now I no longer have a GAE 
server.

Cheers!

On Friday 22 December 2023 at 4:41:07 am UTC+11 tim_mac...@yahoo.co.uk 
wrote:

> These are my current poms, based on the tbroyer archetype.
> Probably best to look at the latter first if youre not familiar with it.
>
> The launch is configured in the server pom:
>
> 
>   env-dev-gae1
>   
>   
>   env
>   haslistener
> ...
>   
> 
>   ...
>
>   com.google.cloud.tools
>   appengine-maven-plugin
>
> A version of Jetty is attached by the appengine-maven-plugin config here 
> (afaik)
> The eclipse launch goal is: appengine:run -Denv=haslistener
>
> Re GWT 2.10 : it can use JRE 17 but can only compile Java 11 source, iirc.
>
> Poms are a bit messy but should help if you want to take this approach
>
> On Thursday, December 21, 2023 at 11:36:51 AM UTC Craig Mitchell wrote:
>
>> Forgot to mention.  My target is Java 17, but my source is Java 1.8.
>>
>> So:
>> 
>> 1.8
>> 17
>> 
>>
>> And:
>> 
>> 
>> 
>> org.apache.maven.plugins
>> maven-compiler-plugin
>> 3.11.0
>> 
>> ${maven.compiler.source}
>> ${maven.compiler.target}
>> 
>> 
>> 
>> org.apache.maven.plugins
>> maven-resources-plugin
>> 3.3.1
>> 
>> 
>> 
>>
>> I've attached my current POM (which isn't working, so don't copy it ), 
>> but if you can see my mistake, please let me know.
>>
>> Thanks again!
>> On Thursday 21 December 2023 at 10:27:01 pm UTC+11 Craig Mitchell wrote:
>>
>>> Hi Tim,
>>>
>>> I thought GWT 2.10.0 supported Java17.  From the release notes:   
>>> https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
>>> *Tested support for running on Java 17, dropped remaining support for 
>>> running on Java 7.*
>>>
>>> I'm also using appengine-maven-plugin 2.5.0.
>>> 
>>> com.google.cloud.tools
>>> appengine-maven-plugin
>>> 2.5.0
>>> 
>>> headtoheaddrifting
>>> GCLOUD_CONFIG
>>> 
>>> 
>>>
>>> Along with GWT plugin:
>>> 
>>> net.ltgt.gwt.maven
>>> gwt-maven-plugin
>>> 1.1.0
>>> true
>>> 
>>> team.drift.DriftTeam
>>> dt
>>> gwt-lib
>>> ${project.build.directory}/gwt/launcherDir
>>> ${project.build.directory}/drift-team-1.0-SNAPSHOT
>>> 
>>> index.html
>>> 
>>> 
>>> 
>>>
>>> Running: "mvn gwt:devmode" I can get it to start the Jetty server and 
>>> GWT code server.  It finds my project, but currently, when opening the 
>>> browser it says:
>>> HTTP ERROR 503 Service Unavailable
>>> URI: /index.html
>>> STATUS: 503
>>> MESSAGE: Service Unavailable
>>> SERVLET: -
>>>
>>> I put my web assets in  src/main/webapp  and I don't think it's seeing 
>>> them.  Plus I don't think it's seeing my web.xml that's in 
>>>  src/main/webapp/WEB-INF/web.xml
>>>
>>> Maybe they need to be copied to the target directory or somewhere, or 
>>> the GWT plugin pointed to where they are somehow.  Not sure.  Any help is 
>>> greatly appreaciated.
>>>
>>>
>>> On Thursday 21 December 2023 at 4:06:46 am UTC

Re: Deploy to Google App Engine (GAE)

2023-12-21 Thread Craig Mitchell
Forgot to mention.  My target is Java 17, but my source is Java 1.8.

So:

1.8
17


And:



org.apache.maven.plugins
maven-compiler-plugin
3.11.0

${maven.compiler.source}
${maven.compiler.target}



org.apache.maven.plugins
maven-resources-plugin
3.3.1




I've attached my current POM (which isn't working, so don't copy it ), 
but if you can see my mistake, please let me know.

Thanks again!
On Thursday 21 December 2023 at 10:27:01 pm UTC+11 Craig Mitchell wrote:

> Hi Tim,
>
> I thought GWT 2.10.0 supported Java17.  From the release notes:   
> https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
> *Tested support for running on Java 17, dropped remaining support for 
> running on Java 7.*
>
> I'm also using appengine-maven-plugin 2.5.0.
> 
> com.google.cloud.tools
> appengine-maven-plugin
> 2.5.0
> 
> headtoheaddrifting
> GCLOUD_CONFIG
> 
> 
>
> Along with GWT plugin:
> 
> net.ltgt.gwt.maven
> gwt-maven-plugin
> 1.1.0
> true
> 
> team.drift.DriftTeam
> dt
> gwt-lib
> ${project.build.directory}/gwt/launcherDir
> ${project.build.directory}/drift-team-1.0-SNAPSHOT
> 
> index.html
> 
> 
> 
>
> Running: "mvn gwt:devmode" I can get it to start the Jetty server and 
> GWT code server.  It finds my project, but currently, when opening the 
> browser it says:
> HTTP ERROR 503 Service Unavailable
> URI: /index.html
> STATUS: 503
> MESSAGE: Service Unavailable
> SERVLET: -
>
> I put my web assets in  src/main/webapp  and I don't think it's seeing 
> them.  Plus I don't think it's seeing my web.xml that's in 
>  src/main/webapp/WEB-INF/web.xml
>
> Maybe they need to be copied to the target directory or somewhere, or the 
> GWT plugin pointed to where they are somehow.  Not sure.  Any help is 
> greatly appreaciated.
>
>
> On Thursday 21 December 2023 at 4:06:46 am UTC+11 tim_mac...@yahoo.co.uk 
> wrote:
>
>> I havent tried raising the Java level yet, its still  JavaSE-1.8. 
>> Got as far as using latest versions:
>> JDK 21
>> gcloud CLI app & cloudSdkVersion  457.0.0 
>> appengine-maven-plugin 2.5.0
>>
>> To get it to run, so far:
>> 1 I had to remove all DOCTYPE declarations in xml files in the server 
>> project (new restrictions on DTD)
>> 2 appengine-maven-plugin 2.5.0 requires:
>> 
>> 
>> --add-opens
>> java.base/java.util=ALL-UNNAMED
>> This stops 500 Server Error which I've not seen before:
>> GCLOUD: java.lang.reflect.InaccessibleObjectException:
>> Unable to make field accessible: module java.base does not "opens 
>> java.util" to unnamed module @2c95ac9e
>>
>> So Craig, you say with Java17 on GAE, there isn't a web server included 
>> anymore.
>> So this has to be defined somewhere in  appengine-maven-plugin ?
>> The minimum level to avoid being shut down on GAE standard is >8
>> & 11 is the max for GWT, so that would seem do for now, why Java 17  ?
>>
>> On Wednesday, December 20, 2023 at 4:46:03 AM UTC Craig Mitchell wrote:
>>
>>> No worries not posting the POMs Tim.
>>>
>>> The bit I'm struggling with, the old Java 8 version had its own GAE 
>>> server.  So I would run that, and a GWT Code Server.  Easy!
>>>
>>> *btw:* I'm talking about GAE Standard.  GAE Flexible you can do 
>>> whatever you want, but that's more work and more expensive.
>>>
>>> Now with the upgrade to Java17 on GAE, there isn't a web server included 
>>> anymore.  It's up to you to supply one.  I would assume when you deploy it, 
>>> it doesn't actually use your server, but what setup is GAE expecting for 
>>> the deploy?
>>>
>>> I see there is a SpringBoot GAE example, so it might be easier to use 
>>> that, and get GWT to work with SpringBoot.  Not sure.  Very interested to 
>>> hear what you're doing.
>>>
>>> Thanks!
>>>
>>> On Wednesday 20 December 2023 at 1:51:55 pm UTC+11 
>>> tim_mac...@yahoo.co.uk wrote:
>>>
>>>> For some years I've been deploying GWT 2.8.2 to GAE with Maven & Google 
>>>> Cloud Tools. 
>>>> I now find GAE is not supporting Java 8 after January, so currently 
>>>> upgrading (rather slowly). 
>>>> There are 4 long POM files,  probably better to mail them then post a 
>>>> distilled version here ?
>>>>
>>>> On Sunday, December 17, 2023 at 5:20:56 AM UTC Craig Mitchell wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> The instructi

Re: Deploy to Google App Engine (GAE)

2023-12-21 Thread Craig Mitchell
Hi Tim,

I thought GWT 2.10.0 supported Java17.  From the release notes:   
https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
*Tested support for running on Java 17, dropped remaining support for 
running on Java 7.*

I'm also using appengine-maven-plugin 2.5.0.

com.google.cloud.tools
appengine-maven-plugin
2.5.0

headtoheaddrifting
GCLOUD_CONFIG



Along with GWT plugin:

net.ltgt.gwt.maven
gwt-maven-plugin
1.1.0
true

team.drift.DriftTeam
dt
gwt-lib
${project.build.directory}/gwt/launcherDir
${project.build.directory}/drift-team-1.0-SNAPSHOT

index.html




Running: "mvn gwt:devmode" I can get it to start the Jetty server and 
GWT code server.  It finds my project, but currently, when opening the 
browser it says:
HTTP ERROR 503 Service Unavailable
URI: /index.html
STATUS: 503
MESSAGE: Service Unavailable
SERVLET: -

I put my web assets in  src/main/webapp  and I don't think it's seeing 
them.  Plus I don't think it's seeing my web.xml that's in 
 src/main/webapp/WEB-INF/web.xml

Maybe they need to be copied to the target directory or somewhere, or the 
GWT plugin pointed to where they are somehow.  Not sure.  Any help is 
greatly appreaciated.


On Thursday 21 December 2023 at 4:06:46 am UTC+11 tim_mac...@yahoo.co.uk 
wrote:

> I havent tried raising the Java level yet, its still  JavaSE-1.8. 
> Got as far as using latest versions:
> JDK 21
> gcloud CLI app & cloudSdkVersion  457.0.0 
> appengine-maven-plugin 2.5.0
>
> To get it to run, so far:
> 1 I had to remove all DOCTYPE declarations in xml files in the server 
> project (new restrictions on DTD)
> 2 appengine-maven-plugin 2.5.0 requires:
> 
> 
> --add-opens
> java.base/java.util=ALL-UNNAMED
> This stops 500 Server Error which I've not seen before:
> GCLOUD: java.lang.reflect.InaccessibleObjectException:
> Unable to make field accessible: module java.base does not "opens 
> java.util" to unnamed module @2c95ac9e
>
> So Craig, you say with Java17 on GAE, there isn't a web server included 
> anymore.
> So this has to be defined somewhere in  appengine-maven-plugin ?
> The minimum level to avoid being shut down on GAE standard is >8
> & 11 is the max for GWT, so that would seem do for now, why Java 17  ?
>
> On Wednesday, December 20, 2023 at 4:46:03 AM UTC Craig Mitchell wrote:
>
>> No worries not posting the POMs Tim.
>>
>> The bit I'm struggling with, the old Java 8 version had its own GAE 
>> server.  So I would run that, and a GWT Code Server.  Easy!
>>
>> *btw:* I'm talking about GAE Standard.  GAE Flexible you can do whatever 
>> you want, but that's more work and more expensive.
>>
>> Now with the upgrade to Java17 on GAE, there isn't a web server included 
>> anymore.  It's up to you to supply one.  I would assume when you deploy it, 
>> it doesn't actually use your server, but what setup is GAE expecting for 
>> the deploy?
>>
>> I see there is a SpringBoot GAE example, so it might be easier to use 
>> that, and get GWT to work with SpringBoot.  Not sure.  Very interested to 
>> hear what you're doing.
>>
>> Thanks!
>>
>> On Wednesday 20 December 2023 at 1:51:55 pm UTC+11 tim_mac...@yahoo.co.uk 
>> wrote:
>>
>>> For some years I've been deploying GWT 2.8.2 to GAE with Maven & Google 
>>> Cloud Tools. 
>>> I now find GAE is not supporting Java 8 after January, so currently 
>>> upgrading (rather slowly). 
>>> There are 4 long POM files,  probably better to mail them then post a 
>>> distilled version here ?
>>>
>>> On Sunday, December 17, 2023 at 5:20:56 AM UTC Craig Mitchell wrote:
>>>
>>>> Hi,
>>>>
>>>> The instructions here 
>>>> https://www.gwtproject.org/doc/latest/tutorial/appengine.html are no 
>>>> longer valid, as the Google Plugin for Eclipse is now dead (Google no 
>>>> longer supports Java 1.8, and the Google Plugin for Eclipse doesn't 
>>>> support 
>>>> any Eclipse versions that support anything after Java 1.8).  Ref:  
>>>> https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3710
>>>>
>>>> The new approach with GAE is to use Maven or Gradle with Google Cloud 
>>>> Tools.
>>>>
>>>> I've been struggling to work out how this is supposed to happen.  It 
>>>> looks like we now have to provide our own Web Server for GAE, but can we 
>>>> use the Jetty server that GWT uses for development?  I assume the deploy 
>>>> build would not include the Jetty web server?
>>>>
>>&

Re: Deploy to Google App Engine (GAE)

2023-12-19 Thread Craig Mitchell
No worries not posting the POMs Tim.

The bit I'm struggling with, the old Java 8 version had its own GAE 
server.  So I would run that, and a GWT Code Server.  Easy!

*btw:* I'm talking about GAE Standard.  GAE Flexible you can do whatever 
you want, but that's more work and more expensive.

Now with the upgrade to Java17 on GAE, there isn't a web server included 
anymore.  It's up to you to supply one.  I would assume when you deploy it, 
it doesn't actually use your server, but what setup is GAE expecting for 
the deploy?

I see there is a SpringBoot GAE example, so it might be easier to use that, 
and get GWT to work with SpringBoot.  Not sure.  Very interested to hear 
what you're doing.

Thanks!

On Wednesday 20 December 2023 at 1:51:55 pm UTC+11 tim_mac...@yahoo.co.uk 
wrote:

> For some years I've been deploying GWT 2.8.2 to GAE with Maven & Google 
> Cloud Tools. 
> I now find GAE is not supporting Java 8 after January, so currently 
> upgrading (rather slowly). 
> There are 4 long POM files,  probably better to mail them then post a 
> distilled version here ?
>
> On Sunday, December 17, 2023 at 5:20:56 AM UTC Craig Mitchell wrote:
>
>> Hi,
>>
>> The instructions here 
>> https://www.gwtproject.org/doc/latest/tutorial/appengine.html are no 
>> longer valid, as the Google Plugin for Eclipse is now dead (Google no 
>> longer supports Java 1.8, and the Google Plugin for Eclipse doesn't support 
>> any Eclipse versions that support anything after Java 1.8).  Ref:  
>> https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3710
>>
>> The new approach with GAE is to use Maven or Gradle with Google Cloud 
>> Tools.
>>
>> I've been struggling to work out how this is supposed to happen.  It 
>> looks like we now have to provide our own Web Server for GAE, but can we 
>> use the Jetty server that GWT uses for development?  I assume the deploy 
>> build would not include the Jetty web server?
>>
>> If anyone has deployed a GWT app to GAE with Maven and the new Google 
>> Cloud Tools, it would be great if you could give high level instructions on 
>> how it's all supposed to fit together.
>>
>> An example Maven POM file with both the Google Cloud Tools, and GWT would 
>> be even better.  
>>
>> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2a454300-0517-400e-8e5c-9754f9d4f1f8n%40googlegroups.com.


Deploy to Google App Engine (GAE)

2023-12-16 Thread Craig Mitchell
Hi,

The instructions 
here https://www.gwtproject.org/doc/latest/tutorial/appengine.html are no 
longer valid, as the Google Plugin for Eclipse is now dead (Google no 
longer supports Java 1.8, and the Google Plugin for Eclipse doesn't support 
any Eclipse versions that support anything after Java 1.8).  
Ref:  https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3710

The new approach with GAE is to use Maven or Gradle with Google Cloud Tools.

I've been struggling to work out how this is supposed to happen.  It looks 
like we now have to provide our own Web Server for GAE, but can we use the 
Jetty server that GWT uses for development?  I assume the deploy build 
would not include the Jetty web server?

If anyone has deployed a GWT app to GAE with Maven and the new Google Cloud 
Tools, it would be great if you could give high level instructions on how 
it's all supposed to fit together.

An example Maven POM file with both the Google Cloud Tools, and GWT would 
be even better.  

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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/64c891f6-21ad-4018-bb2d-5ce8911f3b93n%40googlegroups.com.


Re: Experiences with Kotlin/JS?

2023-07-15 Thread Craig Mitchell
Also would like to hear from someone with some deep experience with it for 
a good comparison.  However, my 2 cents from what I've seen...

Good integration and you get the basics of Kotlin to JS compilation, plus 
easy to use JavaScript interoperability.

You need to include a 1.3Mb kotlin.js library file with your project which 
isn't ideal.  And if you want to use extra features, like the kotlin 
html-js lib, you also need to add those, which further increases the JS 
download size.

Probably a good choice for connecting a Kotlin project to a JS project, or 
if you just need some simple JS for your Kotlin project.  If you needed 
more features, GWT would be a better choice (with its UIBinder, RPC, ...).

I agree with your comments about J2CL.

Personally, I'm more excited about Java to WASM compilations that will 
hopefully be more supported now WASM is getting garbage collection.

On Friday, 14 July 2023 at 11:37:22 am UTC+10 ji...@jinq.org wrote:

> I'm a long-time GWT user, but I've recently been tempted by the siren 
> songs of Kotlin/JS. Does anyone have any experience with it? Is it worth 
> migrating to?
>
> How large is its JS output compared to GWT? Is the code output reliable 
> and mature? How is the debugging? How is the JS interop? I've read that 
> there might be semi-automated methods of converting Java code to 
> Kotlin--how have people found that? I don't use many of the GWT libraries, 
> so I can easily rework that aspect of the code. Can I stay with 
> Eclipse-Maven or will I have to move to IntelliJ-Gradle? 
>
> Every time I look at J2CL, it just seems like it went too deep down the 
> Google rabbit-hole and is completely divorced from modern JavaScript 
> practices, so I've been curious about other possible future migration paths 
> for my GWT code.
>

-- 
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/72563d2b-75df-4db5-a9f3-6b1cf5051d3fn%40googlegroups.com.


Re: GWT for a Java to WASM compiler

2023-05-16 Thread Craig Mitchell
I think the advantages come from transpiling languages other than JS to 
WASM (in their examples, Kotlin and Dart).  Eg: An integer in Java, will 
still be in integer in WASM, while when you ask GWT for an integer, it has 
to do a bunch of magic, as JS doesn't have integers.

On Sunday, 14 May 2023 at 9:50:58 pm UTC+10 lofid...@gmail.com wrote:

> Thanks for the info. A very good explanation in that video.
>
> But still don't understand why would this solution with WASM GC 2x faster 
> than the *"pure transpiling"* solution? The latter is completely in JS 
> and uses the GC from JS as it is.
>
> Does this means using JS with WASM will be 2x faster than the pure JS??? 藍
>
> Thanks 
> Lofi
>
> Craig Mitchell schrieb am Freitag, 12. Mai 2023 um 12:27:43 UTC+2:
>
>> At Google I/O 2023, they showed that WASM (Web Assembly) is finally 
>> getting garbage collection (as well as shared memory).
>>
>> https://developers.googleblog.com/2023/05/bringing-kotlin-to-web.html
>> https://youtu.be/RcHER-3gFXI?t=604
>>
>> They showed that JetBrains was experimenting with Kotlin compiling to 
>> WASM.
>>
>> There wasn't any mention of anyone doing Java compilation to WASM.
>>
>> I wonder how hard it would be to modify GWT to compile to WASM.  
>> Possible?  Thoughts?
>>
>

-- 
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/edaac5a4-7bdd-42d0-a6af-0909da7d0573n%40googlegroups.com.


Re: GWT for a Java to WASM compiler

2023-05-12 Thread Craig Mitchell
Awesome!  Looks like J2CL is on it!  

>From memory, TeaVM has had WASM in an undocumented  and experimental status 
for a few years now.  I won't be holding my breath for that one.  

On Saturday, 13 May 2023 at 2:30:51 am UTC+10 Thomas Broyer wrote:

> Also, TeaVM does Java → WebAssembly (WASM or WASI)
> https://www.teavm.org/
> No idea if it already leverages WASM-GC or it's in their roadmap
>
> On Friday, May 12, 2023 at 12:59:17 PM UTC+2 gordan...@steatoda.com wrote:
>
>> On 12. 05. 2023. 12:27, Craig Mitchell wrote: 
>> > 
>> > There wasn't any mention of anyone doing Java compilation to WASM. 
>> > 
>> > I wonder how hard it would be to modify GWT to compile to WASM.  
>> Possible?  Thoughts? 
>>
>> There is a Wasm compilation target in J2CL, but I haven't ever tried it 
>> myself: 
>>
>> https://github.com/google/j2cl 
>> https://github.com/google/j2cl/issues/88 
>> https://github.com/google/j2cl/issues/93 -> according to this one, they 
>> are working on their WASM support currently ("Now") 
>>
>> -gkresic. 
>>
>

-- 
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/40619553-9a04-4e15-a903-57264bd1824dn%40googlegroups.com.


GWT for a Java to WASM compiler

2023-05-12 Thread Craig Mitchell
At Google I/O 2023, they showed that WASM (Web Assembly) is finally getting 
garbage collection (as well as shared memory).

https://developers.googleblog.com/2023/05/bringing-kotlin-to-web.html
https://youtu.be/RcHER-3gFXI?t=604

They showed that JetBrains was experimenting with Kotlin compiling to WASM.

There wasn't any mention of anyone doing Java compilation to WASM.

I wonder how hard it would be to modify GWT to compile to WASM.  Possible?  
Thoughts?

-- 
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/31f2c100-cdfe-403d-921b-6c975fdc6f94n%40googlegroups.com.


Re: Is it possible to use the new Clipboard API in a GWT app? It depends on document.hasFocus being true.

2023-01-04 Thread Craig Mitchell
I can't see enough of your code to work out what you're doing.

At a guess, you just need to do:

public void pasteDataIntoGrid(BaseEditorGridPanel grid, BaseGridRecordDef 
recordDef, Loaded pasteResult) {
  readText(text -> {
// Stick the text into your grid here

// As it's now an async call, you can't return a success/fail straight 
away, so we do a callback instead
pasteResult.data(true);
  });
}

On Wednesday, 4 January 2023 at 5:52:25 pm UTC+11 patil.p...@gmail.com 
wrote:

> I tried all things, below is the actual flow of code where I need 
> clipboard copied text, upon click on tool icon below function gets called,
>
> protected Function pasteFromExcelFunction =new Function(){
> public void execute(){
>  if(readOnly){
>  return;
>  }// its false
> try{
>  if(pasteFromExcelHelper.pasteDataIntoGrid(BaseEditorGridPanel.this, 
> getRecordDef()));
>doAfterPaste();
>}
> }
>   }
> public boolean pasteDataIntoGrid(BaseEditorGridPanel grid, 
> BaseGridRecordDef recordDef)
> {
>   boolean pasteSuccessful=true;
>   String pastedText= readFromClipboard(); 
>
> * // pastedText is further adjusted as per the grid-all java code*
>  }   
>  private String readFromClipboard (){
> return JavaScriptUtils.getClipboardData();
>}
> public static native String getClipboardData()/*-{
>
> *// I want modern clipboard api to return string*
> if($wnd.clipboardData && clipboardData.setData){
> return $wnd.clipboardData.getData('Text');
> }-*/;
>
>
> So with respect to above method i.e. getClipboardData , which returns string 
> , this works fine with IE but not with modern browser, so I tried new 
> clipboard api but i cant return string. Could you please guide me with repect 
> to above code, its been while I am struggling !!
>
>
>
> On Wed, Jan 4, 2023 at 11:28 AM Craig Mitchell  
> wrote:
>
>> ?  That is the Java code.
>>
>> readTextButton.addClickHandler(event -> {
>>   readText(text -> {
>> // Do whatever you want with the text, eg:
>> GWT.log("The text: " + text);
>>   });
>> });
>>
>> (assuming you are running Java8 or later)
>>
>> The readText is your JSNI call.
>>
>> On Wednesday, 4 January 2023 at 1:18:31 pm UTC+11 patil.p...@gmail.com 
>> wrote:
>>
>>> I am not sure if I can call Java code
>>> readText(text -> {
>>>// Do whatever you want with the text, eg:
>>>GWT.log("The text: " + text);// can I call Java code here to process 
>>> this string?
>>> });
>>>
>>> On Wed, 4 Jan 2023, 4:00 am Craig Mitchell,  
>>> wrote:
>>>
>>>> readText(text -> {
>>>>// Do whatever you want with the text, eg:
>>>>GWT.log("The text: " + text);
>>>> });
>>>>
>>>> Note:  It is returned asynchronously (not from the return statement), 
>>>> so you'll probably need to modify your calling code to cater for that.
>>>>
>>>> On Wednesday, 4 January 2023 at 3:40:05 am UTC+11 patil.p...@gmail.com 
>>>> wrote:
>>>>
>>>>> Hi @Craig Mitchell,
>>>>> You were right about script,
>>>>> The above script posted by me seems to have issues, below is the 
>>>>> working script, I am not getting any compiler errors but neither getting 
>>>>> any string as return value. 
>>>>> I am testing things using below code, 
>>>>>
>>>>> readTextButton.addClickHandler(new ClickHandler(){
>>>>> public void onClick(ClickEvent event){
>>>>>
>>>>> //Goal is to receive copied value on readText() function call.
>>>>> String str =readText(null)// *1. What should I pass as argument over 
>>>>> here-I know null argument is not correct, My apologies as I am not well 
>>>>> versed with async //callbacks*
>>>>> }
>>>>> });
>>>>>
>>>>>
>>>>>
>>>>> public static native String readText(Loaded clipboardText)/*-{
>>>>> try{
>>>>>
>>>>> if($wnd.navigator.clipboard){
>>>>>var promise=$wnd.navigator.clipboard.readText();
>>>>> var resolve= function(text){
>>>>> console.log(txt);  *//2.Here I can see copied text in console*
>>>>>clipboardText.@com.mypackage.Loaded::data(*)(text);
>>>>> };
>>>>&g

Re: Is it possible to use the new Clipboard API in a GWT app? It depends on document.hasFocus being true.

2023-01-03 Thread Craig Mitchell
?  That is the Java code.

readTextButton.addClickHandler(event -> {
  readText(text -> {
// Do whatever you want with the text, eg:
GWT.log("The text: " + text);
  });
});

(assuming you are running Java8 or later)

The readText is your JSNI call.

On Wednesday, 4 January 2023 at 1:18:31 pm UTC+11 patil.p...@gmail.com 
wrote:

> I am not sure if I can call Java code
> readText(text -> {
>// Do whatever you want with the text, eg:
>GWT.log("The text: " + text);// can I call Java code here to process 
> this string?
> });
>
> On Wed, 4 Jan 2023, 4:00 am Craig Mitchell,  
> wrote:
>
>> readText(text -> {
>>// Do whatever you want with the text, eg:
>>GWT.log("The text: " + text);
>> });
>>
>> Note:  It is returned asynchronously (not from the return statement), so 
>> you'll probably need to modify your calling code to cater for that.
>>
>> On Wednesday, 4 January 2023 at 3:40:05 am UTC+11 patil.p...@gmail.com 
>> wrote:
>>
>>> Hi @Craig Mitchell,
>>> You were right about script,
>>> The above script posted by me seems to have issues, below is the working 
>>> script, I am not getting any compiler errors but neither getting any string 
>>> as return value. 
>>> I am testing things using below code, 
>>>
>>> readTextButton.addClickHandler(new ClickHandler(){
>>> public void onClick(ClickEvent event){
>>>
>>> //Goal is to receive copied value on readText() function call.
>>> String str =readText(null)// *1. What should I pass as argument over 
>>> here-I know null argument is not correct, My apologies as I am not well 
>>> versed with async //callbacks*
>>> }
>>> });
>>>
>>>
>>>
>>> public static native String readText(Loaded clipboardText)/*-{
>>> try{
>>>
>>> if($wnd.navigator.clipboard){
>>>var promise=$wnd.navigator.clipboard.readText();
>>> var resolve= function(text){
>>> console.log(txt);  *//2.Here I can see copied text in console*
>>>clipboardText.@com.mypackage.Loaded::data(*)(text);
>>> };
>>>  var reject=function(reason){
>>>   console.log('$wnd.navigator.clipboard.readText failed: + reason'); 
>>> *//3.Getting 
>>> cannot read properties of null*
>>>
>>>
>>> };
>>> promise["catch"](reject);
>>> promise.then(resolve,reject)["catch"](reject);
>>>
>>> }
>>>
>>> }
>>>
>>> catch(e){}
>>> }-*/;
>>>
>>>
>>>
>>>
>>> On Fri, Dec 30, 2022 at 10:53 AM Craig Mitchell <
>>> ma...@craig-mitchell.com> wrote:
>>>
>>>> As it's doing it asynchronously, you'll need to add a callback to 
>>>> return the string.
>>>>
>>>> Something like this:
>>>>
>>>> ---
>>>>
>>>> package mypackage;
>>>>
>>>> public interface Loaded {
>>>> public void data(T data);
>>>> }
>>>>
>>>> ---
>>>>
>>>> public static native String readText(Loaded clipboardText) /*-{
>>>> try {
>>>> var promise = $wnd.navigator.clipboard.readText();
>>>> var resolve = function(text) {
>>>> console.log(text);// I can print text here but not able to 
>>>> return it as String
>>>> clipboardText.@mypackage.Loaded::data(*)(text);
>>>> }
>>>> catch (e){
>>>>   //futher code goes here
>>>> }
>>>> }-*/;
>>>>
>>>> ---
>>>>
>>>> Note:  I'm just copying your JavaScript, it doesn't look correct to me, 
>>>> I think you also need:
>>>>
>>>> promise.then(resolve);
>>>> or something like that.
>>>>
>>>> On Friday, 30 December 2022 at 2:30:14 pm UTC+11 patil.p...@gmail.com 
>>>> wrote:
>>>>
>>>>> Yes, it's working but not working with GWT, I think the async function 
>>>>> and await keyword is not supported with GWT, was getting a compiler 
>>>>> error, 
>>>>> I tried below code which worked, but not able to return as String, can 
>>>>> print the copied text with console.log(text). As of now I didn't get any 
>>>>> solution, I tried to search on the internet but had no luck.
>>>>>

Re: Is it possible to use the new Clipboard API in a GWT app? It depends on document.hasFocus being true.

2023-01-03 Thread Craig Mitchell
readText(text -> {
   // Do whatever you want with the text, eg:
   GWT.log("The text: " + text);
});

Note:  It is returned asynchronously (not from the return statement), so 
you'll probably need to modify your calling code to cater for that.

On Wednesday, 4 January 2023 at 3:40:05 am UTC+11 patil.p...@gmail.com 
wrote:

> Hi @Craig Mitchell,
> You were right about script,
> The above script posted by me seems to have issues, below is the working 
> script, I am not getting any compiler errors but neither getting any string 
> as return value. 
> I am testing things using below code, 
>
> readTextButton.addClickHandler(new ClickHandler(){
> public void onClick(ClickEvent event){
>
> //Goal is to receive copied value on readText() function call.
> String str =readText(null)// *1. What should I pass as argument over 
> here-I know null argument is not correct, My apologies as I am not well 
> versed with async //callbacks*
> }
> });
>
>
>
> public static native String readText(Loaded clipboardText)/*-{
> try{
>
> if($wnd.navigator.clipboard){
>var promise=$wnd.navigator.clipboard.readText();
> var resolve= function(text){
> console.log(txt);  *//2.Here I can see copied text in console*
>clipboardText.@com.mypackage.Loaded::data(*)(text);
> };
>  var reject=function(reason){
>   console.log('$wnd.navigator.clipboard.readText failed: + reason'); 
> *//3.Getting 
> cannot read properties of null*
>
>
> };
> promise["catch"](reject);
> promise.then(resolve,reject)["catch"](reject);
>
> }
>
> }
>
> catch(e){}
> }-*/;
>
>
>
>
> On Fri, Dec 30, 2022 at 10:53 AM Craig Mitchell  
> wrote:
>
>> As it's doing it asynchronously, you'll need to add a callback to return 
>> the string.
>>
>> Something like this:
>>
>> ---
>>
>> package mypackage;
>>
>> public interface Loaded {
>> public void data(T data);
>> }
>>
>> ---
>>
>> public static native String readText(Loaded clipboardText) /*-{
>> try {
>> var promise = $wnd.navigator.clipboard.readText();
>> var resolve = function(text) {
>> console.log(text);// I can print text here but not able to return 
>> it as String
>> clipboardText.@mypackage.Loaded::data(*)(text);
>> }
>> catch (e){
>>   //futher code goes here
>> }
>> }-*/;
>>
>> ---
>>
>> Note:  I'm just copying your JavaScript, it doesn't look correct to me, I 
>> think you also need:
>>
>> promise.then(resolve);
>> or something like that.
>>
>> On Friday, 30 December 2022 at 2:30:14 pm UTC+11 patil.p...@gmail.com 
>> wrote:
>>
>>> Yes, it's working but not working with GWT, I think the async function 
>>> and await keyword is not supported with GWT, was getting a compiler error, 
>>> I tried below code which worked, but not able to return as String, can 
>>> print the copied text with console.log(text). As of now I didn't get any 
>>> solution, I tried to search on the internet but had no luck.
>>>
>>>
>>> is there any library or anything to be included/imported to get async/await 
>>> support with GWT?
>>>
>>> public static native String readText()/*-{
>>>try
>>>  {
>>>   var promise = $wnd.navigator.clipboard.readText();
>>>   var resolve = function(text){
>>>   console.log(text);// I can print text here but not able to return it 
>>> as String
>>>   }
>>>   catch (e){
>>>   //futher code goes here
>>>   }
>>>  }-*/;
>>>
>>>
>>> On Fri, Dec 30, 2022 at 8:04 AM Craig Mitchell  
>>> wrote:
>>>
>>>> Apologies.  That stackoverflow example gets blocked due to cross origin.
>>>>
>>>> Just ran a simple test:
>>>>
>>>> 
>>>> 
>>>> async function readClipboard () {
>>>>   if (!navigator.clipboard) {
>>>> // Clipboard API not available
>>>> return
>>>>   }
>>>>   try {
>>>> const text = await navigator.clipboard.readText();
>>>> document.querySelector('.clipboard-content').innerText = text;
>>>>   } catch (err) {
>>>> console.error('Failed to copy!', err)
>>>>   }
>>>> }
>>>>
>>>> function updateClipboard() {
>>>>   // Here You Can Debug without DomExcep

Re: Is it possible to use the new Clipboard API in a GWT app? It depends on document.hasFocus being true.

2022-12-29 Thread Craig Mitchell
As it's doing it asynchronously, you'll need to add a callback to return 
the string.

Something like this:

---

package mypackage;

public interface Loaded {
public void data(T data);
}

---

public static native String readText(Loaded clipboardText) /*-{
try {
var promise = $wnd.navigator.clipboard.readText();
var resolve = function(text) {
console.log(text);// I can print text here but not able to return 
it as String
clipboardText.@mypackage.Loaded::data(*)(text);
}
catch (e){
  //futher code goes here
}
}-*/;

---

Note:  I'm just copying your JavaScript, it doesn't look correct to me, I 
think you also need:

promise.then(resolve);
or something like that.

On Friday, 30 December 2022 at 2:30:14 pm UTC+11 patil.p...@gmail.com wrote:

> Yes, it's working but not working with GWT, I think the async function and 
> await keyword is not supported with GWT, was getting a compiler error, I 
> tried below code which worked, but not able to return as String, can print 
> the copied text with console.log(text). As of now I didn't get any 
> solution, I tried to search on the internet but had no luck.
>
>
> is there any library or anything to be included/imported to get async/await 
> support with GWT?
>
> public static native String readText()/*-{
>try
>  {
>   var promise = $wnd.navigator.clipboard.readText();
>   var resolve = function(text){
>   console.log(text);// I can print text here but not able to return it as 
> String
>   }
>   catch (e){
>   //futher code goes here
>   }
>  }-*/;
>
>
> On Fri, Dec 30, 2022 at 8:04 AM Craig Mitchell  
> wrote:
>
>> Apologies.  That stackoverflow example gets blocked due to cross origin.
>>
>> Just ran a simple test:
>>
>> 
>> 
>> async function readClipboard () {
>>   if (!navigator.clipboard) {
>> // Clipboard API not available
>> return
>>   }
>>   try {
>> const text = await navigator.clipboard.readText();
>> document.querySelector('.clipboard-content').innerText = text;
>>   } catch (err) {
>> console.error('Failed to copy!', err)
>>   }
>> }
>>
>> function updateClipboard() {
>>   // Here You Can Debug without DomException
>>   debugger
>>   const clipboard = 
>> document.querySelector('.clipboard-content').innerText;
>>   document.querySelector('.clipboard-content').innerText = 'Updated => ' 
>> + clipboard;
>> }
>> 
>>
>> 
>> Paste
>> 
>> Edit
>> 
>> 
>>
>> and it worked fine (browser popped up a message asking for permission).
>>
>> On Thursday, 29 December 2022 at 5:02:34 pm UTC+11 Craig Mitchell wrote:
>>
>>> Browsers now need you to get your users to grant permissions in their 
>>> browsers for this to work.  See "Permissions API" here: 
>>> https://developer.mozilla.org/en-US/docs/Web/API/Clipboard/readText#security
>>>  
>>>
>>> An example:  https://stackoverflow.com/a/59954231/418057  When I run 
>>> the code snippet, and press "paste", it give "NotAllowedError".
>>>
>>> On Monday, 26 December 2022 at 5:02:32 pm UTC+11 patil.p...@gmail.com 
>>> wrote:
>>>
>>>> Hi Experts,
>>>> I am newbie with javascript and GWT, I want my function to return 
>>>> clipboard data,for further use in application upon click of(tool button).
>>>> Is there any way to get the text read from clipboard, I am looking 
>>>> something similar @Jim Douglas mentioned, with 
>>>> $wnd.navigator.clipboard.readText() is working but I need the "pasted" 
>>>> text 
>>>> to be returned to my native method call 
>>>>
>>>> public static native String readText(){
>>>> try{
>>>>if($wnd.navigator.clipboard){
>>>>   var promise= $wnd.navigator.clipboard.readText();
>>>>   var resolve =function(text){
>>>>   console.log(text);   // i want this text which i can see on 
>>>> console(string)  to be returned , Is it possible and how to achieve it any 
>>>> hack to ge
>>>> }
>>>>   }
>>>> }
>>>> }
>>>>
>>>> Please help, as i got stuck at this point for a while. Thanks.
>>>> On Wednesday, 16 October 2019 at 19:53:27 UTC+5:30 Jim Douglas wrote:
>>>>
>>>>> Oh wow, I completely missed that. Of course *navigator* is really 
>>>>> *window.navigator*. JavaScript sample code almost always refere

Re: Is it possible to use the new Clipboard API in a GWT app? It depends on document.hasFocus being true.

2022-12-29 Thread Craig Mitchell
Apologies.  That stackoverflow example gets blocked due to cross origin.

Just ran a simple test:



async function readClipboard () {
  if (!navigator.clipboard) {
// Clipboard API not available
return
  }
  try {
const text = await navigator.clipboard.readText();
document.querySelector('.clipboard-content').innerText = text;
  } catch (err) {
console.error('Failed to copy!', err)
  }
}

function updateClipboard() {
  // Here You Can Debug without DomException
  debugger
  const clipboard = document.querySelector('.clipboard-content').innerText;
  document.querySelector('.clipboard-content').innerText = 'Updated => ' + 
clipboard;
}



Paste

Edit



and it worked fine (browser popped up a message asking for permission).

On Thursday, 29 December 2022 at 5:02:34 pm UTC+11 Craig Mitchell wrote:

> Browsers now need you to get your users to grant permissions in their 
> browsers for this to work.  See "Permissions API" here: 
> https://developer.mozilla.org/en-US/docs/Web/API/Clipboard/readText#security
>  
>
> An example:  https://stackoverflow.com/a/59954231/418057  When I run the 
> code snippet, and press "paste", it give "NotAllowedError".
>
> On Monday, 26 December 2022 at 5:02:32 pm UTC+11 patil.p...@gmail.com 
> wrote:
>
>> Hi Experts,
>> I am newbie with javascript and GWT, I want my function to return 
>> clipboard data,for further use in application upon click of(tool button).
>> Is there any way to get the text read from clipboard, I am looking 
>> something similar @Jim Douglas mentioned, with 
>> $wnd.navigator.clipboard.readText() is working but I need the "pasted" text 
>> to be returned to my native method call 
>>
>> public static native String readText(){
>> try{
>>if($wnd.navigator.clipboard){
>>   var promise= $wnd.navigator.clipboard.readText();
>>   var resolve =function(text){
>>   console.log(text);   // i want this text which i can see on 
>> console(string)  to be returned , Is it possible and how to achieve it any 
>> hack to ge
>> }
>>   }
>> }
>> }
>>
>> Please help, as i got stuck at this point for a while. Thanks.
>> On Wednesday, 16 October 2019 at 19:53:27 UTC+5:30 Jim Douglas wrote:
>>
>>> Oh wow, I completely missed that. Of course *navigator* is really 
>>> *window.navigator*. JavaScript sample code almost always references 
>>> *navigator*, not *window.navigator*, and I rarely think of that detail. 
>>> Even after staring at that code for hours looking for something I might 
>>> have missed, that never occurred to me. Thanks, Thomas; that's exactly what 
>>> I was missing. With that simple change, this now works.
>>>
>>>
>>> On Wednesday, October 16, 2019 at 5:44:05 AM UTC-7, Thomas Broyer wrote:
>>>>
>>>> Have you tried with $wnd.navigator.clipboard?
>>>>
>>>> On Tuesday, October 15, 2019 at 10:40:04 PM UTC+2, Jim Douglas wrote:
>>>>>
>>>>> Ok, there are a few moving parts to this. Keeping it as short as 
>>>>> possible, this is the new Clipboard API:
>>>>>
>>>>> https://developer.mozilla.org/en-US/docs/Web/API/Clipboard
>>>>>
>>>>> Support is extremely limited at the moment, but for now I'd be happy 
>>>>> to get something working in Chrome:
>>>>>
>>>>> https://caniuse.com/#feat=mdn-api_clipboard
>>>>>
>>>>> Here's Google's live sample page:
>>>>>
>>>>> https://googlechrome.github.io/samples/async-clipboard/index.html
>>>>>
>>>>> For obvious reasons, there's a lot of paranoid security around 
>>>>> JavaScript access to the clipboard. This is the specific detail I'm 
>>>>> running 
>>>>> into:
>>>>>
>>>>>
>>>>> https://stackoverflow.com/questions/56306153/domexception-on-calling-navigator-clipboard-readtext
>>>>>
>>>>> These APIs throw a security exception if document.hasFocus() is false. 
>>>>> And I'm not seeing any way to honour that rule in a GWT app. In my 
>>>>> production app, and in a tiny standalone GWT app I just generated for 
>>>>> testing purposes, document.hasFocus() is always false ($doc.hasFocus() is 
>>>>> true).
>>>>>
>>>>> For testing purposes, I generated the GWT StockWatcher demo app:
>>>>>
>>>>> http://www.gwtproject.org/doc/latest/tutorial/create.html
>>>>>
>>&g

Re: Is it possible to use the new Clipboard API in a GWT app? It depends on document.hasFocus being true.

2022-12-28 Thread Craig Mitchell
Browsers now need you to get your users to grant permissions in their 
browsers for this to work.  See "Permissions API" here: 
https://developer.mozilla.org/en-US/docs/Web/API/Clipboard/readText#security 

An example:  https://stackoverflow.com/a/59954231/418057  When I run the 
code snippet, and press "paste", it give "NotAllowedError".

On Monday, 26 December 2022 at 5:02:32 pm UTC+11 patil.p...@gmail.com wrote:

> Hi Experts,
> I am newbie with javascript and GWT, I want my function to return 
> clipboard data,for further use in application upon click of(tool button).
> Is there any way to get the text read from clipboard, I am looking 
> something similar @Jim Douglas mentioned, with 
> $wnd.navigator.clipboard.readText() is working but I need the "pasted" text 
> to be returned to my native method call 
>
> public static native String readText(){
> try{
>if($wnd.navigator.clipboard){
>   var promise= $wnd.navigator.clipboard.readText();
>   var resolve =function(text){
>   console.log(text);   // i want this text which i can see on 
> console(string)  to be returned , Is it possible and how to achieve it any 
> hack to ge
> }
>   }
> }
> }
>
> Please help, as i got stuck at this point for a while. Thanks.
> On Wednesday, 16 October 2019 at 19:53:27 UTC+5:30 Jim Douglas wrote:
>
>> Oh wow, I completely missed that. Of course *navigator* is really 
>> *window.navigator*. JavaScript sample code almost always references 
>> *navigator*, not *window.navigator*, and I rarely think of that detail. 
>> Even after staring at that code for hours looking for something I might 
>> have missed, that never occurred to me. Thanks, Thomas; that's exactly what 
>> I was missing. With that simple change, this now works.
>>
>>
>> On Wednesday, October 16, 2019 at 5:44:05 AM UTC-7, Thomas Broyer wrote:
>>>
>>> Have you tried with $wnd.navigator.clipboard?
>>>
>>> On Tuesday, October 15, 2019 at 10:40:04 PM UTC+2, Jim Douglas wrote:

 Ok, there are a few moving parts to this. Keeping it as short as 
 possible, this is the new Clipboard API:

 https://developer.mozilla.org/en-US/docs/Web/API/Clipboard

 Support is extremely limited at the moment, but for now I'd be happy to 
 get something working in Chrome:

 https://caniuse.com/#feat=mdn-api_clipboard

 Here's Google's live sample page:

 https://googlechrome.github.io/samples/async-clipboard/index.html

 For obvious reasons, there's a lot of paranoid security around 
 JavaScript access to the clipboard. This is the specific detail I'm 
 running 
 into:


 https://stackoverflow.com/questions/56306153/domexception-on-calling-navigator-clipboard-readtext

 These APIs throw a security exception if document.hasFocus() is false. 
 And I'm not seeing any way to honour that rule in a GWT app. In my 
 production app, and in a tiny standalone GWT app I just generated for 
 testing purposes, document.hasFocus() is always false ($doc.hasFocus() is 
 true).

 For testing purposes, I generated the GWT StockWatcher demo app:

 http://www.gwtproject.org/doc/latest/tutorial/create.html

 Then I added some UI hooks for clipboard testing elements in 
 StockWatcher.html:

 Web Application Starter Project


 

   

 Please enter 
 your name:

   

   

 

 

   

   

 >>> *"errorLabelContainer"*>

   

   

 

 

 

   

 

 

   

 

 And minimal testing UI in StockWatcher.java onModuleLoad:

 TextBox readText = *new* TextBox();

 readText.setText("readText");

 Button readTextButton = *new* Button("readText");


 TextBox writeText = *new* TextBox();

 writeText.setText("writeText");

 Button writeTextButton = *new* Button("writeText");

 

 RootPanel.*get*("readTextField").add(readText);

 RootPanel.*get*("readTextButton").add(readTextButton);

 

 RootPanel.*get*("writeTextField").add(writeText);

 RootPanel.*get*("writeTextButton").add(writeTextButton);

 readTextButton.addClickHandler(*new* ClickHandler()

 {

 *public* *void* onClick(ClickEvent event)

 {

 readText();

 }

 });

 

 writeTextButton.addClickHandler(*new* ClickHandler()

 {

 *public* *void* onClick(ClickEvent event)

 {


Re: Trying to get GWT app deployed in local Tomcat (using Eclipse)

2022-11-18 Thread Craig Mitchell
Figured out the Sync CodeServer option only appears if you tick GWT in the 
Project Facets:
[image: Screen.png]

On Wednesday, 25 August 2021 at 12:09:28 am UTC+10 mmo wrote:

> Really odd!
> Here is how this looks on my side:
> [image: GWT-Facet-Settings.png]
>
> On Tuesday, August 24, 2021 at 3:41:34 PM UTC+2 Craig Mitchell wrote:
>
>> Interesting.  I don't have that setting:
>>
>> [image: screenshot.png]
>>
>> I'm using the standard Eclipse for Java Developers.  Not Eclipse for 
>> Enterprise Java.
>>
>> On Monday, 23 August 2021 at 11:01:20 pm UTC+10 mmo wrote:
>>
>>> @Craig Mitchell
>>>
>>> > I've never seen an option to start the code server automatically 
>>> Right-click on the mode --> GTW --> Settings --> GWT - Facet Settings: 
>>> There is a checkbox under "Super Development Mode" labeled "Sync the 
>>> CodeServer state with the WTP server. The WTP server start and stop will 
>>> also start and stop the CodeServer".
>>>
>>> > I think you mean the CodeServer doesn't always show in the Development 
>>> mode. 
>>> No - as I wrote: the CodeServer shows up reliably in this view, but the 
>>> Web-Server doesn't anymore. It used to, though, so I am puzzled why this is 
>>> not working anymore.
>>>
>>> > I just use a "Launch Chrome" launcher to start Chrome in debug, so I 
>>> don't need it to show up. 
>>> These "Connect to Chrome" and "Launch Chrome" entries usually appear in 
>>> the "Run As"/"Debug As"-context menu but often they don't. And once they 
>>> disappeared, they don't show up anymore until the next Eclipse-restart. 
>>> Very odd and annoying!  :-( 
>>>
>>>

-- 
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/58150799-80ea-4442-82e4-7e5e0ff07735n%40googlegroups.com.


Re: Modern browsers support for Copyclipboard functionality

2022-10-25 Thread Craig Mitchell
The  doc.execCommand('copy'), while deprecated, still works.  Eg:

@UiField TextBox myTextBox;

myTextBox.setFocus(true);
myTextBox.selectAll();
boolean success = copyToClipboard();

private static native boolean copyToClipboard() /*-{
return $doc.execCommand('copy');
}-*/;

If you run your site over HTTPS, the user grants permissions, and you jump 
though lots of hoops, you can also use the $wnd.clipboardData.readText() 
and $wnd.clipboardData.writeText(myText).

On Saturday, 22 October 2022 at 8:10:57 pm UTC+11 vas...@gmail.com wrote:

> Well it's the event "copy" as in my example. You need an eventHandler and 
> then the event is passed as argument to your handler.
>
> Hope that helps.
>
> On Thu, Oct 20, 2022 at 7:47 PM Pramod Patil  wrote:
>
>> Thanks again,
>> In below method - how to get "event " ?  so as to use 
>> event.clipboard.setData("text/plain", data), if I can get event handle then 
>> I may achieve desired results. 
>> public static native String setClipboardData(String data)/*-{
>>
>> if($wnd.clipboardData && clipboardData.setData){
>> return $wnd.clipboardData.setData('Text',Data);
>> }
>> }
>> }-
>>
>> On Thu, Oct 20, 2022 at 5:17 PM Vassilis Virvilis  
>> wrote:
>>
>>> I believe I did
>>>
>>> It's this snippet for copy
>>>
>>> event.clipboardData.setData("text/plain", data);
>>>
>>> On Thu, Oct 20, 2022 at 1:52 PM Pramod Patil  
>>> wrote:
>>>
 Thank you again, I understand security implications but objective is to 
 make it work for Edge, I have control over native methods, getClipBoardata 
 and setClipboardData(String data)  which are native methods in java. The 
 code which I have pasted above is working fine with IE browser, but not 
 with modern browsers. So can you help me with the code/pointers which can 
 replace above code and work for Edge,Chrome. Thanks.

 On Thursday, 20 October 2022 at 14:52:22 UTC+5:30 vas...@gmail.com 
 wrote:

> Well if I remember correctly it is not supposed to access the 
> clipboard directly because that would be a huge security issue.
>
> Consider the following scenario. You copy / paste your password for 
> your bank somewhere. Then you go to a random webpage. If the javascript 
> of 
> this webpage that runs on your computer/browser could access 
> (getClipboardData()) your clipboard your bank password would be 
> compromised.
>
> So you can only access the clipboard from inside an event handler that 
> handles the "copy" event aka Ctrl+C.
>
> The necessary details to access the data differ from IE and so I have 
> posted examples.
>
> I do not know why your code does not compile. I think native methods 
> are not checked so they tend to give NULL errors during runtime. If that 
> is 
> your case then caniuse is your friend.
>
> Vassilis
>
>
>
> On Thu, Oct 20, 2022 at 11:12 AM Pramod Patil  
> wrote:
>
>> Hi Thanks for your response, 
>> on both front at GWT and Javascript  I am at beginners level, will it 
>> be possible to have modification in below function, which will 
>> support copyclipboard functionality with Microsoft Edge. I tried 
>> navigator.clipboard.writeText() but code is not getting compiled.
>> public static native String getClipboardData()/*-{
>> i*f($wnd.clipboardData && clipboardData.setData){*
>> *return $wnd.clipboardData.getData('Text');*
>> }
>>
>> On Thu, Oct 20, 2022 at 12:36 PM Vassilis Virvilis  
>> wrote:
>>
>>> For non IE browsers I have this:
>>>
>>> // attach event listeners
>>> // copy - cut - paste handlers
>>> ((Element) 
>>> Js.cast(getElement())).addEventListener("copy", copy_li);
>>> ((Element) 
>>> Js.cast(getElement())).addEventListener("cut", cut_li);
>>> ((Element) 
>>> Js.cast(getElement())).addEventListener("paste", paste_li);
>>>
>>> where (Element) is elemental2.dom.Element
>>>
>>> copy_li is something like this:
>>>
>>> final elemental2.dom.EventListener copy_li = new 
>>> elemental2.dom.EventListener() {
>>> @Override
>>> public void handleEvent(elemental2.dom.Event evt) {
>>> final ClipboardEvent event = Js.cast(evt);
>>> copy(event);
>>> }
>>> };
>>>
>>> where ClipboardEvent is elemental2.dom.ClipboardEvent
>>>
>>> I need a copy function because I reuse it in the "Cut" functionality 
>>> also.
>>>
>>> and finally copy is something like this
>>>
>>>private void copy(ClipboardEvent event) {
>>> if (!hasData()) {  // <-- hasData() is your application 
>>> specific function
>>> return;
>>> }
>>>
>>> // do application stuff get/iterate and finally get the data 

Re: File upload stuck on loading

2022-10-12 Thread Craig Mitchell
Correction:   

On Wednesday, 12 October 2022 at 9:59:13 pm UTC+11 Craig Mitchell wrote:

> I have no clue what your error is, but it's so much easier to read files 
> with HTML5 now.
>
> Something like this:
> -
> 
>
> @UiField InputElement fileInput;
>
> Event.sinkEvents(fileInput, Event.ONCHANGE);
> Event.setEventListener(fileInput, event -> handleFileUpload());
>
> private void handleFileUpload() {
> JavaScriptObject files = fileInput.getPropertyJSO("files");
> 
> if (files instanceof JsArray) {
> JsArray filesArray = 
> (JsArray)files;
> 
> if (filesArray.length() > 0) {
> handleFileUploadJS(filesArray.get(0),  fileData -> 
> handleAfterFileUpload(fileData));
> }
> }
> }
>
> private static native void handleFileUploadJS(JavaScriptObject fileData) 
> /*-{
> var fileReader = new FileReader();
> fileReader.addEventListener("load", function () {
> // Your file data will be in fileReader.result
> }, false);
> fileReader.readAsDataURL(fileData);
> }-*/;
> -
>
> No server code needed.  :)
>
> On Wednesday, 12 October 2022 at 9:24:41 pm UTC+11 system.out...@gmail.com 
> wrote:
>
>> For file upload we are using GXT FileUploadField.
>> for server we are using servlets that extends GWT RemoteServiceServlet
>> There's a UploadExcelHandler that on success send. a notification. It 
>> uses puremvc4gwt.
>> We have a handle notification that gets the received data and calles 
>> methods to update the grid and reload it 
>> ( please read my last message for the reload, I found the root cause but 
>> no solution is found yet)
>> Thanks
>> Le mercredi 12 octobre 2022 à 11:59:26 UTC+2, system out a écrit :
>>
>>> Yes we are using GXT 2.2.5 with GWT 2.8.1
>>> We have a custom Grid object created that has an EditoGrid, 
>>> PagingToolbar, ListStore, ColumnModel and many other properties like 
>>> height..
>>> I found that the problem is caused by the load method inside the 
>>> PagingLoader.
>>> we have this line: 
>>> grid.reconfigure(store, grid.getColumnModel())
>>> then the following line that causes the error:
>>> loader.load(config).
>>> config is a PagingLoadConfig
>>> I tried loader.load() and loader.load(0.50) and 
>>> grid.getStore().getLoader().load()
>>> but nothing seems to work.
>>>
>>> Le mardi 11 octobre 2022 à 18:57:04 UTC+2, t.br...@gmail.com a écrit :
>>>
>>>> It would certainly help if you provided details on how you do the 
>>>> upload (using GWT's own FormPanel and FileUpload? or a third-party 
>>>> library? 
>>>> GXT-specific widgets?) and how you handle the response (including how you 
>>>> generate it server-side)
>>>> For example, see the note at 
>>>> https://www.gwtproject.org/javadoc/latest/com/google/gwt/user/client/ui/FormPanel.html#FormPanel--
>>>>  
>>>> about server-side requirements.
>>>>
>>>> On Tuesday, October 11, 2022 at 4:17:27 PM UTC+2 
>>>> system.out...@gmail.com wrote:
>>>>
>>>>> I managed to print results on client side. I use alerts to chek.
>>>>> The list is received as it is, we have a method that will fill the 
>>>>> grid with that list but somethiing is stopping it. It still print a 
>>>>> loading 
>>>>> spinner that never stops. 
>>>>> The same code works well with gwt 2.4/gxt 2.2.5.
>>>>> Now we are using gwt 2.8/gxt 2.2.5
>>>>>
>>>>> Le lundi 10 octobre 2022 à 21:04:58 UTC+2, system out a écrit :
>>>>>
>>>>>> I migtated gwt app from 2.4 to 2.8
>>>>>> After fixing build erros the app launches and interfaces are 
>>>>>> appearing.
>>>>>> We have a excel file upload.
>>>>>> When I click upload it is stuck on loading. A loading text appears 
>>>>>> and result never shows up.
>>>>>> There a method that takes data imported from excel and put fill some 
>>>>>> objects with it.
>>>>>> The data is well imported. The method that fill objects with it will 
>>>>>> return the filled objects as a List. When I return an empty list it 
>>>>>> works.
>>>>>> Do you know if there's something that should be changed due to the 
>>>>>> migration?
>>>>>>
>>>>>>

-- 
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/0640afcb-2b0c-46f8-88b3-596a21297770n%40googlegroups.com.


Re: File upload stuck on loading

2022-10-12 Thread Craig Mitchell
I have no clue what your error is, but it's so much easier to read files 
with HTML5 now.

Something like this:
-


@UiField InputElement fileInput;

Event.sinkEvents(fileInput, Event.ONCHANGE);
Event.setEventListener(fileInput, event -> handleFileUpload());

private void handleFileUpload() {
JavaScriptObject files = fileInput.getPropertyJSO("files");

if (files instanceof JsArray) {
JsArray filesArray = 
(JsArray)files;

if (filesArray.length() > 0) {
handleFileUploadJS(filesArray.get(0),  fileData -> 
handleAfterFileUpload(fileData));
}
}
}

private static native void handleFileUploadJS(JavaScriptObject fileData) 
/*-{
var fileReader = new FileReader();
fileReader.addEventListener("load", function () {
// Your file data will be in fileReader.result
}, false);
fileReader.readAsDataURL(fileData);
}-*/;
-

No server code needed.  :)

On Wednesday, 12 October 2022 at 9:24:41 pm UTC+11 system.out...@gmail.com 
wrote:

> For file upload we are using GXT FileUploadField.
> for server we are using servlets that extends GWT RemoteServiceServlet
> There's a UploadExcelHandler that on success send. a notification. It uses 
> puremvc4gwt.
> We have a handle notification that gets the received data and calles 
> methods to update the grid and reload it 
> ( please read my last message for the reload, I found the root cause but 
> no solution is found yet)
> Thanks
> Le mercredi 12 octobre 2022 à 11:59:26 UTC+2, system out a écrit :
>
>> Yes we are using GXT 2.2.5 with GWT 2.8.1
>> We have a custom Grid object created that has an EditoGrid, 
>> PagingToolbar, ListStore, ColumnModel and many other properties like 
>> height..
>> I found that the problem is caused by the load method inside the 
>> PagingLoader.
>> we have this line: 
>> grid.reconfigure(store, grid.getColumnModel())
>> then the following line that causes the error:
>> loader.load(config).
>> config is a PagingLoadConfig
>> I tried loader.load() and loader.load(0.50) and 
>> grid.getStore().getLoader().load()
>> but nothing seems to work.
>>
>> Le mardi 11 octobre 2022 à 18:57:04 UTC+2, t.br...@gmail.com a écrit :
>>
>>> It would certainly help if you provided details on how you do the upload 
>>> (using GWT's own FormPanel and FileUpload? or a third-party library? 
>>> GXT-specific widgets?) and how you handle the response (including how you 
>>> generate it server-side)
>>> For example, see the note at 
>>> https://www.gwtproject.org/javadoc/latest/com/google/gwt/user/client/ui/FormPanel.html#FormPanel--
>>>  
>>> about server-side requirements.
>>>
>>> On Tuesday, October 11, 2022 at 4:17:27 PM UTC+2 system.out...@gmail.com 
>>> wrote:
>>>
 I managed to print results on client side. I use alerts to chek.
 The list is received as it is, we have a method that will fill the grid 
 with that list but somethiing is stopping it. It still print a loading 
 spinner that never stops. 
 The same code works well with gwt 2.4/gxt 2.2.5.
 Now we are using gwt 2.8/gxt 2.2.5

 Le lundi 10 octobre 2022 à 21:04:58 UTC+2, system out a écrit :

> I migtated gwt app from 2.4 to 2.8
> After fixing build erros the app launches and interfaces are appearing.
> We have a excel file upload.
> When I click upload it is stuck on loading. A loading text appears and 
> result never shows up.
> There a method that takes data imported from excel and put fill some 
> objects with it.
> The data is well imported. The method that fill objects with it will 
> return the filled objects as a List. When I return an empty list it works.
> Do you know if there's something that should be changed due to the 
> migration?
>
>

-- 
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/7987c8a0-8cf6-43d9-b5cb-b0ac9784d54bn%40googlegroups.com.


Re: getThreadLocalRequest.getSession null

2022-10-05 Thread Craig Mitchell
1. Don't use IE.  It's a deprecated browser, and GWT no longer supports 
it.  However, that's unlikely to be your problem.

2. It's still not clear what you're doing.  I suspect you are running the 
servers independently with different URLs, and not active-active behind a 
router.

3. Depending on your Web Server, you usually should see your session id in 
a cookie, not in a post message.  I'm actually not sure how Chrome shows 
you the cookie transmission in the dev tools, I don't think it does.


On Saturday, 1 October 2022 at 12:23:04 am UTC+10 dhia.xd...@gmail.com 
wrote:

> Thanks for your responses.
> I still didn't find a solution. We have reinstalled tomcat but nothing's 
> changed.
> @Jens I debbuged in DevTools and found that for the server A, there is a 
> Post request containing a sessionId sent to it and intercepted by the 
> service containing both methods. The same request is sent to the server B 
> but doesn't contain a sessionId. I still didn't understand why. The same 
> app is deployed and by the way we can only are using IE to access web pages.
> So The sessionId is sent from both servers to the front. But only sent 
> back to server A.
>
> @Craig both servers are working and active.I have no idea about session 
> replication, how do I check that?
>
> This is for sure related to the server, it must be some config or maybe a 
> security config? 
> Le vendredi 30 septembre 2022 à 03:50:53 UTC+2, ma...@craig-mitchell.com 
> a écrit :
>
>> Your question lacks some details.  You talk about two servers, but don't 
>> tell us if they are active-active, or just running one server at a time.
>>
>> If they are active-active, we'd need to know how you are doing your 
>> session replication between then servers.
>>
>> If you are only running one server at a time, then Jens reply is a good 
>> idea.
>>
>> I personally prefer to handle sessions myself, with a cookie and a 
>> memcache (yes, not really sessions at all), so I can easily scale.  But 
>> that's just a little side note.  :)
>>
>> Either way, this outside of GWT's responsibilities, but still happy to 
>> help.
>>
>> On Thursday, 29 September 2022 at 6:24:33 pm UTC+10 Jens wrote:
>>
>>> Use your browser dev tools to inspect the network request. You should 
>>> check if server B sends back a session id cookie and that this session id 
>>> cookie is transmitted back to the server for the second method that does 
>>> getSession(false). If it doesn't or the session is already invalidated 
>>> (either through code or through session timeout configuration on server B) 
>>> then getSession(false) will return null.
>>>
>>> -- J.
>>>
>>> dhia.xd...@gmail.com schrieb am Mittwoch, 28. September 2022 um 
>>> 12:21:36 UTC+2:
>>>
>>>> I have a gwt app that is running when deployed on tomcat on server A
>>>> For some reason the same app when is deployed on tomcat on a server B 
>>>> has a session issue
>>>>
>>>> We have Method 1 and Method 2 inside a servlet that extends 
>>>> RemoteServiceServlet
>>>>
>>>> We have a method1 in which we do:
>>>> this.getThreadLocalRequest.getSession(true).setAttribute("myuserid", 
>>>> myuserid)
>>>>
>>>> Then in a second method we do
>>>> this.getThreadLocalRequest.getSession(false).getAttribute("myuserid")
>>>> which throws a null pointer exception as getSession retuns null
>>>>
>>>> It is strange as this only happens on the server B
>>>> I have verified the tomcat config files like context.xml files and they 
>>>> are identical
>>>>
>>>> I have printed currentThread.gtId() inside both methods and they are 
>>>> different but as said no issue on server A.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>

-- 
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/9f59149c-58fe-4a98-b074-adced408669dn%40googlegroups.com.


Re: getThreadLocalRequest.getSession null

2022-09-29 Thread Craig Mitchell
Your question lacks some details.  You talk about two servers, but don't 
tell us if they are active-active, or just running one server at a time.

If they are active-active, we'd need to know how you are doing your session 
replication between then servers.

If you are only running one server at a time, then Jens reply is a good 
idea.

I personally prefer to handle sessions myself, with a cookie and a memcache 
(yes, not really sessions at all), so I can easily scale.  But that's just 
a little side note.  :)

Either way, this outside of GWT's responsibilities, but still happy to help.

On Thursday, 29 September 2022 at 6:24:33 pm UTC+10 Jens wrote:

> Use your browser dev tools to inspect the network request. You should 
> check if server B sends back a session id cookie and that this session id 
> cookie is transmitted back to the server for the second method that does 
> getSession(false). If it doesn't or the session is already invalidated 
> (either through code or through session timeout configuration on server B) 
> then getSession(false) will return null.
>
> -- J.
>
> dhia.xd...@gmail.com schrieb am Mittwoch, 28. September 2022 um 12:21:36 
> UTC+2:
>
>> I have a gwt app that is running when deployed on tomcat on server A
>> For some reason the same app when is deployed on tomcat on a server B has 
>> a session issue
>>
>> We have Method 1 and Method 2 inside a servlet that extends 
>> RemoteServiceServlet
>>
>> We have a method1 in which we do:
>> this.getThreadLocalRequest.getSession(true).setAttribute("myuserid", 
>> myuserid)
>>
>> Then in a second method we do
>> this.getThreadLocalRequest.getSession(false).getAttribute("myuserid")
>> which throws a null pointer exception as getSession retuns null
>>
>> It is strange as this only happens on the server B
>> I have verified the tomcat config files like context.xml files and they 
>> are identical
>>
>> I have printed currentThread.gtId() inside both methods and they are 
>> different but as said no issue on server A.
>>
>>
>>
>>
>>
>>

-- 
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/d28d88a6-ba48-41c5-b57a-3ffaefac1723n%40googlegroups.com.


Re: GWT 2.10.0 DTD

2022-09-13 Thread Craig Mitchell
It's also included in the GWT SDK:




On Friday, 9 September 2022 at 5:26:53 am UTC+10 lofid...@gmail.com wrote:

> You're right, GWT Project updates with https now but still I also cannot 
> download it:
>
> https://gwtproject.org/doctype/2.10.0/gwt-module.dtd
>
> But I never use it, or do you really need it?
> Sara Youssef schrieb am Donnerstag, 8. September 2022 um 13:25:43 UTC+2:
>
>> I can't access GWT 2.10.0 DTD from 
>> http://gwtproject.org/doctype/2.10.0/gwt-module.dtd
>> So is there any reason that DTD isn't uploaded to gwt website till now 
>> although the source repository has a version of it or it's uploaded to a 
>> different server?
>>
>

-- 
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/4009cf3c-d2b8-4f8d-94a4-7b5b18fb3963n%40googlegroups.com.


Re: GWT 2.10.0 with WildFly 26.

2022-08-04 Thread Craig Mitchell
src="../gemsInquiry/gemsInquiry.nocache.js" doesn't look correct.  Are you 
sure it shouldn't be src="/gemsInquiry/gemsInquiry.nocache.js"?

So instead of:
http://localhost:8080//gemsInquiry/gemsInquiry.nocaches.js

you would have:
http://localhost:8080/gemsInquiry/gemsInquiry.nocaches.js

On Wednesday, 3 August 2022 at 11:30:29 pm UTC+10 parthib...@gmail.com 
wrote:

>  I am using *Java 17 *and *GWT 2.10.0*. For deploy I am using *WildFly 26*. 
> I Can able to deploy my application successfully but when did I open url 
> getting  *gemsInquiry.nocaches.js file not generated *
>
>
>
>
> * language="javascript"src="../gemsInquiry/gemsInquiry.nocache.js">GET 
> http://localhost:8080//gemsInquiry/gemsInquiry.nocaches.js 
>  404 (Not 
> Found)*
>
> gemsInquiry.nocaches.js file not generated so I am facing 404 ERROR
>
>  *How shall I run my application into WildFly 26?*
>
> Regard, 
> Parthiban Chelladurai.
>

-- 
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/1b62af54-f1f9-4835-927d-5f90ab1c03cbn%40googlegroups.com.


Re: Old system in GWT 1.4.61

2022-07-25 Thread Craig Mitchell
Chrome is pretty good at telling you why it's not happy.  What does it say 
in the console?

There was no super dev mode back then, and the GWT plugin won't work in 
Chrome, so any changes you make will need a full compile and deploy each 
time to test them.

On Tuesday, 26 July 2022 at 2:59:07 am UTC+10 nilo...@gmail.com wrote:

> There is no explicit "Chrome" support in GWT - Chrome started its life as 
> another browser based around the WebKit engine. This is referred to in GWT 
> as "safari", though WebKit started its life as part of the Konqueror 
> browser, which pre-dates Safari's use of it (though arguably Safari 
> popularized it).
>
> Oddly, GWT 1.4.61 isn't even listed on 
> https://www.gwtproject.org/release-notes.html, but your build is probably 
> from about Aug 2007. According to Wikipedia, Chrome was first released in 
> September 2008, and the last GWT 1.x release was made in September 2009, as 
> GWT 1.7.1 (see 
> https://www.gwtproject.org/release-notes.html#Release_Notes_1_7_1). If 
> the issue is merely that there are some specific changes in the Chrome 
> product (as opposed to Safari) that need minimal updates, that might be 
> enough, and should be a very small change to your project (while still 
> requiring an ancient version of Java, and platform-specific code to debug). 
> The release notes should help in understanding what changes might be 
> necessary.
>
> With that said, I would be very surprised if the issue is simply that 
> Chrome isn't supported by old versions of GWT, but more likely that some 
> change happened in the last 15 years since GWT 1.4.61. Very likely GWT had 
> the fix before Chrome introduced the breaking change, but without specifics 
> of the actual issue you are facing, I couldn't guess further.
>
> Can you give some specifics about what is not working, what error, logs, 
> and behavior you are seeing? Have you tried updating as far as GWT 1.7 or 
> some other early 2.x release to see if a simple update can keep your 
> project building but still resolve this?
>
>
>
> On Monday, July 25, 2022 at 10:50:45 AM UTC-5 marian...@gmail.com wrote:
>
>> Hi Guys
>>
>> got an old system running in 1.4.61 that won't work in chrome.
>>
>> This is a very complicated and old system that no one really knows about.
>>
>> I am trying to do the minimum changes to get it to work with chrome.
>>
>> Obvisouly the newer the GWT, the more breaking changes potentially 
>> introduced plus the backend will require java upgrade, so it will trigger a 
>> number of changes that I do not want to do, due to the reasons above.
>>
>> Anyone knows when GWT first started supporting chrome?
>>
>> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/24187611-d60e-4c3f-b5c1-9ecd6cd5a3fdn%40googlegroups.com.


Re: [WARN] 404 - GET //10.14.0.224:8888/sampleapp/sampleapp.nocache.js

2022-07-19 Thread Craig Mitchell
I thought you had to put a "-bindAddress 0.0.0.0" to get access to your 
actual IP address.

Have you tried accessing it from http://127.0.0.1:/ ?

On Wednesday, 20 July 2022 at 12:32:02 am UTC+10 frank.h...@googlemail.com 
wrote:

> Inside your module descriptor, is the rename-to attribute of the module 
> tag also "sampleapp"?
>
> abhiy...@gmail.com schrieb am Montag, 18. Juli 2022 um 19:18:00 UTC+2:
>
>> Hello Everyone,
>>
>> I am getting below error when trying to start application through GWT 
>> plugin in eclipse. I am using GWT 2.9.0. I have renamed my module to 
>> *sampleapp 
>> *and in the html file I have used the below script in html file
>> * *
>>
>> 07:18 20:56:17 |  INFO | [main] | 
>> org.eclipse.jetty.server.handler.ContextHandler:doStart(824) | Started 
>> c.g.g.d.s.j.WebAppContextWithReload@238d3e2d{}
>> 07:18 20:56:18 |  INFO | [main] | 
>> org.eclipse.jetty.server.AbstractConnector:doStart(330) | Started 
>> ServerConnector@6e4484d6{HTTP/1.1,[http/1.1]}{0.0.0.0:}
>> 07:18 20:56:18 |  INFO | [main] | 
>> org.eclipse.jetty.server.Server:doStart(399) | Started @32366ms
>> *[WARN] 404 - GET //10.14.0.224:/ * 
>> *sampleapp**/**sampleapp**.nocache.js (10.14.0.224)*
>>Request headers
>>   Host: 10.14.0.224:
>>   Connection: keep-alive
>>   User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) 
>> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36
>>   Accept: */*
>>   Referer: http://10.14.0.224:/sampleapp.html
>>   Accept-Encoding: gzip, deflate
>>   Accept-Language: en-US,en;q=0.9
>>Response headers
>>   Cache-Control: must-revalidate,no-cache,no-store
>>   Content-Type: text/html;charset=iso-8859-1
>>
>

-- 
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/cf04a5d4-d0bf-4c33-913c-6a2f3f302b78n%40googlegroups.com.


Re: Your src appears not to live underneath a subpackage called 'client',but you'll need to use the directive in your module to make it accessible

2022-07-07 Thread Craig Mitchell
I had never seen the "Facet Settings" menu in my GWT settings (as the 
videos show).  After digging around, I realised I didn't have this checked:

[image: Screenshot 2022-07-08 101601.png]

Then it appeared!

Unfortunately, it still didn't launch my code server automatically.  
However, this could be because I'm using the Google App Engine (GAE) server 
(not Tomcat).

I suspect it wouldn't work even if it did start automatically, as GAE 
doesn't pick up file changes once running, so the GWT Code Server would 
need to start first, update the nocache.js file, and only then could the 
GAE start.

I'll keep starting it manually.  Not much hassle really.  :-)

On Thursday, 7 July 2022 at 11:35:15 pm UTC+10 t.br...@gmail.com wrote:

> On Tuesday, July 5, 2022 at 1:58:03 AM UTC+2 abhiy...@gmail.com wrote:
>
>> 2) Also is there any documentation on how to use external servlet 
>> container along with super dev mode in eclipse plugin 
>>
>>
> IIRC, the videos at 
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html
>  
> cover this 
>

-- 
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/d2bb26cf-641e-4314-bcf4-aabe5e642420n%40googlegroups.com.


Re: Your src appears not to live underneath a subpackage called 'client',but you'll need to use the directive in your module to make it accessible

2022-07-05 Thread Craig Mitchell
As I understand it, you don't need the -noServer flag, you just run the 
code server (not DevMode):
[image: Screenshot 2022-07-06 135501.png]

That needs a -launcherDir to tell it where to generate the nocache.js (that 
nocache.js will contain the url to your codeserver, by default running on 
port 9876).

Then you start your Tomcat server, and point your browser to that.

On Tuesday, 5 July 2022 at 9:58:03 am UTC+10 abhiy...@gmail.com wrote:

> Hi Jen & Thomas,
>
> I was able to resolve that issue but now I am stuck at a different issue.
>
> Now my project structure related to webapp is below as folllows:
>
> MavenProjectName
>
> src/main/webapp
>   gxt -> Some folder and files 
>   js  -> Some folder and files '
>  index.html
>  proj.css
> src/main/webapp/WEB-INF
>  web.xml   -> Some servlets, their mappings and index.html 
> in welcome-file-list tag
>
> Scenario 1)
> Now If I start codeserver then from the GWT eclipse plugin then it does 
> not allows me to use  -noServer flag and it gives me a url 
> *http://127.0.0.1:9876/ 
>  *after starting super dev mode 
> and then displays message*:* *Visit a web page that uses one of these 
> modules*
> After selecting one of the link it displays a empty page on the browser 
> and in the logs 
> GET /nos/js.nocache.js
>Sent error page: not found:
>
> Scenario 2)
> Now if I run super dev mode from gwt eclipse plugin then it gives me an 
> ClassNotFoundError for javax.sql.datasource
> 1)So is my folder structure correct to dispay the application host page ?
> 2) Also is there any documentation on how to use external servlet 
> container along with super dev mode in eclipse plugin 
>
> Can you let me know on this issue
>
>
>
>
>
>
> On Saturday, July 2, 2022 at 1:52:47 PM UTC+5:30 t.br...@gmail.com wrote:
>
>> I suppose you've changed the way you call SuperDevMode to pass it 
>> com.cname.proj.client.Main too: SuperDevMode expects the module name, not 
>> the entrypoint class name. So you'd give SuperDevMode com.cname.proj.Main 
>> (which is the name of the Main.gwt.xml), in which it'll find the entrypoint 
>> class name.
>>
>> On Saturday, July 2, 2022 at 2:05:54 AM UTC+2 abhiy...@gmail.com wrote:
>>
>>> Hi Jen, 
>>>
>>> I have changed my entry point to 
>>> class='com.cname.proj.client.Main. But now super devmode is  now giving 
>>> me an error not able to find com/cname/proj/client/Main.gwt.xml in the 
>>> classpath. It forces me to keen Main.gwt.xml and Main.java in the same 
>>> folder/package and then it is giving me forgot to inherit some module 
>>> error. 
>>>
>>>
>>>
>>> Thanks & Regards,
>>> Abhishek Yadav 
>>>
>>> On Sat, Jul 2, 2022, 2:05 AM Jens  wrote:
>>>

 Content in Main.gwt.xml 
>  
> 
>  
>  
> 
> 
>
> 
> 
> 
> 
>
 With that configuration the GWT compiler can see packages 
 com.cname.proj.client and com.cname.proj.service in your main project. 
 However your entry point is not in any of these packages. You need to move 
 the entry point into the client package and update the  
 accordingly.

 -- J.

 -- 
 You received this message because you are subscribed to the Google 
 Groups "GWT Users" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to google-web-tool...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-web-toolkit/16e5b1a9-dd3b-4403-bf76-973d0370d51an%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/1fc9d8a3-28a0-4a59-87ce-cd9baf41137fn%40googlegroups.com.


Re: GWT 2.10.0 release

2022-06-24 Thread Craig Mitchell
Fantastic work!  Installed it, and everything worked first go.  Well done 
all, and thank you!

-- 
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/9535458b-f1a9-4850-9681-3eaacd7d4f7en%40googlegroups.com.


Re: Is there an easy way to use GWT Request Factory?

2022-05-24 Thread Craig Mitchell
I'm using GWT-RPC, and it works great!

I have a version number (that is used by the client and server) that I 
update when I make a breaking RPC change.  If the client detects it has a 
different version number to the server, it shows the user a message that 
they need to refresh their browser, as a new version has been released.

Probably not the optimum solution, but it works fine for my needs.

On Wednesday, 25 May 2022 at 8:15:50 am UTC+10 hprc wrote:

> thank you for the advice
> I have a poor understanding of Maven, so I can only add functionality in 
> the basic way.
>
> I know myself
> 1 Build and run using Eclipse and GWT plugin
> 2 Add jar to build path
> 3 Add by adding  tag
>
> If you prefer, it would be helpful if you could download the jars you need 
> for domino-rest.
>
> 2022年5月24日火曜日 22:16:47 UTC+9 frank.h...@googlemail.com:
>
>>
>> You can use domino-rest without using maven. But Maven will make things 
>> much easier.
>>
>> There are several examples demontrating the use of the Domino-Stack 
>> (including domino-rest) Also, in most cases, it does not depend on Eclipse. 
>> F.e.: check: 
>> https://github.com/NaluKit/nalu-examples/tree/main/nalu-complex-app-example. 
>> This example demonstrate how to do things in Nalu. This example uses 
>> domino-rest for the communication. (I am pretty sure Ahmad & Rafat have 
>> similar examples using the domino stack). Just follow the instructions 
>> inside the readme.txt. All you need to do is to install Java and Maven and 
>> make it available from your terminal. 
>>
>>
>> hprc schrieb am Dienstag, 24. Mai 2022 um 02:15:12 UTC+2:
>>
>>> Re [domino-rest]
>>> It's a great API, you can use POJO and REST respectively.
>>> However, I don't know how to use ECLIPSE + GWT + MOVEN, so it's sad that 
>>> I can't use it right away.
>>>
>>

-- 
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/782f571c-7389-4eff-9804-95dbd1c419fen%40googlegroups.com.


Re: GWT Java Full Stack Developer Job

2022-05-12 Thread Craig Mitchell
There was a group for job listings, but I think it's now gone.  I'd say go 
for it (but I'm not an admin).

On Thursday, 12 May 2022 at 3:21:25 pm UTC+10 Thomas wrote:

> Hi all,
> Would it be ok to post a job ad for a GWT Java Full Stack Developer Job 
> here?
>
> Thanks,
> Thomas
>

-- 
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/04b266eb-6a4d-4457-894e-8e591cfa2536n%40googlegroups.com.


Re: GWT Eclipse Plugin is not compatible with Eclipse 2022-03

2022-05-03 Thread Craig Mitchell
I'm on Eclipse 2021-09 (4.21.0) and it works fine.

However, after this version, the Google plugin stops working  
https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3659  so 
I haven't tried later versions.

On Monday, 2 May 2022 at 11:17:23 pm UTC+10 eliasbala...@gmail.com wrote:

> Until Eclipse 2021-03 (4.19) the GWT Eclipse Plugin is still working.
>
> Under Eclipse 2022-03, the preferences page, the GWT Development view and 
> the run configurations are not accessible.
>
> This is crucial for certain teams relying on GWT Eclipse Plugin for 
> running applications from within the Eclipse IDE and locks users to Eclipse 
> 2021-03 permanently, unless this can be fixed.
>
>

-- 
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/ea47cd3e-32e8-4590-a4f8-d76c5a89a416n%40googlegroups.com.


Re: URGENT: GWT build crash with out of memory

2022-04-07 Thread Craig Mitchell
That's the only reason I use split points, to speed up load times.  I split 
the admin pages, from the public pages, so the public don't need to d/l all 
the admin JS.

On Sunday, 3 April 2022 at 3:32:01 am UTC+10 leon.p...@gmail.com wrote:

> tbh, I've never worked with split points before. 
> What would be the actual problem be if splitpoints are not used - besides 
> from the initial load times?
>
>
> Op vrijdag 1 april 2022 om 17:46:40 UTC+2 schreef nilo...@gmail.com:
>
>> Split points are amazingly expensive to compute (in both CPU and memory) 
>> - I would definitely remove all split points currently under 10KB, and 
>> strongly consider removing all under 100KB, at least for an application of 
>> that size. Odds are excellent that your 4043KB file is your "leftovers" 
>> split point (you can confirm this by checking if the name of the file is 
>> the largest number in that directory) - if so, it is quite possible that 
>> removing other tiny split points will decrease the size of the leftovers 
>> and increase the size of the other larger split points. It may increase the 
>> initial download size as well, which could tell you that it could be wise 
>> to carefully put some back, but taking care to merge related split points 
>> (for example, using GWT.runAsync(Class, RunAsyncCallback) to tell the 
>> compiler that more than one RunAsyncCallback should be merged as the main 
>> file).
>>
>> Consider the order that your files must load in order for the application 
>> to start up - first, the 1.7MB file loads, and the app is usable until the 
>> first split point loads. Does that first split point load instantly? Does 
>> more than one load right away before the app can be used? Consider merging 
>> those split points, or entirely removing them, if they don't provide some 
>> concrete benefit (like allowing the user to start logging in while the rest 
>> of the app is still downloading, etc).
>>
>> Next, before the very first split point can be loaded, the "leftovers" 
>> split point is loaded - the split point with the biggest number, in your 
>> case this would be 756.cache.js (as of your last message). This must be 
>> downloaded and run before any other split point can be loaded - if this is 
>> your biggest one by a factor of of almost 10, it might not even make sense 
>> to have more than a handful of split points, unless you can find a way to 
>> bring that leftover size down, or possible merge it into the initial split 
>> point.
>> On Friday, March 4, 2022 at 8:08:11 AM UTC-6 viny...@gmail.com wrote:
>>
>>> First of all we are very-very thankful to VIE, FRANK & JENS for their 
>>> valuable suggestions and are sorry for late reply. As we were busy in 
>>> applying the solutions suggested by you people.
>>>
>>> *AS THE RESULT:-*
>>> 1. As we have already using "*gwt.compiler.jvmargs=-Xmx61440m*" so we 
>>> could not get what VIE mean to say.
>>> 2. As per the suggestion of FRANK we change the logLevel and got the 
>>> error details and found that some server side classes has been used eg:
>>>  "*Line 18: No source code is available for type 
>>> java.util.regex.Pattern; did you forget to inherit a required module?"*
>>> *  We solved the bugs one-by-one BUT this also not resolved our 
>>> primary problem*. 
>>> 3. As per the suggestion of JENS
>>>  3.1. We used  -optimize *BUT this also not resolved our primary 
>>> problem*. 
>>>  3.2. We tried to lower down the split points by 100. As we get near 
>>> to 756 *.cache.js files. The code started to compile in 35-40 minutes. 
>>> *   So! the split points were the culprit.*
>>>
>>>
>>> *Now our war file is compiling in 30-40 minutes and we are planning to 
>>> lower down the split points more.*
>>>
>>> *WE ARE VERY THANKFULL TO ALL OF YOU. AS YOUR VALUABLE SUGGESTION HAD 
>>> SAVED US.*
>>>
>>> On Thursday, March 3, 2022 at 6:03:27 AM UTC+5:30 Jens wrote:
>>>
 As already said the first thing you should do is to use -strict. This 
 makes sure GWT compiler does not ignore compile errors. Given you have 12 
 compile errors, you want to fix them first.

 Next it looks like you have a lot of split points if you have 856 
 *.cache.js files. Given that 817 of these files are less than 100kb and 
 these files are usually gzipped by the web server before transferring to 
 the client browser, you should try to reduce the amount of split points. I 
 could imagine that analyzing the code for split point calculation might be 
 the culprit.

 There is also an -optimize option for the GWT compiler with values 0 - 
 9 (0 = no optimizations, 9 = aggressive). I don't recall the default value 
 but if it is 9 then it will do an optimize loop on the code AST until the 
 AST does not change anymore. In rare cases this can end up in an endless 
 loop. Using -optimize 8 usually fixes the issue as the compiler will do at 
 most 8 optimize loops then. So you might want to try 

Re: GWT 2.9, JDK 11 and Tomcat

2022-03-21 Thread Craig Mitchell
(2) As we can only use JS debugger, it will only show javascript variable 
name.

Also, you should see the Java variable name, as well as the Java code, but 
in the Chrome JS debugger.  GWT uses source maps to map them together.

On Tuesday, 22 March 2022 at 9:19:29 am UTC+11 Craig Mitchell wrote:

> >  GWT documentation, it suggested to use "noserver" for DevMode launcher 
> argument
> I don't see that in the doco:  
> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/devmodes/CodeServer.html
>
> > (1)
> This is outside of GWTs responsibility.  Sounds like you have an Eclipse / 
> Log4j / Tomcat config issue.
>
> > (2)
> To watch a variable, just use Chromes debugger:  
> https://developer.chrome.com/docs/devtools/javascript/reference/#watch
>
> Use log, use GWT.log("...") to log messages when running in dev.
>
> To log messages in production, you'd need something like this:
>
> public static native void log(String log) /*-{
> $wnd.console.log(log);
> }-*/;
>
> Hope this helps.  :)
>
> On Tuesday, 22 March 2022 at 7:12:54 am UTC+11 jiny...@gmail.com wrote:
>
>> Craig, 
>>
>> Thanks very much for your help! After I changed the launcherDir value to 
>> the path of my war file location as you suggested, the problem got solved. 
>> I can run the application in super dev. mode with GWT 2.9, JDK 11 and 
>> Tomcat 9. 
>>
>> -launcherDir C:\Users\jiny\gitCodeServer\aries\war
>>
>> The reason I chose previous deployment path is that in the GWT Video it 
>> suggested to use wtp.deploy arg + context path for the launchDir value.
>>
>> The thing I'm still a bit puzzled is that in GWT documentation, it 
>> suggested to use "noserver" for DevMode launcher argument, but I didn't add 
>> this option to the DevMode configuration. It still works to use GWT 
>> Development Mode after running the Tomcat server. The  launcherDir is added 
>> to the GWT Development Mode(CodeServer) launcher configuration. It would be 
>> great that you help explain a bit.
>>
>> During the process of running and debugging the application in this 
>> updated environment, I have two questions and hope they can be clarified:
>>
>> (1) Is there anyway to show log4j debugging information in the "Console" 
>> view in Eclipse? After the application is compiled and loaded, the logging 
>> information is removed and it only shows blank window with "Aries(1) 
>> [launch Chrome]".
>>
>> (2) As we can only use JS debugger, it will only show javascript variable 
>> name and we used to use "Watch" to check expression value, but we don't 
>> have this option any more. 
>>  Java System.out message can no longer be displayed in the console.  Any 
>> tips for debugging in the super dev. mode?
>>
>> Your help is greatly appreciated!
>> Jenny
>> On Saturday, March 19, 2022 at 12:50:39 AM UTC-5 Craig Mitchell wrote:
>>
>>> It sound like your GWT code server launcher directory setting isn't 
>>> correct.  And it doesn't look correct either.  It should be the war 
>>> directory of your project.
>>>
>>> So, something like "c:\whereever_your_code_is\your_project\war" (you 
>>> might not have called it "war", it's called whatever you put in the 
>>> settings in GWT -> Web Application -> WAR directory).
>>>
>>> Basically, the GWT code server needs to override the 
>>> (your_module).nocache.js file, so it need to know where that is, and that 
>>> is in a directory under your war directory.
>>>
>>> On Friday, 18 March 2022 at 9:59:04 am UTC+11 jiny...@gmail.com wrote:
>>>
>>>> Hello,
>>>>
>>>> Recently, I started to resume on our GWT upgrade project with GWT 2.9 
>>>> and JDK 11.
>>>>
>>>> As it has been discussed before, the embedded Jetty server can't work 
>>>> with JDK 11 due to the ASM lib version issue. The recommended approach is 
>>>> to set up an external server, so I followed the following GWT document to 
>>>> manually configure GWT development mode by following steps specified in 
>>>> the 
>>>> second Video. I've watched the video and tried this approach many times, 
>>>> but it still gave 404 error. It seems hard to setup external server and 
>>>> configure Development mode correctly for our project.
>>>>
>>>> Any input or suggestion is greatly appreciated!
>>>>
>>>> *http://gwt-plugins.github.io/documentation/gwt-eclipse-plug

Re: GWT 2.9, JDK 11 and Tomcat

2022-03-21 Thread Craig Mitchell
>  GWT documentation, it suggested to use "noserver" for DevMode launcher 
argument
I don't see that in the 
doco:  
http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/devmodes/CodeServer.html

> (1)
This is outside of GWTs responsibility.  Sounds like you have an Eclipse / 
Log4j / Tomcat config issue.

> (2)
To watch a variable, just use Chromes 
debugger:  
https://developer.chrome.com/docs/devtools/javascript/reference/#watch

Use log, use GWT.log("...") to log messages when running in dev.

To log messages in production, you'd need something like this:

public static native void log(String log) /*-{
$wnd.console.log(log);
}-*/;

Hope this helps.  :)

On Tuesday, 22 March 2022 at 7:12:54 am UTC+11 jiny...@gmail.com wrote:

> Craig, 
>
> Thanks very much for your help! After I changed the launcherDir value to 
> the path of my war file location as you suggested, the problem got solved. 
> I can run the application in super dev. mode with GWT 2.9, JDK 11 and 
> Tomcat 9. 
>
> -launcherDir C:\Users\jiny\gitCodeServer\aries\war
>
> The reason I chose previous deployment path is that in the GWT Video it 
> suggested to use wtp.deploy arg + context path for the launchDir value.
>
> The thing I'm still a bit puzzled is that in GWT documentation, it 
> suggested to use "noserver" for DevMode launcher argument, but I didn't add 
> this option to the DevMode configuration. It still works to use GWT 
> Development Mode after running the Tomcat server. The  launcherDir is added 
> to the GWT Development Mode(CodeServer) launcher configuration. It would be 
> great that you help explain a bit.
>
> During the process of running and debugging the application in this 
> updated environment, I have two questions and hope they can be clarified:
>
> (1) Is there anyway to show log4j debugging information in the "Console" 
> view in Eclipse? After the application is compiled and loaded, the logging 
> information is removed and it only shows blank window with "Aries(1) 
> [launch Chrome]".
>
> (2) As we can only use JS debugger, it will only show javascript variable 
> name and we used to use "Watch" to check expression value, but we don't 
> have this option any more. 
>  Java System.out message can no longer be displayed in the console.  Any 
> tips for debugging in the super dev. mode?
>
> Your help is greatly appreciated!
> Jenny
> On Saturday, March 19, 2022 at 12:50:39 AM UTC-5 Craig Mitchell wrote:
>
>> It sound like your GWT code server launcher directory setting isn't 
>> correct.  And it doesn't look correct either.  It should be the war 
>> directory of your project.
>>
>> So, something like "c:\whereever_your_code_is\your_project\war" (you 
>> might not have called it "war", it's called whatever you put in the 
>> settings in GWT -> Web Application -> WAR directory).
>>
>> Basically, the GWT code server needs to override the 
>> (your_module).nocache.js file, so it need to know where that is, and that 
>> is in a directory under your war directory.
>>
>> On Friday, 18 March 2022 at 9:59:04 am UTC+11 jiny...@gmail.com wrote:
>>
>>> Hello,
>>>
>>> Recently, I started to resume on our GWT upgrade project with GWT 2.9 
>>> and JDK 11.
>>>
>>> As it has been discussed before, the embedded Jetty server can't work 
>>> with JDK 11 due to the ASM lib version issue. The recommended approach is 
>>> to set up an external server, so I followed the following GWT document to 
>>> manually configure GWT development mode by following steps specified in the 
>>> second Video. I've watched the video and tried this approach many times, 
>>> but it still gave 404 error. It seems hard to setup external server and 
>>> configure Development mode correctly for our project.
>>>
>>> Any input or suggestion is greatly appreciated!
>>>
>>> *http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html
>>>  
>>> <http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html>*
>>>
>>> Manually Configure GWT Development Mode
>>>
>>> Manually Configuring the -launcherDir in the GWT Eclipse Plugin
>>>
>>> Our GWT project is not Maven oriented and it was developed several years 
>>> ago with a big codebase. 
>>>
>>> Step 1: Converted Aries project to Dynamic Web Project by adding project 
>>> facet "Dynamic Web Module" in Eclipse.
>>>
>>> Step 2: Set up Apache Tomcat 9 Server
>>>
>>> Step 3: Add 

Re: GWT 2.9, JDK 11 and Tomcat

2022-03-18 Thread Craig Mitchell
It sound like your GWT code server launcher directory setting isn't 
correct.  And it doesn't look correct either.  It should be the war 
directory of your project.

So, something like "c:\whereever_your_code_is\your_project\war" (you might 
not have called it "war", it's called whatever you put in the settings in 
GWT -> Web Application -> WAR directory).

Basically, the GWT code server needs to override the 
(your_module).nocache.js file, so it need to know where that is, and that 
is in a directory under your war directory.

On Friday, 18 March 2022 at 9:59:04 am UTC+11 jiny...@gmail.com wrote:

> Hello,
>
> Recently, I started to resume on our GWT upgrade project with GWT 2.9 and 
> JDK 11.
>
> As it has been discussed before, the embedded Jetty server can't work with 
> JDK 11 due to the ASM lib version issue. The recommended approach is to set 
> up an external server, so I followed the following GWT document to manually 
> configure GWT development mode by following steps specified in the second 
> Video. I've watched the video and tried this approach many times, but it 
> still gave 404 error. It seems hard to setup external server and configure 
> Development mode correctly for our project.
>
> Any input or suggestion is greatly appreciated!
>
> *http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/servers/Tomcat.html
>  
> *
>
> Manually Configure GWT Development Mode
>
> Manually Configuring the -launcherDir in the GWT Eclipse Plugin
>
> Our GWT project is not Maven oriented and it was developed several years 
> ago with a big codebase. 
>
> Step 1: Converted Aries project to Dynamic Web Project by adding project 
> facet "Dynamic Web Module" in Eclipse.
>
> Step 2: Set up Apache Tomcat 9 Server
>
> Step 3: Add the project to server. Right click on Server -> Add and Remove
>
> Step 4: Start the Tomcat Server
>
> Step 5: Right click project->Debug As -> GWT Development mode
>
> Step 6. It started fine. Stop it so we can add the -launcherDir Program Arg
>
> Step 7: Double click on Tomcat server, select Open launch configuration
>
>  Get the server web app directory root: wtp.deploy
>
> Copy path
>
>  
> C:\EclipseGWTCodeServerWorkSpace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps
>
> Step 8. Open the file explorer to see the deployment path
>
> Step 9: Go to Debug Configurations
>
> GWT Development Mode (CodeServer)->Arguments.
>
> Add -launcherDir
>
> Value: It is the wtp.deploy arg + context path.
>
> After updated the Argument to GWT Development Mode(CodeServer), the 
> Arguments tab has following content:
>
> -launcherDir 
> C:\EclipseGWTCodeServerWorkSpace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\aries
>  
> -logLevel INFO -port 9876 edu.vanderbilt.mc.aries.ARIES
>
> Step 10 Launch the code server, click on Debug from CodeServer dialog. Now 
> both the Web Server and Code Server are running. Back to the file manager. 
> Watching for the application directory to be created.
>
> Step 11: Launch the browser for debugging with the Javascript Debugging
>
> Open with SBDG debugger
>
> Step 12: Open browser with Code Server URL: 127.0.0.1:9876 and Change the 
> port number to 8080 ( the Tomcat web server port number)
>
> It gave me 404 Not found error.
>
> Your help is greatly appreciated, 
>
> Jenny
>

-- 
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/77678bff-1531-4891-a6b0-8b6aac57e009n%40googlegroups.com.


Re: hilla.dev

2022-03-15 Thread Craig Mitchell
Guilty, I was being a little over simplistic.  :)

Sometimes I love Springboot, Spring Security, etc, and other times I hate 
it.  So I can understand your view there.

I guess I saw the Vaadin web components, Lit framework, Spring, etc, all 
things that you can get standalone.  However, I guess Hilla are packaging 
them up for you to work nicely together, so probably should be considered 
part of it.

On Monday, 14 March 2022 at 9:40:45 pm UTC+11 t.br...@gmail.com wrote:

> I haven't tried it (if only because of Spring) but your description is 
> overly reductive IMO.
> Hilla is made of (at least) 3 parts:
>
>- client-side library of web components (router, form data-binding, 
>data grids, etc.)
>- server-side framework (or only scaffolding?) based on Spring Boot, à 
>la JHipster
>- code generator that takes Java code for your Spring Boot endpoints 
>and generates TypeScript code to call them, and type definitions for 
> direct 
>use with the form data-binding components (the generator actually is 
> itself 
>made of 2 parts: generates an OpenAPI spec from the Spring Boot endpoints, 
>then generates TypeScript from that OpenAPI spec; it doesn't support all 
> of 
>OpenAPI though, as it's tailored for the Hilla backend, wrt authentication 
>for instance).
>
>
> On Monday, March 14, 2022 at 6:07:53 AM UTC+1 Craig Mitchell wrote:
>
>> Has anyone tried https://hilla.dev/ ?  It seems like GWT minus most of 
>> the bits.  Ie: They give you the model in TypeScript, then it's up to you 
>> to do the rest.
>
>

-- 
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/c11be2d6-b39b-4ef3-b9e2-b4cdc4163714n%40googlegroups.com.


hilla.dev

2022-03-13 Thread Craig Mitchell
Has anyone tried https://hilla.dev/ ?  It seems like GWT minus most of the 
bits.  Ie: They give you the model in TypeScript, then it's up to you to do 
the rest.

-- 
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/f6586d05-5b99-4573-a2a6-b103991c3221n%40googlegroups.com.


Re: Performance Comparison GWT Transpiler with MacBook Pro M1 Pro processor

2022-01-13 Thread Craig Mitchell
*>  I haven't been able to get Eclipse to run natively as macOS AArch64 

 is 
only available from the 2021-12 version which just borks my project.  It 
seems to be a conflict with the google-cloud-plugin I use for appengine.*

Same.  It's been reported to 
Google:  
https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3659#issuecomment-1011900580
 

On Thursday, 13 January 2022 at 6:39:12 pm UTC+11 Shawn wrote:

> Just to correct myself ...
>
> I haven't been able to get Eclipse to run natively as macOS AArch64 
> 
>  is 
> only available from the 2021-12 version which just borks my project.  It 
> seems to be a conflict with the google-cloud-plugin I use for appengine.  
> Still 2021-09 with emulated Eclipse is a major improvement especially since 
> the dev server and build processes can be run natively. 
>
>
> Eclipse 2021-12 runs fine with AArch64.  I used the following from the 
> Eclipse Market place which is what caused the trouble — Eclipse m2e - Maven 
> support in Eclipse IDE 
>
> And AArch64 is available before 2021-12 (4.22).  That the first version 
> for a distributed J2EE download though you can get an earlier version and 
> add in J2EE support.
>
> And SDBG debugging still works (debugging in eclipse).  I wasn’t able to 
> build the SDBG for Java 11 anymore (I remember it being easy last time) but 
> was able to use the one I’d previously build.
>
> S
>
>

-- 
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/06f309db-6198-4485-aeb6-6ee312996b23n%40googlegroups.com.


Re: CACHE ISSUES WITH GWT

2021-12-07 Thread Craig Mitchell
This is often because your web server is not handling the nocache files 
correctly:  
https://groups.google.com/g/google-web-toolkit/c/Mb_0PWgrhNI/m/SZ5ZkFQ_CgAJ


On Tuesday, 7 December 2021 at 5:15:02 pm UTC+11 pearla...@gmail.com wrote:

> hello guys i have  an issues with Gwt and using 2.7.0 and also am using 
> smart gwt (6.1) when i make updates  like changing theme colors i get 
> chrome browser have having the old theme colors 

-- 
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/8a6d9f39-f34e-4c17-972e-f8542d367bfcn%40googlegroups.com.


Re: Element type "entry-point" must be declared.

2021-11-26 Thread Craig Mitchell
The DTD is also included with the GWT SDK.  So you can just point it 
there.  Eg:



(change the location path to where you have your GWT SDK)

On Wednesday, 24 November 2021 at 4:01:56 pm UTC+11 manish@gmail.com 
wrote:

> In dtd , www. Was missing. Eclipse issue. 
>
> Adding the same resolved the issue. 
>
> Thanks Thomas for your help.
>
> Regards. Manish
>
>
> On Tue, 23 Nov, 2021, 5:04 pm Thomas Broyer,  wrote:
>
>> Those errors are *only* about the XML DTD validation, but they actually 
>> won't affect GWT itself.
>>
>> It looks like there's a problem with the gwtproject.org site that 
>> doesn't serve the doctype/2.8.1/gwt-module.dtd and instead redirects back 
>> to the home page, breaking XML DTD validation altogether (see that last 
>> error in your screenshot? its the one causing all the others).
>>
>> Because the DTD is useless (it only used to help with autocompletion and 
>> the like in IDEs), I'd suggest removing the > those errors and won't change the GWT behavior in any way.
>>
>> On Tuesday, November 23, 2021 at 11:38:52 AM UTC+1 manish@gmail.com 
>> wrote:
>>
>>> 
>>> 
>>> >> 2.8.1//EN"
>>>   "http://gwtproject.org/doctype/2.8.1/gwt-module.dtd;>
>>> 
>>>   
>>>   
>>>
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>
>>>   
>>>
>>>   
>>>   
>>>
>>>   
>>>   
>>>   
>>>
>>>   
>>>   
>>> 
>>>
>>> I am getting these errors . 
>>> I am new to GWT . 
>>>
>>> Kindly 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-tool...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/a26a546a-34d9-44ef-bc41-47751bf73c79n%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/faab0183-6aa1-48d4-a2dc-a2312475a946n%40googlegroups.com.


Re: Display a list of objects.

2021-11-03 Thread Craig Mitchell
I'm not familiar with the material UI.  However, I can see you're missing 
the "@UiField" on your ListBox declaration.  ie: It should be:
@UiField ListBox canBeusedBy;

Then you call just call "addItem" to add some items into the list.  
See http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwListBox 
for more detail.
On Tuesday, 2 November 2021 at 4:41:25 am UTC+11 tonio@gmail.com wrote:

> Hi, 
> I've been struggling for days to display a list of objects in an editor 
> using UIBinder.
>
> But I can't figure out which class to use and even less how.
>
> Here are some code snippets:
>
> The UIBinder file
> 
> http://dl.google.com/gwt/DTD/xhtml.ent;>
>  xmlns:ui="urn:ui:com.google.gwt.uibinder"
> xmlns:m="urn:import:gwt.material.design.client.ui"
> xmlns:ma="urn:import:gwt.material.design.addins.client"
> 
> xmlns:combobox="urn:import:gwt.material.design.addins.client.combobox"
> xmlns:g="urn:import:com.google.gwt.user.client.ui">
>
> .widget {
>margin: 30px;
>}
> 
>
>addStyleNames="{style.widget}">
> 
> 
> 
> 
> 
>  />
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> 
> 
> 
> 
> 
> 
>   
> 
> 
>
>
>
>
> The Editor Java file
>
> package com.lacen.gwt.spot.client.ui.mvp.editors.generated;
>  import com.google.gwt.core.client.GWT;
>  import com.google.gwt.editor.client.Editor;
>  import com.google.gwt.editor.client.SimpleBeanEditorDriver;
>  import com.google.gwt.event.dom.client.ClickEvent;
>  import com.google.gwt.uibinder.client.UiBinder;
>  import com.google.gwt.uibinder.client.UiField;
>  import com.google.gwt.uibinder.client.UiHandler;
>  import com.google.gwt.user.client.ui.Composite;
>  import com.google.gwt.user.client.ui.Widget;
>  import com.lacen.event.Event;
>  import gwt.material.design.client.ui.MaterialPanel;
>  import com.lacen.gwt.spot.client.ui.mvp.editors.ComboBoxEnum;
>  import gwt.material.design.client.ui.MaterialDialog;
>  import gwt.material.design.client.ui.MaterialTextBox;
>  import com.google.gwt.user.client.ui.ListBox;
>  import java.util.List;
>  import com.lacen.gwt.spot.client.ui.mvp.editors.ListValueSpot;
>  import com.lacen.users.Stakeholder;
>  import com.lacen.organisation.Action;
>  /**
>  * Create an editor to describe a event.
>  * @author Antonio
>  */
>  public class EventEditor extends Composite implements Editor {
>   /** The Constant driver. */
>   // Editor driver
>   private static final EventDriver driver = 
> GWT.create(EventDriver.class);
>   /**
>   * The Interface EventDriver.
>   */
>   interface EventDriver extends SimpleBeanEditorDriver EventEditor> {
>   }
>   /** The Constant uiBinder. */
>   // UiBinder and fields
>   private static final EventEditorUiBinder uiBinder = 
> GWT.create(EventEditorUiBinder.class);
>   /**
>   * The Interface EventEditorUiBinder.
>   */
>   interface EventEditorUiBinder extends UiBinder {
>   }
>   /** The dialog. */
>   @UiField
>   MaterialDialog dialog;
>   /** The name */
>   @UiField
>   MaterialTextBox name;
>   /** The graphID */
>   @UiField
>   MaterialTextBox graphID;
>   /** The eventStatus */
>   @UiField
>   MaterialPanel MaterialPanelCombo2;
>   ComboBoxEnum eventStatus;
>   /** The relevance */
>   @UiField
>   MaterialPanel MaterialPanelCombo3;
>   ComboBoxEnum relevance;
>   /** The status */
>   @UiField
>   MaterialPanel MaterialPanelCombo4;
>   ComboBoxEnum status;
>   /** The detectability */
>   @UiField
>   MaterialPanel MaterialPanelCombo5;
>   ComboBoxEnum detectability;
>   /** The criticity */
>   @UiField
>   MaterialPanel MaterialPanelCombo6;
>   ComboBoxEnum criticity;
>   /** The canBeusedBy */
>   ListBox canBeusedBy;
>   /** The initial object (Event). */
>   private Event initialObject;
>   /**
>   * Instantiates a new Event editor.
>   */
>   public EventEditor() {
>initWidget(uiBinder.createAndBindUi(this));  Create the UI 
> of the Editor.
>eventStatus = new 
> ComboBoxEnum("eventStatus", 
> com.lacen.event.HandlingProgress.VALUES);
>MaterialPanelCombo2.add(eventStatus.getComboBox());
>relevance = new 
> ComboBoxEnum("relevance", 
> com.lacen.event.Relevance.VALUES);
>MaterialPanelCombo3.add(relevance.getComboBox());
>status = new 
> ComboBoxEnum("status", 
> com.lacen.event.StatusEvent.VALUES);
>MaterialPanelCombo4.add(status.getComboBox());
>detectability = new 
> ComboBoxEnum("detectability", 
> com.lacen.event.Detectability.VALUES);
>MaterialPanelCombo5.add(detectability.getComboBox());
>criticity = new 
> ComboBoxEnum("criticity", 
> 

Re: Performance Comparison GWT Transpiler with MacBook Pro M1 Pro processor

2021-10-28 Thread Craig Mitchell
After Apple threatened me with legal action for writing an Android app, 
I've steered clear of any Apple product.  But, wow, those M1 chips are 
amazing!

On Friday, 29 October 2021 at 9:38:45 am UTC+11 lofid...@gmail.com wrote:

> Hi All,
>
> I wrote a short comparison about GWT Transpiler with MacBook Pro M1 Pro 
> processor.
>
> https://bit.ly/GWTM1ProPerformance
>
> Enjoy!
>
>

-- 
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/79aacccb-46aa-4b19-96e4-e8eb7a5ee833n%40googlegroups.com.


Re: Populating CellTable using ListDataProvider?

2021-10-21 Thread Craig Mitchell
Just to clarify my comment.  I find it easier to use pure HTML + CSS then 
GWT's built in CellTable etc.

Eg:

@UiField TableElement myTable;
TableRowElement row = myTable.insertRow(...);
...

Then you can use all the fancy CSS styles, that others have written to make 
tables look pretty.  No need to mangle them into what GWT wants.

Adding GWT widgets into the table is a little annoying that you need to 
call onAttach to get their events to work, but that's a minor inconvience.

Anyhow, I wasn't suggesting writing any JavaScript.  :)

Also not saying don't use CellTable.  Maybe you have a massive amount of 
data, and all the fancy databinding will save you time in the long run.

On Friday, 22 October 2021 at 2:37:14 am UTC+11 ime...@gmail.com wrote:

> Hi Tomas,
>
> First, pls. let me thank you and the team for the amazing work on GWT.
>
> As for the documentation, I'd say it's lacking an example for importing 
> custom widgets  because the way some of use read the XML. Personally I just 
> automatically skip over the xmls section because it contains "standard" GWT 
> namespaces. 
>
> I think the docs would benefit from explicitly stating
>
>  "To import your own widget com.example.gwt.client.SampeTextField, use the 
> xmlns to add a package with your own packages and then use the prefix in 
> the body of the template. For example:
>
>  xmlns:e='urn:import:com.example.gwt.client'>
>
>   
>
> 
> "
> On Thursday, October 21, 2021 at 4:20:49 AM UTC-7 t.br...@gmail.com wrote:
>
>> Is this 
>> <http://www.gwtproject.org/doc/latest/DevGuideUiBinder.html#Hello_Widget_World>
>>  
>> not enough? Buried too deep? Lacking examples and/or a step-by-step?
>>
>> In order to use a set of widgets in a ui.xml template file, you need to 
>> tie their package to an XML namespace prefix. That’s what’s happening in 
>> this attribute of the 
>> root  element: 
>> xmlns:g='urn:import:com.google.gwt.user.client.ui'. 
>> This says that every class in the com.google.gwt.user.client.ui package can 
>> be used as an element with prefix g and a tag name matching its Java class 
>> name, like .
>>
>> See how the g:ListBox element has a visibleItemCount='1' attribute? That 
>> becomes a call to ListBox#setVisibleItemCount(int) 
>> <http://www.gwtproject.org/javadoc/latest/com/google/gwt/user/client/ui/ListBox.html#setVisibleItemCount-int->.
>>  
>> Every one of the widget’s methods that follow JavaBean-style conventions 
>> for setting a property can be used this way.
>>
>> On Thursday, October 21, 2021 at 6:32:24 AM UTC+2 ime...@gmail.com wrote:
>>
>>> Hey, hey, hey,
>>>
>>> I'm one of us Javascript-deaf. With GWT I'm back to my a screen-a-day in 
>>> pure Java. Just loving it.
>>>
>>> Still, would GWT team be accepting of some PRs to update Javadocs? Took 
>>> me a day of Googling to figure out how to make use of custom widgets in UI 
>>> Binder templates.
>>>
>>> Slava
>>>
>>>
>>> On Wednesday, October 20, 2021 at 7:15:59 PM UTC-7 Craig Mitchell wrote:
>>>
>>>> GWT does many great things.  Implementation of lists and tables wasn't 
>>>> one of them (IMHO).
>>>>
>>>> If GWT 3 ever comes out.  It will be great to have separation of this 
>>>> stuff.
>>>>
>>>> However, to answer your question, yes, it would make sense, I just 
>>>> don't know what the likelihood of a 2.9.1 release is.
>>>> On Tuesday, 19 October 2021 at 2:36:28 pm UTC+11 ime...@gmail.com 
>>>> wrote:
>>>>
>>>>> Folks, 
>>>>>
>>>>> Just following up on what turned to be my own blunder. Using 
>>>>> ListDataProvider doesn't work when the CellTable is created using 
>>>>> pageSize 
>>>>> = 0. 
>>>>>
>>>>> super(0, resources, keyProvider);
>>>>>
>>>>> It still works when using setRowCount(); setRowData();.
>>>>>
>>>>> So I fixed it for the time being by setting a meaningfully large 
>>>>> pageSize.
>>>>>
>>>>> Here is the question: would it make sense to add a bit more to the 
>>>>> Javadoc for pageSize. Or maybe checking for 0 and throwing 
>>>>> IllegalArgumentException?
>>>>>
>>>>> On Friday, September 24, 2021 at 4:44:10 PM UTC-7 Slava Imeshev wrote:
>>>>>
>>>>>> So, I'm following basic examples, and I just cannot get it to work. 
>>>>>

Re: Populating CellTable using ListDataProvider?

2021-10-20 Thread Craig Mitchell
GWT does many great things.  Implementation of lists and tables wasn't one 
of them (IMHO).

If GWT 3 ever comes out.  It will be great to have separation of this stuff.

However, to answer your question, yes, it would make sense, I just don't 
know what the likelihood of a 2.9.1 release is.
On Tuesday, 19 October 2021 at 2:36:28 pm UTC+11 ime...@gmail.com wrote:

> Folks, 
>
> Just following up on what turned to be my own blunder. Using 
> ListDataProvider doesn't work when the CellTable is created using pageSize 
> = 0. 
>
> super(0, resources, keyProvider);
>
> It still works when using setRowCount(); setRowData();.
>
> So I fixed it for the time being by setting a meaningfully large pageSize.
>
> Here is the question: would it make sense to add a bit more to the Javadoc 
> for pageSize. Or maybe checking for 0 and throwing IllegalArgumentException?
>
> On Friday, September 24, 2021 at 4:44:10 PM UTC-7 Slava Imeshev wrote:
>
>> So, I'm following basic examples, and I just cannot get it to work. The 
>> populate() method below using ListDataProvider leaves the table empty. 
>> populateWorking() works. Any hints?
>>
>> public class GapAnalysisListTable extends CellTable {
>>
>> public GapAnalysisListTable() {
>>
>> // Create a data provider.
>> dataProvider = new ListDataProvider<>(GapAnalysisVO::getId);
>>
>> // Connect the table to the data provider.
>> dataProvider.addDataDisplay(this);
>> }
>>
>> public void populate(final GapAnalysisVO[] gapAnalysisVOList) {
>>
>> final List list = dataProvider.getList();
>> list.addAll(Arrays.asList(gapAnalysisVOList));
>> dataProvider.refresh();
>> }
>>
>> public void populateWorks(final GapAnalysisVO[] gapAnalysisVOList) {
>>
>> setRowCount(gapAnalysisVOList.length);
>> setRowData(Arrays.asList(gapAnalysisVOList));
>> }
>> }
>>
>

-- 
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/f6e7df58-a414-4ea7-937f-c7757bee41cen%40googlegroups.com.


Re: Digest for google-web-toolkit@googlegroups.com - 6 updates in 1 topic

2021-10-08 Thread Craig Mitchell
I'm using OpenJDK 8.  https://adoptopenjdk.net/ 

On Saturday, 9 October 2021 at 4:16:17 am UTC+11 james0072 wrote:

> @Craig Mitchell. What version of Java SDK do you use with the eclipse 2021 
> 06. I would like to use the eclipse plugin as well. It has been a long time 
> since I worked with GWT.
>
> On Fri, Oct 8, 2021 at 6:02 AM  wrote:
>
>> google-we...@googlegroups.com 
>> <https://groups.google.com/forum/?utm_source=digest_medium=email#!forum/google-web-toolkit/topics>
>>  Google 
>> Groups 
>> <https://groups.google.com/forum/?utm_source=digest_medium=email/#!overview>
>>  
>> <https://groups.google.com/forum/?utm_source=digest_medium=email/#!overview>
>>  
>> Topic digest 
>> View all topics 
>> <https://groups.google.com/forum/?utm_source=digest_medium=email#!forum/google-web-toolkit/topics>
>>  
>>
>>- GWT Eclipse plug in 
>><#m_-2793253033233777504_m_3463309873041189631_group_thread_0> - 6 
>>Updates 
>>
>> GWT Eclipse plug in 
>> <http://groups.google.com/group/google-web-toolkit/t/50747f3f08a2d472?utm_source=digest_medium=email>
>>  
>> "pierre...@gmail.com" : Oct 07 07:08AM -0700 
>>
>> Thanks Lofi,
>> Yes I agree for the future app but I have legacy apps mixing backend 
>> using 
>> a plugin (no maven) and gwt with shared classes.
>> Migrating to maven will be a major change for 0 benefit if even possible. 
>> At least even the path with this funny /src/main/java for maven will make 
>> both part incompatible.
>> It was easier for me to use an old eclipse version with the 2 plugins and 
>> continue like this until the apps are abandonned. 
>> Pierre
>> "lofid...@gmail.com" : Oct 07 01:19PM -0700 
>>
>> Yes, it always a problem to migrate... 
>>  
>> I've experienced this a long time ago with Ant, which we wanted to move 
>> to 
>> Maven. I created a framework to make the migration from Ant to Maven semi 
>> automatically:
>>  
>> https://github.com/crowdcode-de/MoveToMaven
>>  
>> Maybe I would have some time to implement GWT Ant to Maven migration so 
>> that all those old Ant projects can be transformed into the new Maven 
>> structure... Also to separate the "frontend" from the "backend" part 
>> (best 
>> practice in GWT).
>>  
>> I'm doing some stuffs in migrations / transformations: new 
>> article: https://bit.ly/AppsMigration 
>>  
>> Thanks,
>> Lofi
>>  
>> pierre...@gmail.com schrieb am Donnerstag, 7. Oktober 2021 um 16:08:37 
>> UTC+2:
>>  
>> Craig Mitchell : Oct 07 04:34PM -0700 
>>
>> My project is very simple, so Maven would be an unnecessary complication 
>> for me. The GWT Eclipse plugin works great. Eclipse 2021-06. Windows 10.
>>  
>> "lofid...@gmail.com" : Oct 08 01:47AM -0700 
>>
>> Actually Maven is not complicated... 
>>  
>> A lot more easier than Eclipse Plugin ;-)
>>  
>> ... and you'll become independent from Eclipse or you stay with Eclipse 
>> and 
>> you have the Maven integration directly in standard Eclipse, no need to 
>> install plugin...
>>  
>> OK, in my case all the webapps are managed with CI / CD, so, this is a 
>> must. But I feel also without this requirement, Maven is just better and 
>> easier than doing the stuff manually in IDE.
>>  
>> My 2 cents ;-)
>>  
>> Craig Mitchell schrieb am Freitag, 8. Oktober 2021 um 01:34:18 UTC+2:
>>  
>> Craig Mitchell : Oct 08 03:46AM -0700 
>>
>> A lot easier then going 
>> here 
>> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html, 
>>
>> dragging and dropping the install button, and clicking confirm? I really 
>> don't think so. ;-)
>>  
>> I have used Maven in projects. It's sometimes great, but often not. 
>> Things like it caching the fact that it couldn't find a library, so when 
>> you correct the artifactory, it still says it can't find it, because you 
>> have to clear its cache (which is a nightmare of searching through this 
>> massive .m2 directory). And you have to explicitly tell it it's okay to 
>> get a snapshot library. And don't get me started on the fact that they 
>> didn't even bother creating an installer for it on Windows, you have to 
>> extract the zip, and add the directory to your path manually. *maven rant 
>> over*
>>  
>> Michael Conrad : Oct 08 07:26AM -0400 
>>
>> I vote for Gradle.
>>  
>> On Fri, Oct 8, 20

Re: GWT Eclipse plug in

2021-10-07 Thread Craig Mitchell
My project is very simple, so Maven would be an unnecessary complication 
for me.  The GWT Eclipse plugin works great.  Eclipse 2021-06.  Windows 10.

On Friday, 8 October 2021 at 7:19:34 am UTC+11 lofid...@gmail.com wrote:

> Yes, it always a problem to migrate... 
>
> I've experienced this a long time ago with Ant, which we wanted to move to 
> Maven. I created a framework to make the migration from Ant to Maven semi 
> automatically:
>
> https://github.com/crowdcode-de/MoveToMaven
>
> Maybe I would have some time to implement GWT Ant to Maven migration so 
> that all those old Ant projects can be transformed into the new Maven 
> structure... Also to separate the "frontend" from the "backend" part (best 
> practice in GWT).
>
> I'm doing some stuffs in migrations / transformations: new article: 
> https://bit.ly/AppsMigration 
>
> Thanks,
> Lofi
>
> pierre...@gmail.com schrieb am Donnerstag, 7. Oktober 2021 um 16:08:37 
> UTC+2:
>
>> Thanks Lofi,
>> Yes I agree for the future app but I have legacy apps mixing backend 
>> using a plugin (no maven) and gwt with shared classes.
>> Migrating to maven will be a major change for 0 benefit if even possible. 
>> At least even the path with this funny /src/main/java for maven will make 
>> both part incompatible.
>> It was easier for me to use an old eclipse version with the 2 plugins and 
>> continue like this until the apps are abandonned.  
>> Pierre
>> Le mercredi 6 octobre 2021 à 13:23:28 UTC+2, lofid...@gmail.com a écrit :
>>
>>> The problem is the GWT Eclipse plugin is not maintained anymore, so it 
>>> stops working in the newer versions...
>>>
>>> As I said, I wouldn't use it anymore. Also ant.xml as build tool is 
>>> deprecated. I would just use Maven quite easy.
>>>
>>> Additional to the example above, there are also following examples for 
>>> "StockWatcher GWT Example" but with Maven and newer ways:
>>>
>>> https://github.com/lofidewanto/stockwatcher
>>>
>>> Thanks, Lofi
>>>
>>> pierre...@gmail.com schrieb am Mittwoch, 6. Oktober 2021 um 11:31:01 
>>> UTC+2:
>>>
 Seem to be more an eclipse and constraint environment (Hospital) 
 incompatibility.
 I had to take an older version eclipse 2019-03 and then it's works.
 No idea why but GWT and maven plugin are not broken anymore with this 
 version.

 Le lundi 4 octobre 2021 à 12:06:12 UTC+2, pierre...@gmail.com a écrit :

> Hi,
>
> I am using GWT Eclipse  plug in eclipse 2019-12. 
>
> Afer installing another plugin (JBoss Toosl),  the GWT plugin 
> was  completly broken. 
> I tried many thing remove Jboss - reinstall GWT without success.
>
> Then, I installed a new eclipse + GWT plugin but the result is still 
> the same. 
> GWT plugin is install successfully but nothing from it appears. 
>
> Thanks in avance for any help
>
> Best, Pierre



-- 
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/e2d266e0-fc2e-4231-8b74-c79dc70e32afn%40googlegroups.com.


Re: What setting controls whether Eclipse is building the development version or not?

2021-08-25 Thread Craig Mitchell
Glad you found your issue.  I'm always forgetting to set the "-launcherDir" 
on the code server on a fresh install.  :)

Another thing that trips me up, is when I do a "GWT Compile Project" 
(because I want to deploy my site to test/prod), after I've done that, when 
I start up my code server again, I have to remember, in Eclipse, to publish 
my web server.  This triggers the web server to realise that the 
xxx.nocache.js has been changed after the compile was done.

If I don't do that, when I start my web server, it still has the compiled 
xxx.nocache.js, and then uses the compiled JS, not the code server.

Interested to know if this happens with Tomcat, or it's just a quirk of the 
Google App Engine web server.

On Wednesday, 25 August 2021 at 7:23:13 am UTC+10 mmo wrote:

> Issue solved! 
> Probably due to my experimenting (among them the re-creation of a 
> Server-definition) the CodeServer's launcherDir-path (
> \.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\rwtool-web)
>  
> and the WTP deploy-path for Tomcat: (-
> Dwtp.deploy="U:\Documents\eclipse\workspace_KStA_RW-Tool\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps)
>  
> had diverged from each other (Note the "tmp0" vs. "tmp1" in the paths). 
> Once I had realized and fixed this, everything came back to normal!
>
> Apologies for the bandwidth used...
>
>
> On Tuesday, August 24, 2021 at 4:02:32 PM UTC+2 mmo wrote:
>
>> I somehow destroyed my Eclipse setup for GWT applicaiton debugging - 
>> could some kind soul please help me to get going again?
>>
>> Before I had set up my GWT project using a local Tomcat server such that 
>> I was able to run and debug it using:
>>
>> First starting the CodeServer (via right-click on the GWT project --> 
>> "Run As" --> "GWT Development Mode") on localhost:9876.
>> Second: starting Tomcat (via right-click on the GWT project --> "Run As" 
>> --> "Run on Server") on localhost:8080
>>
>> This had worked out-of-the-box and created and started up the application 
>> in development mode where it fetches the .nocache.js code from the 
>> code server, but directs all HTML, CSS and especially also all RPC-requests 
>> to Tomcat's application port. With that I had been able to start, 
>> breakpoint and debug my GWT application (though the server side code only).
>>
>> Trying to get this setup to also provide the sourcemaps and allow me to 
>> debug also client side code using Chrome and the SDBG plugin I somehow 
>> destroyed that working setup and I haven't understood, yet, why this is not 
>> working anymore:
>>
>> While I can still start the code server as described above starting up 
>> the application on Tomcat downloads an index.html file-version that tries 
>> to fetch the .nocache.js file from Tomcat as well (i.e. using the 
>> URL  
>> in the index.html-file). 
>>
>> That of course doesn't work (that file needs to be fetched from the 
>> code-server's port!) and so my GWT applications (or rather its welcome 
>> page) just hangs and nothing happens.
>>
>> I have no clue what I did or destroyed or disabled so that this doesn't 
>> work anymore.
>> What do I need to do to convince Eclipse to build the development version 
>> again like it used to?
>>
>>

-- 
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/f5be9c0b-3aa2-4c8c-aeaf-b6872ba82542n%40googlegroups.com.


Re: Trying to get GWT app deployed in local Tomcat (using Eclipse)

2021-08-24 Thread Craig Mitchell
Interesting.  I don't have that setting:

[image: screenshot.png]

I'm using the standard Eclipse for Java Developers.  Not Eclipse for 
Enterprise Java.

On Monday, 23 August 2021 at 11:01:20 pm UTC+10 mmo wrote:

> @Craig Mitchell
>
> > I've never seen an option to start the code server automatically 
> Right-click on the mode --> GTW --> Settings --> GWT - Facet Settings: 
> There is a checkbox under "Super Development Mode" labeled "Sync the 
> CodeServer state with the WTP server. The WTP server start and stop will 
> also start and stop the CodeServer".
>
> > I think you mean the CodeServer doesn't always show in the Development 
> mode. 
> No - as I wrote: the CodeServer shows up reliably in this view, but the 
> Web-Server doesn't anymore. It used to, though, so I am puzzled why this is 
> not working anymore.
>
> > I just use a "Launch Chrome" launcher to start Chrome in debug, so I 
> don't need it to show up. 
> These "Connect to Chrome" and "Launch Chrome" entries usually appear in 
> the "Run As"/"Debug As"-context menu but often they don't. And once they 
> disappeared, they don't show up anymore until the next Eclipse-restart. 
> Very odd and annoying!  :-( 
>
>

-- 
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/87690eea-a63d-438d-8377-17ddb99a16cen%40googlegroups.com.


Re: Trying to get GWT app deployed in local Tomcat (using Eclipse)

2021-08-21 Thread Craig Mitchell
1.  I've never seen an option to start the code server automatically, and I 
couldn't find the option you're talking about.  I always start the code 
server manually.  However, I not running Tomcat, I'm running Google App 
Engine Standard.
2.  I think you mean the CodeServer doesn't always show in the Development 
mode.  I've seen this happen too on my old Eclipse install, haven't seen it 
happen on the new 2021-06 install.  I just use a "Launch Chrome" launcher 
to start Chrome in debug, so I don't need it to show up.

On Saturday, 21 August 2021 at 3:54:26 am UTC+10 mmo wrote:

> Thanks all! Meanwhile I got this starting up nicely from inside eclipse 
> and - boy - this is really much faster! 
>
> Things that don't work, yet:
> 1. As far as I understand, the CodeServer should be started up 
> automatically when starting the WebServer. There even is a flag in the GWT 
> settings "Sync the CodeServer state with the WTP server. The WTP server 
> start and stop will also start and stop the CodeServer". 
> That is not working for me. I always have to start the CodeServer 
> separately. Strange enough it sometimes gets stopped, when I stop Tomcat, 
> but it is never started, when I start Tomcat. So this feature seems to work 
> only in one direction and then unreliably. But fortunately that's not such 
> a big deal...
> 2. The CodeServer reliably appears with its URL in the "Development 
> Mode"-view of the GWT plugin. However, the Tomcat server does so not 
> always. Sometimes it appears, sometimes it does not. And right now it seems 
> to refuse altogether. I have started and restarted it maybe 10 times now 
> but its URL does not show up in that view. Any idea what setting or state 
> could influence that? 
> The issue with the Web-server's URL not being listed there is, that I then 
> can not right-click on the URL and choose to "Run with SDBG Chrome JS 
> debugger". I would like to try that mode to see if that's working and 
> helpful to debug client code. 
>
> Any advice on these topics?
>
> On Sunday, August 8, 2021 at 6:23:05 PM UTC+2 vas...@gmail.com wrote:
>
>> So maybe it is possible for you to skip GWT compilation while building 
>>> the *.war directory to save some minutes.
>>
>>
>> In my case this is a huge understatement. In superdevmode the compilation 
>> is nearly instant (1-2secs maybe less)  instead of 90sec of the full 
>> compile.
>>
>> I don't know how it behaves in really big codebases that take several 
>> minutes to compile but I bet it would make a big difference.
>>
>> So follow Jens' advice and try to setup superdevmode for development. For 
>> production you still need the final compilation step.
>>
>> The other solution is to use code splitting 
>> http://www.gwtproject.org/doc/latest/DevGuideCodeSplitting.html but a) I 
>> have never done it and b) certainly looks more invasing.
>> -- 
>> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/fa0f4421-231c-4e6b-b469-6ddc157e8ed7n%40googlegroups.com.


Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06

2021-08-20 Thread Craig Mitchell
I've not seen the error.   2021-06, connecting to a Bitbucket repos.

On Friday, 20 August 2021 at 8:39:27 pm UTC+10 Shawn wrote:

> Ha funny or not after a little use I got the same error.
>
> I couldn't find the underlying issue mentioned anywhere (was a missing 
> class) so didn't know what to reinstall and just restarted eclipse.  It 
> works again.
>
> On Fri, Aug 20, 2021 at 5:57 PM Shawn Brown  wrote:
>
>> Hey.  Sorry to hear that.
>>
>> I'm on v2021-06 and don't see eGit crashing.  That said, I mostly use 
>> GitHub Desktop.
>>
>> I do remember struggling with v2021-03 to get a compatible eGit version 
>> installed.  Not sure why that was or if it's related to the SDBG plugin, 
>> but I think I installed the SDBG plugin prior to v2021-03.  Likely it was 
>> some other update or installation I tried that required a newer version of 
>> eGit and that installing it perhaps resolved the issue with SDBG.  Just 
>> speculation here...
>>
>> On Fri, Aug 20, 2021 at 5:04 PM mmo  wrote:
>>
>>> @Craig Mitchell
>>> > ...
>>> > And all working great now!  Yay!  Thanks.
>>>
>>> Unfortunately not quite: 
>>>
>>> While the instructions to download, build and replace the SDBG plugin 
>>> *do* work fine the replacement of the plugin had a *very *adverse 
>>> side-effect (on my eclipse at least - v2021-03):
>>> With the new SDBG plugin installed the eGit-plugin reproducibly crashes. 
>>> I.e. I then can not access any git-repo anymore using Eclipse.
>>>
>>> Cheers,
>>> Michael
>>>
>>> -- 
>>> 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/6cdd59cb--46a7-845f-8e42f5833420n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/google-web-toolkit/6cdd59cb--46a7-845f-8e42f5833420n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
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/73b82bdd-c9f0-4696-8d32-7614b15f646bn%40googlegroups.com.


Re: Just saying thanks

2021-08-11 Thread Craig Mitchell
Also giving GWT thanks.  I thank Java for being an excellent strongly typed 
language.  GWT lets me use Java for the browser, and for that, thank you 
GWT, and all its dedicated, hard working contributors!  :)

On Thursday, 12 August 2021 at 12:30:41 am UTC+10 ralph.f...@gmail.com 
wrote:

> I agree without reservation! Using GWT since 2011 and really glad to see 
> the 2.9 release working! 
>
>
> Tom Van Eetvelde  schrieb am Mo. 19. Okt. 2020 um 
> 12:54:
>
>> Hi,
>>
>> I just wanted to say that I have been using GWT since 2009 and I never 
>> thought about sharing how much fun GWT has brought to my developer life. So 
>> I am doing it now :-)
>>
>> To be honest, there are some libraries/toolkits out there that rise above 
>> the others. They have this intrinsic quality, they are open instead of 
>> restrictive on your coding style and when you need to take the extra mile 
>> in your dev work, the framework goes along, providing what you need. GWT is 
>> definitely among these.
>>
>> GWT is the reason that I started browser UI development as a Java backend 
>> profile.
>> I am so happy GWT is still among us and I will be continuing to use this 
>> framework for many years to come. 
>>
>> Thanks for this great framework!
>>
>> -- 
>>
> 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/63a54346-f3fd-45b9-86d9-c1fe3ef9298dn%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/69febbf9-df20-48e3-b5ac-b2df3afd22d9n%40googlegroups.com.


Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06

2021-08-11 Thread Craig Mitchell
Sorry, I understand now.  Other people have fixed it, it just hasn't been 
released.  I'm guessing this was the 
fix:  
https://github.com/sdbg/sdbg/commit/be4f2e193bf6f31fefc00985e8657e1254b2230c

So, to get it working.  Steps:

1.  Uninstall the existing one:
[image: plugin.png]
2. Clone:  https://github.com/sdbg/sdbg
3. Run maven:  mvn package
4. Add the built plugin with these 
steps:  
https://stackoverflow.com/questions/31553376/eclipse-how-to-install-a-plugin-manually

Plugin is 
in:  
com.github.sdbg.releng.p2\target\com.github.sdbg.releng.p2-1.0.10.qualifier.zip

And all working great now!  Yay!  Thanks.

On Wednesday, 11 August 2021 at 10:09:22 am UTC+10 Craig Mitchell wrote:

> Hi Shawn.
>
> > Just do a maven build and install in eclipse from the archive
>
> Sorry, I'm not understanding, which build and what archive?
>
> The SDBG repos is here:  https://github.com/sdbg/sdbg
>
> When I get some time, I'll check out the  SDBG repos, modify the code to 
> remove the use of DatatypeConverter, build, and then install in Eclipse, 
> and hopefully that fixes the problem.
>
> Cheers.
>
> On Tuesday, 10 August 2021 at 12:33:23 am UTC+10 Shawn wrote:
>
>> Using SDGB built from recent code solves the issue (of it not working 
>> with Java 11).  Just do a maven build and install in eclipse from the 
>> archive.  At the time I moved to Java 11, it was at 
>> com.github.sdbg.releng.p2/target/com.github.sdbg.releng.
>> p2-1.0.10.qualifier.zip
>>
>> Perhaps the version has changed since then.  
>>
>> I think the SDGB repo is in GitHub or someplace similar.  Not at my 
>> computer at the moment so can’t confirm.
>>
>> On Sun, Aug 8, 2021 at 3:05 Craig Mitchell  
>> wrote:
>>
>>> >  client side in Chrome or Edge
>>>
>>> Yep, I can still do this.  And when I want to step into code, I often do 
>>> just use the Chrome debugger (as the SDBG plugin was a bit of hit and miss 
>>> when inspecting variable, etc.).
>>>
>>> However, it's very convient to get the Chrome console right in Eclipse.  
>>> You can instantly see if anything is going wrong.  That's the main reason 
>>> it'd be great to get the SDBG plugin working again.
>>>
>>> I guess I could try to fix SDBG myself.  Looks like this is the problem:
>>>
>>>
>>> https://github.com/sdbg/sdbg/blob/master/com.github.sdbg.debug.core/src/com/github/sdbg/debug/core/internal/webkit/protocol/WebkitPage.java#L109
>>>
>>> I'll post a message in https://groups.google.com/g/sdbg first, and hope 
>>> someone that knows something about the plugin responds.  :-)
>>>
>>> On Sunday, 8 August 2021 at 4:38:53 pm UTC+10 ralph.f...@gmail.com 
>>> wrote:
>>>
>>>> Stopped using Eclipse plug-ins just recently when going to JDK11. Am 
>>>> using Maven Jetty plugin to run code server and host the application. 
>>>>
>>>> It was a bit cumbersome to set up (steep Maven learning curve!) but was 
>>>> worth it in the end: onboard a new developer in no time (if Maven is 
>>>> already configured). 
>>>>
>>>> Server side debugging in Eclipse (or whatever is your preferred IDE), 
>>>> client side in Chrome or Edge. 
>>>>
>>>>
>>>> Craig Mitchell  schrieb am So. 8. Aug. 2021 
>>>> um 08:25:
>>>>
>>>>> Tried a fresh Eclipse install, and also tried installing the GWT 
>>>>> plugin without the Chrome debugger, and then adding the SDBG manually 
>>>>> from 
>>>>> here https://sdbg.github.io/ with no luck.
>>>>>
>>>>> Looks like the SDBG died somewhere between my old 2018-12 Eclipse, and 
>>>>> 2021-06 Eclipse.
>>>>>
>>>>> Looking at the error:  javax/xml/bind/Datatypeconverter not found, it 
>>>>> sounds like it's because Eclipse can no longer run on Java 8 (I'm running 
>>>>> it on Java 11).
>>>>>
>>>>> Does anyone have Chrome debug in Eclipse still working?  Or are there 
>>>>> any other plugins that we can use?
>>>>>
>>>>> On Saturday, 7 August 2021 at 2:46:30 pm UTC+10 Craig Mitchell wrote:
>>>>>
>>>>>> I just did a fresh install on a new PC, and the GWT plugin worked 
>>>>>> fine with Eclipse 2021-06.
>>>>>>
>>>>>> The only issue I have is when I launch Chrome from Eclipse, Chrome 
>>>>>> opens fine, however, I get this error:
>>>>&

Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06

2021-08-10 Thread Craig Mitchell
Hi Shawn.

> Just do a maven build and install in eclipse from the archive

Sorry, I'm not understanding, which build and what archive?

The SDBG repos is here:  https://github.com/sdbg/sdbg

When I get some time, I'll check out the  SDBG repos, modify the code to 
remove the use of DatatypeConverter, build, and then install in Eclipse, 
and hopefully that fixes the problem.

Cheers.

On Tuesday, 10 August 2021 at 12:33:23 am UTC+10 Shawn wrote:

> Using SDGB built from recent code solves the issue (of it not working 
> with Java 11).  Just do a maven build and install in eclipse from the 
> archive.  At the time I moved to Java 11, it was at 
> com.github.sdbg.releng.p2/target/com.github.sdbg.releng.
> p2-1.0.10.qualifier.zip
>
> Perhaps the version has changed since then.  
>
> I think the SDGB repo is in GitHub or someplace similar.  Not at my 
> computer at the moment so can’t confirm.
>
> On Sun, Aug 8, 2021 at 3:05 Craig Mitchell  
> wrote:
>
>> >  client side in Chrome or Edge
>>
>> Yep, I can still do this.  And when I want to step into code, I often do 
>> just use the Chrome debugger (as the SDBG plugin was a bit of hit and miss 
>> when inspecting variable, etc.).
>>
>> However, it's very convient to get the Chrome console right in Eclipse.  
>> You can instantly see if anything is going wrong.  That's the main reason 
>> it'd be great to get the SDBG plugin working again.
>>
>> I guess I could try to fix SDBG myself.  Looks like this is the problem:
>>
>>
>> https://github.com/sdbg/sdbg/blob/master/com.github.sdbg.debug.core/src/com/github/sdbg/debug/core/internal/webkit/protocol/WebkitPage.java#L109
>>
>> I'll post a message in https://groups.google.com/g/sdbg first, and hope 
>> someone that knows something about the plugin responds.  :-)
>>
>> On Sunday, 8 August 2021 at 4:38:53 pm UTC+10 ralph.f...@gmail.com wrote:
>>
>>> Stopped using Eclipse plug-ins just recently when going to JDK11. Am 
>>> using Maven Jetty plugin to run code server and host the application. 
>>>
>>> It was a bit cumbersome to set up (steep Maven learning curve!) but was 
>>> worth it in the end: onboard a new developer in no time (if Maven is 
>>> already configured). 
>>>
>>> Server side debugging in Eclipse (or whatever is your preferred IDE), 
>>> client side in Chrome or Edge. 
>>>
>>>
>>> Craig Mitchell  schrieb am So. 8. Aug. 2021 
>>> um 08:25:
>>>
>>>> Tried a fresh Eclipse install, and also tried installing the GWT plugin 
>>>> without the Chrome debugger, and then adding the SDBG manually from here 
>>>> https://sdbg.github.io/ with no luck.
>>>>
>>>> Looks like the SDBG died somewhere between my old 2018-12 Eclipse, and 
>>>> 2021-06 Eclipse.
>>>>
>>>> Looking at the error:  javax/xml/bind/Datatypeconverter not found, it 
>>>> sounds like it's because Eclipse can no longer run on Java 8 (I'm running 
>>>> it on Java 11).
>>>>
>>>> Does anyone have Chrome debug in Eclipse still working?  Or are there 
>>>> any other plugins that we can use?
>>>>
>>>> On Saturday, 7 August 2021 at 2:46:30 pm UTC+10 Craig Mitchell wrote:
>>>>
>>>>> I just did a fresh install on a new PC, and the GWT plugin worked fine 
>>>>> with Eclipse 2021-06.
>>>>>
>>>>> The only issue I have is when I launch Chrome from Eclipse, Chrome 
>>>>> opens fine, however, I get this error:
>>>>> [image: error.png]
>>>>> and I can't debug the browser in Eclipse.  Debugging still works fine 
>>>>> in Chrome.
>>>>>
>>>>>
>>>>> On Thursday, 17 June 2021 at 3:22:34 am UTC+10 Jim Douglas wrote:
>>>>>
>>>>>> I just updated my Eclipse development environment from 2021-03 to 
>>>>>> 2021-06. The installed GWT Eclipse Plugin (which hasn't been updated 
>>>>>> since 
>>>>>> 2017) no longer shows up in the menu bar, and it logs a bunch of errors. 
>>>>>> Is 
>>>>>> anyone (Brandon?) still maintaining it?
>>>>>>
>>>>>>
>>>>>> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html
>>>>>>
>>>>>>   GWT Eclipse Plugin 3.0.0.201710131939 
>>>>>> com.gwtplugins.eclipse.suite.v3.feature.feature.group GWT Eclipse 
>>>>>> Plugin
>>>>>>
>&g

Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06

2021-08-08 Thread Craig Mitchell
>  client side in Chrome or Edge

Yep, I can still do this.  And when I want to step into code, I often do 
just use the Chrome debugger (as the SDBG plugin was a bit of hit and miss 
when inspecting variable, etc.).

However, it's very convient to get the Chrome console right in Eclipse.  
You can instantly see if anything is going wrong.  That's the main reason 
it'd be great to get the SDBG plugin working again.

I guess I could try to fix SDBG myself.  Looks like this is the problem:

https://github.com/sdbg/sdbg/blob/master/com.github.sdbg.debug.core/src/com/github/sdbg/debug/core/internal/webkit/protocol/WebkitPage.java#L109

I'll post a message in https://groups.google.com/g/sdbg first, and hope 
someone that knows something about the plugin responds.  :-)

On Sunday, 8 August 2021 at 4:38:53 pm UTC+10 ralph.f...@gmail.com wrote:

> Stopped using Eclipse plug-ins just recently when going to JDK11. Am using 
> Maven Jetty plugin to run code server and host the application. 
>
> It was a bit cumbersome to set up (steep Maven learning curve!) but was 
> worth it in the end: onboard a new developer in no time (if Maven is 
> already configured). 
>
> Server side debugging in Eclipse (or whatever is your preferred IDE), 
> client side in Chrome or Edge. 
>
>
> Craig Mitchell  schrieb am So. 8. Aug. 2021 um 
> 08:25:
>
>> Tried a fresh Eclipse install, and also tried installing the GWT plugin 
>> without the Chrome debugger, and then adding the SDBG manually from here 
>> https://sdbg.github.io/ with no luck.
>>
>> Looks like the SDBG died somewhere between my old 2018-12 Eclipse, and 
>> 2021-06 Eclipse.
>>
>> Looking at the error:  javax/xml/bind/Datatypeconverter not found, it 
>> sounds like it's because Eclipse can no longer run on Java 8 (I'm running 
>> it on Java 11).
>>
>> Does anyone have Chrome debug in Eclipse still working?  Or are there any 
>> other plugins that we can use?
>>
>> On Saturday, 7 August 2021 at 2:46:30 pm UTC+10 Craig Mitchell wrote:
>>
>>> I just did a fresh install on a new PC, and the GWT plugin worked fine 
>>> with Eclipse 2021-06.
>>>
>>> The only issue I have is when I launch Chrome from Eclipse, Chrome opens 
>>> fine, however, I get this error:
>>> [image: error.png]
>>> and I can't debug the browser in Eclipse.  Debugging still works fine in 
>>> Chrome.
>>>
>>>
>>> On Thursday, 17 June 2021 at 3:22:34 am UTC+10 Jim Douglas wrote:
>>>
>>>> I just updated my Eclipse development environment from 2021-03 to 
>>>> 2021-06. The installed GWT Eclipse Plugin (which hasn't been updated since 
>>>> 2017) no longer shows up in the menu bar, and it logs a bunch of errors. 
>>>> Is 
>>>> anyone (Brandon?) still maintaining it?
>>>>
>>>>
>>>> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html
>>>>
>>>>   GWT Eclipse Plugin 3.0.0.201710131939 
>>>> com.gwtplugins.eclipse.suite.v3.feature.feature.group GWT Eclipse 
>>>> Plugin
>>>>
>>>>
>>>> org.osgi.framework.BundleException: Could not resolve module: 
>>>> com.gwtplugins.gdt.eclipse.core [3649]
>>>>   Unresolved requirement: Require-Bundle: 
>>>> com.gwtplugins.gdt.eclipse.platform
>>>> -> Bundle-SymbolicName: com.gwtplugins.gdt.eclipse.platform; 
>>>> bundle-version="3.0.0.201710131939"; singleton:="true"
>>>>com.gwtplugins.gdt.eclipse.platform [3651]
>>>>  No resolution report for the bundle.  Bundle was not resolved 
>>>> because of a uses constraint violation.
>>>>   org.apache.felix.resolver.reason.ReasonException: Uses constraint 
>>>> violation. Unable to resolve resource com.gwtplugins.gdt.eclipse.platform 
>>>> [osgi.identity; type="osgi.bundle"; version:Version="3.0.0.201710131939"; 
>>>> osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"] 
>>>> because it is exposed to package 'javax.servlet' from resources 
>>>> javax.servlet [osgi.identity; type="osgi.bundle"; 
>>>> version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"] and 
>>>> jakarta.servlet-api [osgi.identity; type="osgi.bundle"; 
>>>> version:Version="4.0.0"; osgi.identity="jakarta.servlet-api"] via two 
>>>> dependency chains.
>>>>
>>>> Chain 1:
>>>>   com.gwtplugins.gdt.eclipse.platf

Re: The GWT Eclipse Plugin stopped working in Eclipse 2021-06

2021-08-08 Thread Craig Mitchell
Tried a fresh Eclipse install, and also tried installing the GWT plugin 
without the Chrome debugger, and then adding the SDBG manually from here 
https://sdbg.github.io/ with no luck.

Looks like the SDBG died somewhere between my old 2018-12 Eclipse, and 
2021-06 Eclipse.

Looking at the error:  javax/xml/bind/Datatypeconverter not found, it 
sounds like it's because Eclipse can no longer run on Java 8 (I'm running 
it on Java 11).

Does anyone have Chrome debug in Eclipse still working?  Or are there any 
other plugins that we can use?

On Saturday, 7 August 2021 at 2:46:30 pm UTC+10 Craig Mitchell wrote:

> I just did a fresh install on a new PC, and the GWT plugin worked fine 
> with Eclipse 2021-06.
>
> The only issue I have is when I launch Chrome from Eclipse, Chrome opens 
> fine, however, I get this error:
> [image: error.png]
> and I can't debug the browser in Eclipse.  Debugging still works fine in 
> Chrome.
>
>
> On Thursday, 17 June 2021 at 3:22:34 am UTC+10 Jim Douglas wrote:
>
>> I just updated my Eclipse development environment from 2021-03 to 
>> 2021-06. The installed GWT Eclipse Plugin (which hasn't been updated since 
>> 2017) no longer shows up in the menu bar, and it logs a bunch of errors. Is 
>> anyone (Brandon?) still maintaining it?
>>
>>
>> http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html
>>
>>   GWT Eclipse Plugin 3.0.0.201710131939 
>> com.gwtplugins.eclipse.suite.v3.feature.feature.group GWT Eclipse Plugin
>>
>>
>> org.osgi.framework.BundleException: Could not resolve module: 
>> com.gwtplugins.gdt.eclipse.core [3649]
>>   Unresolved requirement: Require-Bundle: 
>> com.gwtplugins.gdt.eclipse.platform
>> -> Bundle-SymbolicName: com.gwtplugins.gdt.eclipse.platform; 
>> bundle-version="3.0.0.201710131939"; singleton:="true"
>>com.gwtplugins.gdt.eclipse.platform [3651]
>>  No resolution report for the bundle.  Bundle was not resolved 
>> because of a uses constraint violation.
>>   org.apache.felix.resolver.reason.ReasonException: Uses constraint 
>> violation. Unable to resolve resource com.gwtplugins.gdt.eclipse.platform 
>> [osgi.identity; type="osgi.bundle"; version:Version="3.0.0.201710131939"; 
>> osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"] 
>> because it is exposed to package 'javax.servlet' from resources 
>> javax.servlet [osgi.identity; type="osgi.bundle"; 
>> version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"] and 
>> jakarta.servlet-api [osgi.identity; type="osgi.bundle"; 
>> version:Version="4.0.0"; osgi.identity="jakarta.servlet-api"] via two 
>> dependency chains.
>>
>> Chain 1:
>>   com.gwtplugins.gdt.eclipse.platform [osgi.identity; type="osgi.bundle"; 
>> version:Version="3.0.0.201710131939"; 
>> osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]
>> require: (osgi.wiring.bundle=javax.servlet)
>>  |
>> provide: osgi.wiring.bundle: javax.servlet
>>   javax.servlet [osgi.identity; type="osgi.bundle"; 
>> version:Version="3.0.0.v201112011016"; osgi.identity="javax.servlet"]
>>
>> Chain 2:
>>   com.gwtplugins.gdt.eclipse.platform [osgi.identity; type="osgi.bundle"; 
>> version:Version="3.0.0.201710131939"; 
>> osgi.identity="com.gwtplugins.gdt.eclipse.platform"; singleton:="true"]
>> require: (osgi.wiring.bundle=org.eclipse.jetty.servlet)
>>  |
>> provide: osgi.wiring.bundle; bundle-version:Version="10.0.5"; 
>> osgi.wiring.bundle="org.eclipse.jetty.servlet"
>>   org.eclipse.jetty.servlet [osgi.identity; type="osgi.bundle"; 
>> version:Version="10.0.5"; osgi.identity="org.eclipse.jetty.servlet"]
>> import: 
>> (&(osgi.wiring.package=javax.servlet)(&(version>=4.0.0)(!(version>=5.0.0
>>  |
>> export: osgi.wiring.package: javax.servlet
>>   jakarta.servlet-api [osgi.identity; type="osgi.bundle"; 
>> version:Version="4.0.0"; osgi.identity="jakarta.servlet-api"]
>> at org.eclipse.osgi.container.Module.start(Module.java:463)
>> at 
>> org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1849)
>> at 
>> org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
>> at 
>> org.eclipse.osgi.contai

  1   2   3   >