Re: Is moving away from RPC a good idea?

2024-01-10 Thread Michael Conrad
You should investigate the DominoKit project. They have a much more 
up-to-date JSON/Jackson-ish implementation.


Ref: https://github.com/DominoKit/domino-rest



On 1/10/24 11:26, Christian Hebert wrote:
Hi guys, I've seen the changes in the new release regarding jakarta 
servlets, which is great, it's a step toward jakarta but to this day, 
 GWT is still based on the Servlet API 3.1.


Prior of seeing that change, I tried to move away from RPC calls and 
use http requests instead. I found a nice library called RestyGWT 
(https://resty-gwt.github.io/) who can really simplify the process of 
handling json data from/to a Rest API.


So I converted my GWT remote servlets to a Rest API, made a few minor 
changes in my client code and voilà, I was able to deploy it on a 
Jakarta Application server since there is no GWT involved on the 
server side anymore.


The last version of RestyGWT has been release in 2020 so I'm not sure 
how active this project is but from what I've seen it's enough for me.


So, I would like to get your thoughts on that.  Would you go on that 
road? stick to RPC calls and wait for a version of GWT based on 
Jakarta? build your "own" GWT with the changes introduced in the vew 
version?

--
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/8fa7dc19-2a15-442d-93b2-adebb947046cn%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/156e77ff-25bd-4743-8798-0d0347d1866d%40newsrx.com.


Re: Support for Intellj ide

2023-12-15 Thread Michael Conrad
There is a GWT plugin for Ultimate (paid). It is not available for the
community version.

On Thu, Dec 14, 2023 at 6:45 PM Jvm  wrote:

> Please is there no gwt support for intellj ide?
>
> --
> 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/af8950f6-47eb-4fdc-b27a-fce2c88eacc4n%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/CALao4gN2b5rueqT1%2B8OUoVB3KR%3DpSF1%2BWVXAMegxfYLbcVaNWQ%40mail.gmail.com.


Re: GWT RPC call recognized as a Java Method Injection by Fortiweb

2023-07-25 Thread Michael Conrad
Did y'all test DominoKit? It is actively maintained and has a REST module. 
I'm curious if you did test it what shortcomings you may have run into.

On Tuesday, July 25, 2023 at 9:23:53 AM UTC-4 RobW wrote:

> We got to a similar point. Looked in depth at moving the GWT front end to 
> a REST API - but found two big drawbacks: 
>
>1. none of the frameworks we could find had async callback handling 
>similar to GWT-RPC, with common interface classes client server side AND 
>support JAX-RS subresources. RestyGWT got close apart from those last two 
>points - there is a model with common client/server interfaces, but it 
>doesn't support subresources. We found at least 1 other GWT REST toolkit 
>that had exactly the same issue  - so it's clearly not a trivial one to 
>solve. 
>2. somewhat more serious than the first issue was that none of the GWT 
>REST API frameworks looked to be that actively maintained, at least 
>tracking their GitHub commits anyhow
>
> So ultimately, although REST API an attractive route, GWT-RPC remains more 
> practical for us in the near term.
>
> Note - one we didn't explore in depth but may come back too was Domino 
> Kit, which has a REST API component. That did look more actively maintained 
> and perhaps is a way forward.
>
> On Monday, 24 July 2023 at 18:50:38 UTC+1 Ralph Fiergolla wrote:
>
>> That is, as long as I stay within GWT there is no need to change (and 
>> loose type checking and convenience). I will happily stay with GWT RPC then!
>>
>> R
>>
>> Jens  schrieb am Mo. 24. Juli 2023 um 18:24:
>>
>>>
>>> I think I asked the question before: as a long-term GWT-RPC user, what 
>>> would be the benefit of moving to some other RPC protocol/mechanism?
>>>
>>>
>>> Depends on your situation of course. If you want to use your existing 
>>> backend with other clients written in other languages then GWT-RPC is a bad 
>>> fit. While the wire format of GWT-RPC is documented, you still need to 
>>> write the client code to generate it. Also GWT-RPC supports inheritance 
>>> which other languages you want to use might not support. Other JS based RPC 
>>> solutions as well as general purpose solutions like gRPC typically do not 
>>> support inheritance.
>>>
>>> GWT-RPC will already be annoying if you decide to have some portions of 
>>> your app being written in a different framework since it is easier to find 
>>> developers for that framework, e.g. angular, svelte, react, whatever. You 
>>> would then need to define a JS api that calls into GWT code so these 
>>> frameworks can talk to your GWT-RPC backend (or you need to provide new 
>>> endpoints in your backend that do not talk GWT-RPC).
>>>
>>> -- 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/ab08b131-3904-49b1-8920-b924c7b31c9an%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/16623367-e3d6-46ad-9c0f-7cd02e7a496fn%40googlegroups.com.


Re: GWT app gets loaded multiple times in Firefox

2023-02-08 Thread Michael Conrad

Thank you very much!



On 2/8/23 14:44, Thomas Broyer wrote:
It seems to be due to the __gwt_historyFrame: the subsequent requests 
have initiator=subdocument in the dev tools network panel, and a 
Sec-Fetch-Dest:iframe request header; if you inspect the iframe in dev 
tools, you can see the host page being loaded inside it rather than an 
about:blank, and each reload will load one more level.
Given that this iframe was only there for old IE versions that didn't 
support onhashchange (according to caniuse.com, that was IE6 and IE7), 
you can safely remove it (code using it was removed in GWT 2.7 a bit 
more than 9 years ago, released more than 8 years ago: 
https://github.com/gwtproject/gwt/commit/802da200257a1ba1600638be217f55fda331bde9 
– yet, the website still references it, and the GWT Plugin for Eclipse 
apparently still generates it: 
https://github.com/gwt-plugins/gwt-eclipse-plugin/blob/ceff817bc9e1af81cf007411dc11192c0c700cb1/plugins/com.gwtplugins.gwt.eclipse.core/src/com/google/gwt/eclipse/core/wizards/NewHostPageWizard.java#L171-L173)


On Wednesday, February 8, 2023 at 1:02:37 PM UTC+1 grue wrote:

I have deployed the example app here:

http://test7.pb3.technology/TestGWT/

On Wednesday, 8 February 2023 at 11:47:43 UTC+1 grue wrote:

I have tested it on MacOS 12.6.3 and Ubuntu and Windows 10 and
in deploy mode but I also see the issue in development mode.

Michael


On Wednesday, 8 February 2023 at 10:32:38 UTC+1
lofid...@gmail.com wrote:

Following question:
- What OS?
- Do you try in development mode or deployment mode?

Thanks,
Lofi

grue schrieb am Dienstag, 7. Februar 2023 um 14:03:25 UTC+1:

I have observed a weird behaviour when opening a GWT
app in Firefox. When I first open the page everything
is normal but once I refresh the page all resources
including the index.html get fetched twice. If I
refresh the page once more everything gets fetched
three times and so on... (see screenshot attached)
I see this behaviour only on FF, even on a freshly
installed one and after clearing all the caches and data.
To reproduce the issue I created a minimalistic GWT
app at https://github.com/mgrue/TestGWT
Reproducing is a bit tricky since sometimes the app
behaves normal but once you close the tab and open a
new on or restart FF the weird behaviour is back. I
tested the app both on Wildfly and Jetty (I have
included a Dockerfile) but can't see any difference.

I'd really appreciate if someone could help me
figuring out what's going on here.

Thank you very much in advance!
Michael

Screen Shot 2023-02-07 at 1.40.03 PM.png

--
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/990885cc-98e1-4f5f-a159-ca0c1b080f32n%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/9bc5eb18-3332-dde0-902b-750256f0f207%40newsrx.com.


Re: GWT app gets loaded multiple times in Firefox

2023-02-08 Thread Michael Conrad
We see the same behavior here. I'm convinced it is some sort of FF bug. 
Why else would a page reload increase the number of times the entry 
point is entered? Is not a page reload supposed to be the same as 
opening it up in a new tab while discarding all previous JS states?


On 2/8/23 07:02, 'grue' via GWT Users wrote:

I have deployed the example app here:

http://test7.pb3.technology/TestGWT/

On Wednesday, 8 February 2023 at 11:47:43 UTC+1 grue wrote:

I have tested it on MacOS 12.6.3 and Ubuntu and Windows 10 and in
deploy mode but I also see the issue in development mode.

Michael


On Wednesday, 8 February 2023 at 10:32:38 UTC+1 lofid...@gmail.com
wrote:

Following question:
- What OS?
- Do you try in development mode or deployment mode?

Thanks,
Lofi

grue schrieb am Dienstag, 7. Februar 2023 um 14:03:25 UTC+1:

I have observed a weird behaviour when opening a GWT app
in Firefox. When I first open the page everything is
normal but once I refresh the page all resources including
the index.html get fetched twice. If I refresh the page
once more everything gets fetched three times and so on...
(see screenshot attached)
I see this behaviour only on FF, even on a freshly
installed one and after clearing all the caches and data.
To reproduce the issue I created a minimalistic GWT app at
https://github.com/mgrue/TestGWT
Reproducing is a bit tricky since sometimes the app
behaves normal but once you close the tab and open a new
on or restart FF the weird behaviour is back. I tested the
app both on Wildfly and Jetty (I have included a
Dockerfile) but can't see any difference.

I'd really appreciate if someone could help me figuring
out what's going on here.

Thank you very much in advance!
Michael

Screen Shot 2023-02-07 at 1.40.03 PM.png

--
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/e2a0a891-04e1-4bd8-9e7f-8047fab9ea8en%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/39bfdd42-0853-98f5-3586-4c12eb8270bb%40newsrx.com.


Re: Issue with migrating to GWT 2.10

2023-01-19 Thread Michael Conrad

Meh... I just saw the compile options below the empty pic.

On 1/19/23 16:04, Michael Conrad wrote:

a) Have you tried increasing heap space?
b) Are you compiling production in STRICT mode? (Strongly recommended.)
c) Are you running SDM in STRICT compile mode? (Strongly recommended.)

On 1/19/23 14:43, Paul Stockley wrote:
We are trying to migrate to GWT 2.10 from 2.08. We get this internal 
error


nirvana_–_ci2_build_nirvana_war_xml__nirvana_.jpg

Any idea how to further debug this? Our app works fine using SDM we 
just get this error when compiling for deployment.


Compiler options are:  -logLevel DEBUG -war ${webapp.dir} 
com.ocs.nirvana.Encasa -XnoclassMetadata -XnocheckCasts 
-generateJsInteropExports -style ${compile.style} -strict -optimize 7

--
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/b9d05c7f-d9eb-465f-8b70-e84627b455c0n%40googlegroups.com 
<https://groups.google.com/d/msgid/google-web-toolkit/b9d05c7f-d9eb-465f-8b70-e84627b455c0n%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/ead9badb-000c-865c-c323-afe068de9095%40newsrx.com.


Re: Issue with migrating to GWT 2.10

2023-01-19 Thread Michael Conrad

a) Have you tried increasing heap space?
b) Are you compiling production in STRICT mode? (Strongly recommended.)
c) Are you running SDM in STRICT compile mode? (Strongly recommended.)

On 1/19/23 14:43, Paul Stockley wrote:
We are trying to migrate to GWT 2.10 from 2.08. We get this internal 
error


nirvana_–_ci2_build_nirvana_war_xml__nirvana_.jpg

Any idea how to further debug this? Our app works fine using SDM we 
just get this error when compiling for deployment.


Compiler options are:  -logLevel DEBUG -war ${webapp.dir} 
com.ocs.nirvana.Encasa -XnoclassMetadata -XnocheckCasts 
-generateJsInteropExports -style ${compile.style} -strict -optimize 7

--
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/b9d05c7f-d9eb-465f-8b70-e84627b455c0n%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/c44138a7-7f77-f16c-f60d-6246334ce8db%40newsrx.com.


Re: Convert Existing GWT Backend to SPRING BOOT

2022-11-21 Thread Michael Conrad

*Are you using gwt-RPC ?*
Yes! we are using GWT-RPC & currently having a single WAR of near 
about 500mb, having CLIENT-SHARED-SERVER in a same project.
You can still have everything in a master parent project that builds the 
final WAR with all the client JS and SERVER classes in the same war.


*You'll need to switch to JSON for data transport.*
Is there any drawback of switching to JSON in GWT, such as impact on 
performance etc.
You lose easy polymorphism for models, they will require an extra set of 
annotations at the very least if you have polymorphism as part of your 
DTO setup.


*You'll need to use something like DominoKit REST.*
We found one RestyGWT , but not sure 
about its final impact as we haven't applied it yet. any suggestions...
RestyGWT is effectively defunct. Stick with a modern GWT3 compatible 
approach such as DominoKit.




*It would be also be best to split the project into three projects. An 
API project, a shared code project, and a UI project.*
We cannot get why keeping *SHARED CODE *as a separate project**is 
best. We are not having any library of GWT on server side. So except 
MODELS, what are the other stuffs we can have in SHARED CODE PROJECT.**
In this case SHARED CODE is really just the MODELS and INTERFACES and 
possible the REST Interface.


*If you are using gwt-RPC then IMHO there will need to be a big 
refactoring change at the very least*
This is where we are stuck & looking for the solution with a minimum 
change and should be stable but unable to figure out yet.
I don't think you can accomplish this with a large project with minimum 
of change unless the client API calls are fully abstracted away (or can 
be) so that code could be replaced with a different class.


On Monday, November 21, 2022 at 7:37:33 PM UTC+5:30 Michael Joyner wrote:

There are a lot of factors to consider.

Are you using gwt-RPC ? You'll need to switch to JSON for data
transport.

You'll need to use something like DominoKit REST
(https://github.com/DominoKit/domino-rest) for the data transport
layer.

It would be also be best to split the project into three projects.
An API project, a shared code project, and a UI project.

If you are using gwt-RPC then IMHO there will need to be a big
refactoring change at the very least.


On 11/21/22 08:19, viny...@gmail.com wrote:


We are having a huge project already running successfully on GWT.

But for some reasons we are planning to move our backend to
SPRING-BOOT keeping front end in GWT.

Is there any way we can do it easily without a big change in our
existing application.


-- 
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/c267bbb3-504f-41a8-896a-a2c2463eccdcn%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/1790c907-ce31-4d97-a5b9-1915fef68865n%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/9ad2ecbc-f04d-62a2-2217-291e078e9002%40newsrx.com.


Re: Convert Existing GWT Backend to SPRING BOOT

2022-11-21 Thread Michael Conrad

There are a lot of factors to consider.

Are you using gwt-RPC ? You'll need to switch to JSON for data transport.

You'll need to use something like DominoKit REST 
(https://github.com/DominoKit/domino-rest)  for the data transport layer.


It would be also be best to split the project into three projects. An 
API project, a shared code project, and a UI project.


If you are using gwt-RPC then IMHO there will need to be a big 
refactoring change at the very least.


On 11/21/22 08:19, viny...@gmail.com wrote:


We are having a huge project already running successfully on GWT.

But for some reasons we are planning to move our backend to 
SPRING-BOOT keeping front end in GWT.


Is there any way we can do it easily without a big change in our 
existing application.



--
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/c267bbb3-504f-41a8-896a-a2c2463eccdcn%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/d415aa3e-1c85-38fe-8694-343bfacd182f%40newsrx.com.


Re: The file war\WEB-INF\lib\gwt-servlet.jar has a different size than GWT SDK library gwt-servlet.jar; perhaps it is a different version? gwt-servlet.jar

2022-11-16 Thread Michael Conrad

Replace the dated version of the jar as the error message indicates.

On 11/16/22 15:39, Christian Nzhie wrote:

No one gave a try on this issue?

On Thursday, June 7, 2018 at 9:51:33 AM UTC abdenour Bali wrote:

Has anybody ran through this error using GWT 2.7

DescriptionResourcePathLocationType
The file war\WEB-INF\lib\gwt-servlet.jar has a different size than
GWT SDK library gwt-servlet.jar; perhaps it is a different
version?gwt-servlet.jar/XXX/war/WEB-INF/libUnknownGoogle Web
Toolkit Problem

Thanks.
Abdenour

--
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/ed9e1fcf-f30f-41d7-be3c-54897c7fb4a8n%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/0bf9d48d-b956-4a6e-3b57-f53ec52d813c%40newsrx.com.


Re: [GWT] [ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core'

2022-10-07 Thread Michael Conrad
We are using JDK 17 here at the office for builds without any issue. 
(Gradle setup here).


On 10/7/22 08:29, Christian Nzhie wrote:

Hello here.
I would like to react for this threat. Would at this time (2022) gwt 
supports java 12?

For I am experiencing the error mentioned above.
Thanks in advance.


On Monday, May 20, 2019 at 12:59:25 AM UTC ma...@craig-mitchell.com wrote:

I don't believe GWT supports Java 12 yet.  I'd recommend just
using Java 8.

And you might want to use the latest GWT version (2.8.2).

--
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/9e0c2d5e-770b-4884-887a-3e300a2ac28an%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/db2806b1-74a4-8c7e-59a3-d349a6a53193%40newsrx.com.


Re: App Server for GWT 2.10

2022-09-21 Thread Michael Conrad
There is the jakarta migration utility. Supposed to convert wars from
javax.* to jakarta.* for deployment. Tomcat also has a special deployment
option for such.

Another approach to consider, depending on your needs, is spring boot run,
maybe inside a docker container.


On Wed, Sep 21, 2022 at 11:16 AM Valavanur Man  wrote:

> Thanks. We had problems due to jakarta.servlet with Glassfish 6.0 when we
> attempted to migrate.
> So was looking for a good replacement preferably open source.  Was
> thinking Payara, but if it goes jakarta route, we will have the same issue
> in the future.  Any suggestions?
>
> On Wednesday, September 21, 2022 at 4:34:01 AM UTC-7 Jens wrote:
>
>> If you use GWT-RPC or RequestFactory you need to choose a servlet
>> container that still uses javax.servlet instead of jakarta.servlet because
>> both these GWT features have a servlet component using javax.servlet.
>>
>> Other than that, you can choose whatever you want.
>>
>> -- J.
>>
>> Valavanur Man schrieb am Dienstag, 20. September 2022 um 17:59:48 UTC+2:
>>
>>> Hi,
>>>
>>> We are running GWT 2.8 with Glassfish4.  We had issues trying to run the
>>> GWT (2.8) App in Glassfish 6.
>>>
>>> Currently we are looking into upgrading to GWT 2.10. Would like you know
>>> what appservers are supported to run GWT 2.10 (even GWT 2.8 and beyond). Is
>>> there a recommended set of servers?
>>>
>>> Appreciate any pointers.
>>>
>>> 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/6a0dbe21-60fc-4dd7-a071-ce021d09155fn%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/CAFHWztxr-dNwVnoYBKzPobg7vHFu4h80Xj3YJ6jo95OZ5H%3D3Fw%40mail.gmail.com.


Re: Wrapping Javascript library (chart.js) using JSInterop

2022-09-11 Thread Michael Conrad
Check your dependencies. That is an add-on library which must be included
explicitly.

On Sun, Sep 11, 2022 at 5:10 AM Manas  wrote:

> Hi All,
>
> Good Day!
>
> I'm new in GWT and I'm going through documentation and JSInterop. I'm
> facing issues with implementing chart.js using JSInterop. Can anyone guide
> me on how to resolve and keep things working? I am facing an error - "The
> import elemental2 cannot be resolved"
>
> code is -
> package chartjs;
>
> import elemental2.dom.HTMLCanvasElement; => facing error on this line
> import jsinterop.annotations.JsPackage;
> import jsinterop.annotations.JsType;
>
> @JsType(isNative = true, namespace = JsPackage.GLOBAL)
> public class Chart {
>
> public Chart(HTMLCanvasElement canvasElement, ChartConfiguration
> configuration) {
> }
> }
>
> --
> 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/d85e1313-7a55-482f-b712-022cf6fef5acn%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/CAFHWztxJ175xA6fPd8k3%3DFNut7Lb1yQLsL5P1GbJUMLNte2PCQ%40mail.gmail.com.


Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

2022-08-16 Thread Michael Conrad
My 2¢ worth  is that it would be good to have a split path with both a 
branch (GWT 2.10.x) for only security updates and misc fixes as a bug 
fix only *LTS* and also a current *Stable* branch (GWT 3.x)  that 
implements new language features and tracks with most recent Java LTS. 
This is especially important to us here  at where I work as we are 
currently migration to JDK 17 for everything and would like to take 
advantage of some of the JDK17 language features in shared code between 
GWT and Servlets. This would also allow developers the ability to have a 
more aggressive approach to adding new features and removing old cruft 
like IE x stuff or the need for permutations. Of course if would be idea 
to keep GWT 3.x compatible with GWT 2.10.x - but if a breaking change is 
needed to move the GWT ecosystem forward and keep things relevant - then 
doing so with a branch that would allow such would be ideal. I think 
godot-engine does something similar with their 3.x and 4.x branches.


As an aside, I think it would be good to have the foundation setup a 
patreon account to accept donations for funding future development.


-Michael/NewsRx

On 8/12/22 10:13, Colin Alworth wrote:
Thanks to everyone for their insights. By my count, 25% of the replies 
have at least some use for Java 8 yet, so as the example that all 
responders latched on to, it seems unlikely that the time has come to 
drop support for it, at least in production deployments (a useful 
distinction that Jens drew).


With that said, I'd like to more specifically focus on the release 
side - as conflicts arise, do we "split" releases and support both 
"old" and "new", or do we find a single consistent path of least 
resistance? A single path could require a bit more work to implement 
up front (such as build wiring to ensure Java8 support in server jars, 
but runtime support for 11+), while a split path would probably keep 
better coverage over use cases at the cost of additional release 
testing (backporting a fix requires a release for both leading and 
trailing versions).


Historically we have held off updating dependencies until there was no 
choice, to ensure that nearly every GWT project could update promptly 
- so that any performance improvements or security fixes could be 
quickly put to use. Looking at Java 8 specifically, we have several 
years before Java 8 will be EOLd. At a quick glance, I'm not seeing an 
obvious EOL for the implementations of javax.servlet packages (Jetty 
10, specifically), so I'm not sure we can afford to do more than 
implement both sets of interfaces and hope for the best, unless we 
again split as "leading"/"trailing" builds... but to reiterate, there 
are other cases here where we could remove or improve code based on 
dependencies that someone might still have a need for.


Worst case, I'm wrong, and we should focus first and foremost on 
exactly what deprecations should be handled, but with 25% of 
respondents so far with need of a version of Java that Adoptium 
intends to support until at least 2026 
, I think there might be merits to 
considering how that support could look for GWT. The question I'm 
trying to pose is how will we manage that - lighter testing on the old 
builds, focusing on only old dependencies and encouraging adoption of 
the newer release?


Are developers on this list (deliberately sent to the contributors 
list, not the general user mailing list) who don't update right away 
to new APIs (new JDK, javax vs jakarta, etc) interested in supporting 
work to keep a "LTS" release active (i.e. mostly validating backported 
fixes and smoke testing releases)? If so, is 2.10 that LTS, or do we 
want a short round of 2.11 for any more changes before beginning to 
"break" things in 2.12?


And if not, will it be acceptable to stay on stale versions of GWT, 
and while some effort will be put into keeping backwards 
compatibility, it will not outweigh needs like supporting modern 
servlet packages, drop "dev mode" htmlunit, etc?

On Sunday, August 7, 2022 at 1:16:56 PM UTC-5 stuckagain wrote:

In my case we have different codebases that overlap with reusable
components. Not all projects are willing to invest in a newer jdk
since they are basically in maintenance mode.

If GWT would drop Java 8 it would be a problem. On the other hand,
maybe it will finally force people to move on faster. They tend to
complain that we are using old technology (GWT) but at the same
time they stick with Java 8.
On 4 Aug 2022, 06:05 +0300, Colin Alworth , wrote:



If there’s one thing that GWT has tried to be consistent about,
it is retaining support for technologies past their “best by”
dates. This is a sore point from time to time, as it makes the
tooling feel dated even right after a release, but it has some
specific advantages with regards to enabling projects that are
otherwise in maintenance mode to still be able to 

Re: GWT 2.10.0: gradle gwtSuperDev - java.lang.IllegalArgumentException: No selectors

2022-08-10 Thread Michael Conrad

Hrm...

This looks like it could be a side effect from the package name change… 
Different package, no dependency upgrade detected.


-Mike

On 8/10/22 07:50, Michael Conrad wrote:

I'm now using the following for GWT in our build.gradle files.

I've remove the gwtVersion from the gwt block and switched to using 
gwtSdk to specify the GWT version.


Really not sure why it keeps getting overridden from dependencies, I 
would have thought that pulling in gwt-dev would have Gradle pull in 
the newer version automatically. Is this possibly a bug with the plugin?


I have explicitly specified the htmlunit dependency to get superdev 
mode to working again.


plugins {
id"java" id"war" id"org.docstr.gwt" id"org.gretty" }

dependencies {
gwtSdk'org.gwtproject:gwt-user:2.10.0' gwtSdk'org.gwtproject:gwt-dev:2.10.0' providedCompile"net.sourceforge.htmlunit:htmlunit:2.55.0" // to get superdev mode 
working }



On 8/9/22 15:00, Colin Alworth wrote:
My apologies, I didn't notice your attachment until I had already hit 
send. Checking the list shows that gwt-materialdesign is bringing in 
an old version of htmlunit (GWT 2.10.0 updated this also), which is 
in turn bringing in some old jetty versions:
|    |    \--- 
org.eclipse.jetty.websocket:websocket-client:9.2.18.v20160721

|    |         +--- org.eclipse.jetty:jetty-util:9.2.18.v20160721
*|    |         +--- org.eclipse.jetty:jetty-io:9.2.18.v20160721*

I can't speak to how your Gradle setup is configured, but I think you 
should have an explicit compile dependency on gwt-dev:2.10.0, which 
should at least force jetty-io and htmlunit to be updated to the 
expected versions.



On Tuesday, August 9, 2022 at 1:58:04 PM UTC-5 Colin Alworth wrote:

Your stack trace lines up except for the top frame - jetty-io
9.4.4.v20210927 has a blank line for SelectorManager.java:81, and
the source for the file at that version doesn't contain the
string "No selectors". On the other hand, jetty-io
9.2.14.v20151116 has this as a constructor (and line 81 is where
it throws):
    protected SelectorManager(Executor executor, Scheduler
scheduler, int selectors)
    {
        if (selectors<=0)
            throw new IllegalArgumentException("No selectors");
        this.executor = executor;
        this.scheduler = scheduler;
        _selectors = new ManagedSelector[selectors];
    }

This much older version of jetty-io is the general version of
Jetty that GWT 2.9 used (as well as a few earlier GWT versions).

My guess is that you have correctly updated GWT, and the expected
version of Jetty has been updated (9.4.44), except somehow you
have a dependency on the old version of jetty-io. Check the rest
of your classpath, or the particular gradle plugin you are using?


On Tuesday, August 9, 2022 at 9:20:42 AM UTC-5 Michael Joyner wrote:

Meh,

I've managed to break my GWT setup again. This time for
superdev mode. Looking for suggestions on where the (I
assume) Jetty conflict is coming from.

Getting the following stacktrace after "Module setup
completed" is logged when trying to run "./gradlew
subproject:gwtSuperDev"

java.lang.IllegalArgumentException: No selectors
    at
org.eclipse.jetty.io.SelectorManager.(SelectorManager.java:81)
    at

org.eclipse.jetty.server.ServerConnector$ServerConnectorManager.(ServerConnector.java:600)
    at

org.eclipse.jetty.server.ServerConnector.newSelectorManager(ServerConnector.java:223)
    at

org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:216)
    at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:98)
    at
com.google.gwt.dev.codeserver.WebServer.start(WebServer.java:122)
    at
com.google.gwt.dev.codeserver.CodeServer.start(CodeServer.java:162)
    at
com.google.gwt.dev.codeserver.CodeServer.main(CodeServer.java:104)
    at
com.google.gwt.dev.codeserver.CodeServer.main(CodeServer.java:55)


We are using Gradle with the wisepersist GWT plugin:

id"org.wisepersist.gwt" version"1.1.18" id"org.gretty" version"3.0.8"

gwt {

gwtVersion ="2.10.0" src += 
files(compileJava.options.annotationProcessorGeneratedSourcesDirectory)

logLevel ="INFO" maxHeapSize ="2048M";
 modules'com.newsrx.butter.Butter' compiler{ disableClassMetadata 
=false;
 strict =true;
 style ="OBF";
 } // allow sdm on simultaneous modules // devModules
'com.newsrx.butter.Butter',
'com.newsrx.newsletter.NewsletterBrowser',
'com.

Re: GWT 2.10.0: gradle gwtSuperDev - java.lang.IllegalArgumentException: No selectors

2022-08-10 Thread Michael Conrad

I'm now using the following for GWT in our build.gradle files.

I've remove the gwtVersion from the gwt block and switched to using 
gwtSdk to specify the GWT version.


Really not sure why it keeps getting overridden from dependencies, I 
would have thought that pulling in gwt-dev would have Gradle pull in the 
newer version automatically. Is this possibly a bug with the plugin?


I have explicitly specified the htmlunit dependency to get superdev mode 
to working again.


plugins {
   id"java" id"war" id"org.docstr.gwt" id"org.gretty" }

dependencies {
   gwtSdk'org.gwtproject:gwt-user:2.10.0' gwtSdk'org.gwtproject:gwt-dev:2.10.0' providedCompile"net.sourceforge.htmlunit:htmlunit:2.55.0" // to get superdev mode 
working }




On 8/9/22 15:00, Colin Alworth wrote:
My apologies, I didn't notice your attachment until I had already hit 
send. Checking the list shows that gwt-materialdesign is bringing in 
an old version of htmlunit (GWT 2.10.0 updated this also), which is in 
turn bringing in some old jetty versions:
|    |    \--- 
org.eclipse.jetty.websocket:websocket-client:9.2.18.v20160721

|    |         +--- org.eclipse.jetty:jetty-util:9.2.18.v20160721
*|    |         +--- org.eclipse.jetty:jetty-io:9.2.18.v20160721*

I can't speak to how your Gradle setup is configured, but I think you 
should have an explicit compile dependency on gwt-dev:2.10.0, which 
should at least force jetty-io and htmlunit to be updated to the 
expected versions.



On Tuesday, August 9, 2022 at 1:58:04 PM UTC-5 Colin Alworth wrote:

Your stack trace lines up except for the top frame - jetty-io
9.4.4.v20210927 has a blank line for SelectorManager.java:81, and
the source for the file at that version doesn't contain the string
"No selectors". On the other hand, jetty-io 9.2.14.v20151116 has
this as a constructor (and line 81 is where it throws):
    protected SelectorManager(Executor executor, Scheduler
scheduler, int selectors)
    {
        if (selectors<=0)
            throw new IllegalArgumentException("No selectors");
        this.executor = executor;
        this.scheduler = scheduler;
        _selectors = new ManagedSelector[selectors];
    }

This much older version of jetty-io is the general version of
Jetty that GWT 2.9 used (as well as a few earlier GWT versions).

My guess is that you have correctly updated GWT, and the expected
version of Jetty has been updated (9.4.44), except somehow you
have a dependency on the old version of jetty-io. Check the rest
of your classpath, or the particular gradle plugin you are using?


On Tuesday, August 9, 2022 at 9:20:42 AM UTC-5 Michael Joyner wrote:

Meh,

I've managed to break my GWT setup again. This time for
superdev mode. Looking for suggestions on where the (I assume)
Jetty conflict is coming from.

Getting the following stacktrace after "Module setup
completed" is logged when trying to run "./gradlew
subproject:gwtSuperDev"

java.lang.IllegalArgumentException: No selectors
    at
org.eclipse.jetty.io.SelectorManager.(SelectorManager.java:81)
    at

org.eclipse.jetty.server.ServerConnector$ServerConnectorManager.(ServerConnector.java:600)
    at

org.eclipse.jetty.server.ServerConnector.newSelectorManager(ServerConnector.java:223)
    at

org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:216)
    at
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:98)
    at
com.google.gwt.dev.codeserver.WebServer.start(WebServer.java:122)
    at
com.google.gwt.dev.codeserver.CodeServer.start(CodeServer.java:162)
    at
com.google.gwt.dev.codeserver.CodeServer.main(CodeServer.java:104)
    at
com.google.gwt.dev.codeserver.CodeServer.main(CodeServer.java:55)


We are using Gradle with the wisepersist GWT plugin:

id"org.wisepersist.gwt" version"1.1.18" id"org.gretty" version"3.0.8"

gwt {

gwtVersion ="2.10.0" src += 
files(compileJava.options.annotationProcessorGeneratedSourcesDirectory)

logLevel ="INFO" maxHeapSize ="2048M";
 modules'com.newsrx.butter.Butter' compiler{ disableClassMetadata 
=false;
 strict =true;
 style ="OBF";
 } // allow sdm on simultaneous modules // devModules
'com.newsrx.butter.Butter',
'com.newsrx.newsletter.NewsletterBrowser',
'com.newsrx.dailies.DailiesBrowser' superDev{ noPrecompile =false;
 failOnError =false;
 bindAddress ="0.0.0.0";
 } }

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

Re: GWT 2.10.0: gradle gwtSuperDev - java.lang.IllegalArgumentException: No selectors

2022-08-09 Thread Michael Conrad
So, I'm guessing that gretty jetty is leaking into gwt super dev mode 
somehow.


I added the following as a compile time dependency, and superdev mode 
seems to be working.


providedCompile"net.sourceforge.htmlunit:htmlunit:2.55.0" // to get superdev 
mode working



On 8/9/22 10:20, Michael Conrad wrote:

Meh,

I've managed to break my GWT setup again. This time for superdev mode. 
Looking for suggestions on where the (I assume) Jetty conflict is 
coming from.


Getting the following stacktrace after "Module setup completed" is 
logged when trying to run "./gradlew subproject:gwtSuperDev"


java.lang.IllegalArgumentException: No selectors
    at 
org.eclipse.jetty.io.SelectorManager.(SelectorManager.java:81)
    at 
org.eclipse.jetty.server.ServerConnector$ServerConnectorManager.(ServerConnector.java:600)
    at 
org.eclipse.jetty.server.ServerConnector.newSelectorManager(ServerConnector.java:223)
    at 
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:216)
    at 
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:98)
    at 
com.google.gwt.dev.codeserver.WebServer.start(WebServer.java:122)
    at 
com.google.gwt.dev.codeserver.CodeServer.start(CodeServer.java:162)
    at 
com.google.gwt.dev.codeserver.CodeServer.main(CodeServer.java:104)
    at 
com.google.gwt.dev.codeserver.CodeServer.main(CodeServer.java:55)



We are using Gradle with the wisepersist GWT plugin:

id"org.wisepersist.gwt" version"1.1.18" id"org.gretty" version"3.0.8"
gwt {
gwtVersion ="2.10.0" src += 
files(compileJava.options.annotationProcessorGeneratedSourcesDirectory)

logLevel ="INFO" maxHeapSize ="2048M";
 modules'com.newsrx.butter.Butter' compiler{ disableClassMetadata =false;
 strict =true;
 style ="OBF";
 } // allow sdm on simultaneous modules // devModules 
'com.newsrx.butter.Butter', 'com.newsrx.newsletter.NewsletterBrowser', 
'com.newsrx.dailies.DailiesBrowser' superDev{ noPrecompile =false;

 failOnError =false;
 bindAddress ="0.0.0.0";
 } }


--
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/48f1b448-cea9-3b41-0476-9f2ca1cac7a8%40newsrx.com.


GWT 2.10.0: gradle gwtSuperDev - java.lang.IllegalArgumentException: No selectors

2022-08-09 Thread Michael Conrad

Meh,

I've managed to break my GWT setup again. This time for superdev mode. 
Looking for suggestions on where the (I assume) Jetty conflict is coming 
from.


Getting the following stacktrace after "Module setup completed" is 
logged when trying to run "./gradlew subproject:gwtSuperDev"


java.lang.IllegalArgumentException: No selectors
    at 
org.eclipse.jetty.io.SelectorManager.(SelectorManager.java:81)
    at 
org.eclipse.jetty.server.ServerConnector$ServerConnectorManager.(ServerConnector.java:600)
    at 
org.eclipse.jetty.server.ServerConnector.newSelectorManager(ServerConnector.java:223)
    at 
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:216)
    at 
org.eclipse.jetty.server.ServerConnector.(ServerConnector.java:98)
    at 
com.google.gwt.dev.codeserver.WebServer.start(WebServer.java:122)
    at 
com.google.gwt.dev.codeserver.CodeServer.start(CodeServer.java:162)
    at 
com.google.gwt.dev.codeserver.CodeServer.main(CodeServer.java:104)
    at 
com.google.gwt.dev.codeserver.CodeServer.main(CodeServer.java:55)



We are using Gradle with the wisepersist GWT plugin:

id"org.wisepersist.gwt" version"1.1.18" id"org.gretty" version"3.0.8"

gwt {

gwtVersion ="2.10.0" src += 
files(compileJava.options.annotationProcessorGeneratedSourcesDirectory)

logLevel ="INFO" maxHeapSize ="2048M";
modules'com.newsrx.butter.Butter' compiler{ disableClassMetadata =false;
strict =true;
style ="OBF";
} // allow sdm on simultaneous modules // devModules 
'com.newsrx.butter.Butter', 'com.newsrx.newsletter.NewsletterBrowser', 
'com.newsrx.dailies.DailiesBrowser' superDev{ noPrecompile =false;

failOnError =false;
bindAddress ="0.0.0.0";
} }

--
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/d94f908e-46db-fb79-07fb-6e4bba88a944%40newsrx.com.

> Task :MainSite:dependencies


Project ':MainSite'


annotationProcessor - Annotation processors and their dependencies for source 
set 'main'.
No dependencies

apiElements - API elements for main. (n)
No dependencies

archives - Configuration for archive artifacts. (n)
No dependencies

compileClasspath - Compile classpath for source set 'main'.
+--- com.github.gwtd3:gwt-d3-api:1.3.0
|\--- com.github.gwtd3:gwt-d3-js:3.5.11
| \--- junit:junit:4.8.2
+--- com.github.tommyettinger:blazingchain:1.4.4.4
+--- com.github.gwtmaterialdesign:gwt-material:2.6.0
|+--- com.github.gwtmaterialdesign:gwt-material-jquery:2.6.0
|+--- net.sourceforge.htmlunit:htmlunit:2.23
||+--- xalan:xalan:2.7.2
|||\--- xalan:serializer:2.7.2
||+--- org.apache.commons:commons-lang3:3.4
||+--- org.apache.httpcomponents:httpclient:4.5.2
|||+--- org.apache.httpcomponents:httpcore:4.4.4
|||+--- commons-logging:commons-logging:1.2
|||\--- commons-codec:commons-codec:1.9 -> 1.10
||+--- org.apache.httpcomponents:httpmime:4.5.2
|||\--- org.apache.httpcomponents:httpclient:4.5.2 (*)
||+--- commons-codec:commons-codec:1.10
||+--- net.sourceforge.htmlunit:htmlunit-core-js:2.23
||+--- net.sourceforge.htmlunit:neko-htmlunit:2.23
|||\--- xerces:xercesImpl:2.11.0
||| \--- xml-apis:xml-apis:1.4.01
||+--- net.sourceforge.cssparser:cssparser:0.9.20
|||\--- org.w3c.css:sac:1.3
||+--- commons-io:commons-io:2.5
||+--- commons-logging:commons-logging:1.2
||\--- org.eclipse.jetty.websocket:websocket-client:9.2.18.v20160721
|| +--- org.eclipse.jetty:jetty-util:9.2.18.v20160721
|| +--- org.eclipse.jetty:jetty-io:9.2.18.v20160721
|| |\--- org.eclipse.jetty:jetty-util:9.2.18.v20160721
|| \--- 
org.eclipse.jetty.websocket:websocket-common:9.2.18.v20160721
||  +--- 
org.eclipse.jetty.websocket:websocket-api:9.2.18.v20160721
||  +--- org.eclipse.jetty:jetty-util:9.2.18.v20160721
||  \--- org.eclipse.jetty:jetty-io:9.2.18.v20160721 (*)
|+--- com.google.elemental2:elemental2-core:1.0.0-RC1
||+--- com.google.jsinterop:jsinterop-annotations:1.0.2
||\--- com.google.jsinterop:base:1.0.0-RC1
|| \--- com.google.jsinterop:jsinterop-annotations:1.0.2
|+--- com.google.elemental2:elemental2-promise:1.0.0-RC1
||+--- com.google.jsinterop:jsinterop-annotations:1.0.2
||\--- com.google.jsinterop:base:1.0.0-RC1 (*)
|+--- com.google.elemental2:elemental2-dom:1.0.0-RC1
||+--- 

Re: [ERROR] Unexpected internal compiler error | BytecodeSignatureMaker.java:59 | at com.google.gwt.dev.Compiler.main(Compiler.java:113)

2022-08-09 Thread Michael Conrad
Thanks for the assistance.

After poking around a bit, I removed the dependency and switched to using
Element2 for websock work.

On Fri, Aug 5, 2022 at 11:41 AM Jens  wrote:

> GWT (gwt-dev) depends on ASM 9.2 which supports up to Java 18. On your
> compile classpath you have gwt-websockets which depends on ASM 5.x. Seems
> like that ASM version is used during GWT compilation.
>
> ASM's ClassVisitor constructor checks the byte code version of the class
> file and if it is too high then this exception will be thrown.
>
> -- J.
>
> Michael Joyner schrieb am Mittwoch, 3. August 2022 um 22:36:02 UTC+2:
>
>>
>> Trying to update to gwt 2.10.0, have it mostly figured out, but I'm
>> getting the following stack trace.
>>
>> Any suggestions on what I need to look for?
>>
>> I've already did the exclude module's thing on multiple dependencies to
>> keep gwt 2.8 stuff out of the classpath. There is no GWT servlet stuff.
>>
>> Using Gradle, JDK 17, Linux, IntelliJU
>>
>> plugins {
>> id "java"
>> id "war"
>> id "org.wisepersist.gwt"
>> id "org.gretty"
>> }
>>
>> > Task :compileGwt
>> Compiling module com.newsrx.butter.Butter
>> [ERROR] Unexpected internal compiler error
>> java.lang.IllegalArgumentException
>> at org.objectweb.asm.ClassVisitor.(Unknown Source)
>> at org.objectweb.asm.ClassVisitor.(Unknown Source)
>> at
>> com.google.gwt.dev.javac.BytecodeSignatureMaker$CompileDependencyVisitor.(BytecodeSignatureMaker.java:59)
>> at
>> com.google.gwt.dev.javac.BytecodeSignatureMaker.visitCompileDependenciesInBytecode(BytecodeSignatureMaker.java:227)
>> at
>> com.google.gwt.dev.javac.BytecodeSignatureMaker.getCompileDependencySignature(BytecodeSignatureMaker.java:209)
>> at
>> com.google.gwt.dev.javac.CompiledClass.getSignatureHash(CompiledClass.java:166)
>> at
>> com.google.gwt.dev.javac.Dependencies$Ref.(Dependencies.java:41)
>> at
>> com.google.gwt.dev.javac.Dependencies$Ref.(Dependencies.java:36)
>> at
>> com.google.gwt.dev.javac.Dependencies.resolve(Dependencies.java:100)
>> at
>> com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:349)
>> at
>> com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:532)
>> at
>> com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:464)
>> at
>> com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:423)
>> at com.google.gwt.dev.Precompile.precompile(Precompile.java:210)
>> at com.google.gwt.dev.Precompile.precompile(Precompile.java:190)
>> at com.google.gwt.dev.Precompile.precompile(Precompile.java:131)
>> at com.google.gwt.dev.Compiler.compile(Compiler.java:192)
>> at com.google.gwt.dev.Compiler.compile(Compiler.java:143)
>> at com.google.gwt.dev.Compiler.compile(Compiler.java:132)
>> at com.google.gwt.dev.Compiler$1.run(Compiler.java:110)
>> at
>> com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
>> at
>> com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
>> at com.google.gwt.dev.Compiler.main(Compiler.java:113)
>>
>>
>> Dependency graph attached.
>>
>>
>> --
> 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/6d3ae1a3-0d62-49a6-b02e-73be14a1f6fcn%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/CALao4gMe49kW8Tf%2Bk125dOFhLe3NDTsjDEmM1SDhOpdqDWudcQ%40mail.gmail.com.


Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

2022-08-06 Thread Michael Conrad
My company is also migrating everything to JDK 17. The less opportunity for
bitrot in future versions, the better.

On Sat, Aug 6, 2022 at 11:06 AM Manfred Tremmel 
wrote:

> In my company Java 8 was dropped long ago, at the moment the migration
> from
> Java 11 to 17 is in progress. So from my side, let's cut off the old stuff.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/7868638.WIiY39HZoD%40t470
> .
>

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


Re: net.ltgt.gwt.maven and testing in multi-module project structure?

2022-08-03 Thread Michael Conrad
Did you give the shared module a gwt.xml file? Did you inherit in the main
project's gwt.xml the shared module's gwt.xml file?

On Wed, Aug 3, 2022 at 8:48 PM Slava Imeshev  wrote:

> Continuing the journey, in this multi-module client/shared/server
> structure, is it possible to have the shared code in a package different
> from the client?
>
> I get
>
> "No source code is available for type
> com.effectiveem.app.gwt.shared.GapAnalysisLineItemVO; did you forget to
> inherit a required module?
> [ERROR] Hint: Check the inheritance chain from your module; it may not be
> inheriting a required module or a module may not be adding its source path
> entries properly"
>
> The client sits in com.effectiveem.app.gwt.client.
>
> Client's pom sets the module name to
>
> com.effectiveem.app.gwt.client.EemApp
>
>
> On Wednesday, July 13, 2022 at 1:53:19 AM UTC-7 t.br...@gmail.com wrote:
>
>> On Wednesday, July 13, 2022 at 3:06:37 AM UTC+2 ime...@gmail.com wrote:
>>
>>> Thank you, the setting the  did it.
>>>
>>
>> FYI, using a GWTTestSuite can improve performance (that's why it's the
>> default in the plugin, because it favors best practices):
>> https://www.gwtproject.org/doc/latest/DevGuideTesting.html#DevGuideJUnitSuites
>>
>>
>>> My next question about testing is, what are the expectations for the
>>> test module? Are we still required to provide a separate JUnit.gwt.xml?
>>>
>>
>> You've never been (or at least not for many many years) as GWT will
>> synthesize a module that inherits both com.google.gwt.junit.JUnit and the
>> module your GWTTestCase's getModuleName() returns.
>> The gwt-maven-plugin itself has no specific expectations either, so
>> https://www.gwtproject.org/doc/latest/DevGuideTesting.html should apply
>> as-is (I haven't re-read it though, but that's the goal of the plugin, to
>> be a "thin" wrapper that only wires things that are specific to Maven, e.g.
>> src/main/java, computing the classpath from dependencies, etc.)
>>
>> --
> 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/64fe3efb-04f5-431a-b8e1-a56d83904246n%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/CAFHWztw1Wi7aHnR%2BxnjiZnO1r87d27i1BKfyJWK%2BGHm9mSwMfQ%40mail.gmail.com.


[ERROR] Unexpected internal compiler error | BytecodeSignatureMaker.java:59 | at com.google.gwt.dev.Compiler.main(Compiler.java:113)

2022-08-03 Thread Michael Conrad


Trying to update to gwt 2.10.0, have it mostly figured out, but I'm 
getting the following stack trace.


Any suggestions on what I need to look for?

I've already did the exclude module's thing on multiple dependencies to 
keep gwt 2.8 stuff out of the classpath. There is no GWT servlet stuff.


Using Gradle, JDK 17, Linux, IntelliJU

plugins {
    id "java"
    id "war"
    id "org.wisepersist.gwt"
    id "org.gretty"
}

> Task :compileGwt
Compiling module com.newsrx.butter.Butter
[ERROR] Unexpected internal compiler error
java.lang.IllegalArgumentException
    at org.objectweb.asm.ClassVisitor.(Unknown Source)
    at org.objectweb.asm.ClassVisitor.(Unknown Source)
    at 
com.google.gwt.dev.javac.BytecodeSignatureMaker$CompileDependencyVisitor.(BytecodeSignatureMaker.java:59)
    at 
com.google.gwt.dev.javac.BytecodeSignatureMaker.visitCompileDependenciesInBytecode(BytecodeSignatureMaker.java:227)
    at 
com.google.gwt.dev.javac.BytecodeSignatureMaker.getCompileDependencySignature(BytecodeSignatureMaker.java:209)
    at 
com.google.gwt.dev.javac.CompiledClass.getSignatureHash(CompiledClass.java:166)
    at 
com.google.gwt.dev.javac.Dependencies$Ref.(Dependencies.java:41)
    at 
com.google.gwt.dev.javac.Dependencies$Ref.(Dependencies.java:36)
    at 
com.google.gwt.dev.javac.Dependencies.resolve(Dependencies.java:100)
    at 
com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:349)
    at 
com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:532)
    at 
com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:464)
    at 
com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:423)

    at com.google.gwt.dev.Precompile.precompile(Precompile.java:210)
    at com.google.gwt.dev.Precompile.precompile(Precompile.java:190)
    at com.google.gwt.dev.Precompile.precompile(Precompile.java:131)
    at com.google.gwt.dev.Compiler.compile(Compiler.java:192)
    at com.google.gwt.dev.Compiler.compile(Compiler.java:143)
    at com.google.gwt.dev.Compiler.compile(Compiler.java:132)
    at com.google.gwt.dev.Compiler$1.run(Compiler.java:110)
    at 
com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
    at 
com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)

    at com.google.gwt.dev.Compiler.main(Compiler.java:113)


Dependency graph attached.

--
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/4359819d-3580-dcf9-4c8c-a91521c4ae26%40newsrx.com.

> Task :dependencies


Root project 'Butter'


annotationProcessor - Annotation processors and their dependencies for source 
set 'main'.
No dependencies

apiElements - API elements for main. (n)
No dependencies

archives - Configuration for archive artifacts. (n)
No dependencies

compileClasspath - Compile classpath for source set 'main'.
+--- org.gwtproject:gwt-user:2.10.0
|+--- com.google.jsinterop:jsinterop-annotations:2.0.0
|+--- javax.validation:validation-api:1.0.0.GA
|+--- javax.servlet:javax.servlet-api:3.1.0 -> 4.0.1
|\--- org.w3c.css:sac:1.3
+--- project :ClinicaltrialShared
+--- project :ButterShared
+--- project :SHARED-POJOS
+--- project :QueryObjects
+--- project :ObservableObjects
+--- project :SharedInterfaces
+--- project :DailiesShared
+--- org.eclipse.jdt:org.eclipse.jdt.annotation:2.2.600
+--- com.google.elemental2:elemental2-dom:1.1.0
|+--- com.google.jsinterop:jsinterop-annotations:2.0.0
|+--- com.google.jsinterop:base:1.0.0
||\--- com.google.jsinterop:jsinterop-annotations:1.0.2 -> 2.0.0
|+--- com.google.elemental2:elemental2-core:1.1.0
||+--- com.google.jsinterop:jsinterop-annotations:2.0.0
||+--- com.google.jsinterop:base:1.0.0 (*)
||\--- com.google.elemental2:elemental2-promise:1.1.0
|| +--- com.google.jsinterop:jsinterop-annotations:2.0.0
|| \--- com.google.jsinterop:base:1.0.0 (*)
|\--- com.google.elemental2:elemental2-promise:1.1.0 (*)
+--- com.google.elemental2:elemental2-core:1.1.0 (*)
+--- com.google.elemental2:elemental2-promise:1.1.0 (*)
+--- com.github.gwtd3:gwt-d3-api:1.3.0
|\--- com.github.gwtd3:gwt-d3-js:3.5.11
| \--- junit:junit:4.8.2
+--- com.github.tommyettinger:blazingchain:1.4.4.4
+--- com.github.gwtmaterialdesign:gwt-material:2.6.0
|+--- com.github.gwtmaterialdesign:gwt-material-jquery:2.6.0
|+--- net.sourceforge.htmlunit:htmlunit:2.23
||+--- 

Re: Compatibility of GWT 2.10.0 with GXT 2.3.1.a

2022-07-20 Thread Michael Conrad
If you publish your work to a jitpack compatible public git repo and 
then follow the jitpack.io instructions, you could provide a 
Maven/Gradle ready dependency for others to use.


On 7/20/22 07:36, Ricardo Serathiuk wrote:

I have explained in another similar thread the steps:
https://groups.google.com/g/google-web-toolkit/c/IZRriHLTWxA/m/DIerF5bzAgAJ

Tips:
* You need to use this jar: 
https://mvnrepository.com/artifact/com.extjs/gxt/2.3.1a-gwt22
* Extract the jar source code (.xml and .java files, remove all .class 
files) and create an internal project with the source code.

* Try to see the errors and fix one by one.
* In com.extjs.gxt.ui.client.image.XImages, change its to extends 
ClientBundle and change all to AbstractImagePrototype ImageResource. 
After that, fix all errors.
* Most of the errors are about setHeading, AbstractImagePrototype and 
the com.google.gwt.user.client.Element deprecation.


I have made all the core changes in a day. And some fixes and 
improvements during the years. I do not remember all the changes, but 
it is a guide to start.


Em qua., 20 de jul. de 2022 às 06:14, mmo  escreveu:

> We have fixed some things on GXT 2.3.1a.  With some fixes, you
can run perfectly the GXT 2.3.1a in GWT 2.2+ (GWT 2.9.0 and 2.10.0
included).

Would you mind to elaborate on these fixes? Have you documented
these somewhere?

On Monday, July 18, 2022 at 6:05:57 PM UTC+2 Ricardo Serathiuk wrote:

I work with an application using GWT 2.10.0 and GXT 2.3.1a. We
have fixed some things on GXT 2.3.1a. With some fixes, you can
run perfectly the GXT 2.3.1a in GWT 2.2+ (GWT 2.9.0 and 2.10.0
included).

-- 
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/a4aa86c7-d74a-48ef-a6c0-d687be2018aan%40googlegroups.com

.



--
Ricardo Serathiuk
--
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/CALVte5xy9Hdi%2BmykRRbXwOvdsa8DKPi_Q%3Dy8rJ94SxOwNkQhFA%40mail.gmail.com 
.


--
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/1ebcbe41-2325-91f4-9779-2ff5685a1a60%40newsrx.com.


Re: 'Throwable.HasJavaThrowable' has invalid name '?'.

2022-06-30 Thread Michael Conrad
How many of these libs are you thinking would need converting to JS for 
the client bundle?


At a glance, it really looks like you got a dependency chain fubar. The 
GWT client code should not have any kind of dependency to 
java.sql.DataSource as an example. It looks like you are trying to 
compile server side only code as a GWT dependency.


On 6/30/22 10:22, mmo wrote:
Anyway - after settings said option I got much more GWT compiler 
output and there are tons of error messages with the pattern "No 
source code is available for type . did you forget to inherit a 
required module".
Unfortunately, the classes referenced are misc. stuff 
from com.google.gwt.user, com.google.common.collect, 
org.apache.commons.collections, org.springframework.security.core, 
etc., i.e. all classes that I can not shift into the UI's shared or 
client folder. How can one make the sources of these classes known to 
the GWT compiler?


--
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/cfb5b417-e96e-4adc-4083-22e63ae88d7c%40newsrx.com.


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

2022-06-30 Thread Michael Conrad
I didn't think that java.sql.DataSource is emulated by GWT. Looks like you
are pulling in server side only type stuff from somewhere?

On Thu, Jun 30, 2022 at 3:30 AM Thomas Broyer  wrote:

> Didn't legacy devmode also only work with JDK 8?
>
> On Wednesday, June 29, 2022 at 10:46:30 PM UTC+2 Jens wrote:
>
>> Without being able to see the project setup this is tough to answer.
>>
>> However regardless of the exception you are seeing: Classic/Legacy
>> DevMode will not work with GWT 2.9.0 correctly, because GWT 2.9.0 already
>> uses JsInterop internally in its Java SDK emulation (e.g. java.util.Date
>> uses it). JsInterop is not supported by classic/legacy DevMode. With GWT
>> 2.9.0 you have to use SuperDevMode to have a functional Java SDK emulation
>> during development.
>>
>> -- J.
>>
>> abhiy...@gmail.com schrieb am Mittwoch, 29. Juni 2022 um 21:58:40 UTC+2:
>>
>>> Hi Team,
>>>
>>> I am trying to start classic DEV mode in eclipse through GWT eclipse
>>> plugin .
>>> I am using GWT 2.9.0 + Java 11 combination.
>>> I am getting below error. Can you help me in resolving the below error:
>>>
>>> [b]Caused by: java.lang.ClassNotFoundException: javax.sql.DataSource
>>> at
>>> com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload$WebAppClassLoaderExtension.findClass(JettyLauncher.java:478)
>>> ~[gwt-dev-2.9.0.jar:?]
>>> at
>>> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:441)
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/6d3569b5-b7f0-4c2e-918c-c342b6803441n%40googlegroups.com
> 
> .
>

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


Re: 'Throwable.HasJavaThrowable' has invalid name '?'.

2022-06-29 Thread Michael Conrad

I see the following in your stack trace.

It would probably help to track the issue down if you set the GWT 
compile to strict.


On 6/29/22 13:10, mmo wrote:

Ignored 5 units with compilation errors in first pass.


--
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/5c422a07-ac4e-989c-15a8-735c028cdd1a%40newsrx.com.


Re: Using JsInterop to create JS object literals

2022-06-28 Thread Michael Conrad
try adding name = "Object" so that it uses an empty javascript Object as
the wrapped item.

I found this via Googling:

@JsType(namespace = JsPackage.GLOBAL, isNative = true, name = "Object")
public class MyPluginConfig {
@JsProperty public void set(String str);
@JsProperty public String get();
...
}

Ref: https://stackoverflow.com/a/36329387/12407701


On Tue, Jun 28, 2022 at 6:24 PM Nicolas Chamouard 
wrote:

> Yes, it does not change anything :
>
> @JsType(*isNative*=*true*, *namespace* = JsPackage.*GLOBAL*)
>
> *public* *class* OptionOverrides {
>
>
> @JsConstructor
>
> *public* OptionOverrides() {}
>
>
>
> @JsProperty
>
> *public* *native* String getInitialView();
>
> @JsProperty
>
> *public* *native* *void* setInitialView(String initialView);
>
> }
>
>
> Still the same error : *$wnd.OptionOverrides is not a constructor*
>
> Le mardi 28 juin 2022 à 23:27:08 UTC+2, m.conr...@gmail.com a écrit :
>
>> Have you tried giving the class a constructor?
>>
>>
>> On Tue, Jun 28, 2022 at 4:04 PM Nicolas Chamouard <
>> ncham...@alara-group.fr> wrote:
>>
>>> Hello,
>>>
>>> I am using JsInterop to integrate FullCalendar to my GWT application.
>>> As described here https://fullcalendar.io/docs/initialize-globals, I am
>>> supposed to create an object literal and pass it to the Calendar()
>>> constructor.
>>>
>>> I have managed to create this class :
>>>
>>> @JsType(*namespace* = JsPackage.*GLOBAL*)
>>>
>>> *public* *class* OptionOverrides {
>>>
>>>
>>> @JsProperty
>>>
>>> *public* *native* String getInitialView();
>>>
>>> @JsProperty
>>>
>>> *public* *native* *void* setInitialView(String initialView);
>>>
>>> }
>>>
>>> It works but the FullCalendar complains about all the Java Object stuff
>>> that is translated to javascript : equals(), hashCode(), etc
>>>
>>> I have tried to add* isNative=true* to my class, but in this case i
>>> cannot instantiate it in Java (error : $wnd.OptionOverrides is not a
>>> constructor)
>>>
>>> Is there an other way to do this, am I missing something here ?
>>>
>>> Thanks
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-web-tool...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit/a03c881a-48d4-4892-9fae-7719bc9a57b8n%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/4d8099ea-3a37-4026-b459-f228e35ca59bn%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/CAFHWztzapXtRGkSs1foFVkDQBv1bgn-sk70%3D%2BCyokKGJ1Y6AQA%40mail.gmail.com.


Re: Using JsInterop to create JS object literals

2022-06-28 Thread Michael Conrad
Have you tried giving the class a constructor?


On Tue, Jun 28, 2022 at 4:04 PM Nicolas Chamouard 
wrote:

> Hello,
>
> I am using JsInterop to integrate FullCalendar to my GWT application.
> As described here https://fullcalendar.io/docs/initialize-globals, I am
> supposed to create an object literal and pass it to the Calendar()
> constructor.
>
> I have managed to create this class :
>
> @JsType(*namespace* = JsPackage.*GLOBAL*)
>
> *public* *class* OptionOverrides {
>
>
> @JsProperty
>
> *public* *native* String getInitialView();
>
> @JsProperty
>
> *public* *native* *void* setInitialView(String initialView);
>
> }
>
> It works but the FullCalendar complains about all the Java Object stuff
> that is translated to javascript : equals(), hashCode(), etc
>
> I have tried to add* isNative=true* to my class, but in this case i
> cannot instantiate it in Java (error : $wnd.OptionOverrides is not a
> constructor)
>
> Is there an other way to do this, am I missing something here ?
>
> 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/a03c881a-48d4-4892-9fae-7719bc9a57b8n%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/CAFHWztz%2Bs1cvtpEM341n0RiYhEstQ-iu5BUAvjC0jk4WnoU8ug%40mail.gmail.com.


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

2022-05-23 Thread Michael Conrad
Take a look at domino-rest: https://github.com/DominoKit/domino-rest

You can use a shared POJOs project between the client and server projects
with common POJOs annotated with Jackson JSON annotations to transfer data
as JSON objects between client and server in a bidirectional fashion.

On Mon, May 23, 2022 at 6:33 PM hprc  wrote:

> I think it's a great design method.
> Client side and server
> Side communication should be loosely coupled.
>
> However, although I understand this merit, maintenance is possible more
> intuitively because the Java object set in the shared package is used for
> communication between the two.
> Normally, when using the RESET API etc., conversion work such as parsing
> is required.
>
> 2022年5月24日火曜日 2:37:05 UTC+9 Rogelio Flores:
>
>> The big disadvantage that I see with gwt-rpc is that it ties your
>> client-side with your server-side code (if you change anything related to
>> your models/rpc on the client side, you also have to update your serve-side
>> code, otherwise, it will not work). To me that in itself is a big
>> disadvantage. With something like REST APIs, your client and server side
>> code remain decoupled, giving you more freedom.
>>
>> On Friday, May 20, 2022 at 8:14:58 AM UTC-6 ralph.f...@gmail.com wrote:
>>
>>> why not use gwt-rpc? I am a lazy guy and am happily using it for more
>>> than 10 years now - I even use the generated serializers in combination
>>> with WebSockets. What can possibly go wrong here...?
>>>
>>> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer  wrote:
>>>
 Short answer: don't start using RequestFactory now, it's been
 practically unmaintained for years.

 Long answer: there's not really a longer answer actually, it's OK to
 keep using RF in existing projects (if you can't afford moving to something
 else), but don't start anything with it now.
 (I wouldn't start anything new with gwt-rpc either BTW, but YMMV)

 On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote:

> I know that GWT Request Factor plays an important role in Java object
> persistence and communication between client and server.
> However, on the server and client, even one object needs to generate
> related classes and interfaces, and then annotation settings etc. need to
> be set for each class and interface.
> It is complicated and has a lot of trouble to create.
>
> Originally, these things are like plugins, and it is desirable to
> select one object and generate a related class, but do you all know?
>
> I have been using GWT for over 10 years, but I do not use
> "RequestFactory" and operate only with objects like Map by RPC
> communication.
> This can simplify the entire system and greatly reduce the effort
> required to create it.
>
> GWT RequestFactory
> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html
>
 --
 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/66b91749-8cb7-4b84-964d-82c2996adca8n%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/f52fd06a-b57b-4a47-bc53-f376a6e179e8n%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/CAFHWztyJ%2BizrXLgB040Wxj%3DJ3tO0Z91xKmpLnmrLfwswhx%2Bq_A%40mail.gmail.com.


Re: Pbs with GWT + Eclipse + Jetty + Neo4J

2021-10-12 Thread Michael Conrad
You didn't provide the exception stack trace It is needed for anyone 
to be able to help you.


On 10/12/21 1:09 PM, Guillen Antonio wrote:

Hi all,

I am struggling with a pb using RPC:

When I use the service to create and store my objects in my DB (Neo4J) 
using remote service, all is Fine.
When I try to load my objects all is ok in my service class and in 
Neo4J as well. But at the last line of the method public static void 
writeResponse(ServletContext servletContext, HttpServletResponse 
response, String responseContent, boolean gzipResponse)  throws 
IOException {


I have an exception.

Here is the method of com.google.gwt.user.server.rpc.RPCServletUtils


  public static void writeResponse(ServletContext servletContext,
  HttpServletResponse response, String responseContent, boolean 
gzipResponse)

  throws IOException {

    byte[] responseBytes = responseContent.getBytes(CHARSET_UTF8);
    if (gzipResponse) {
  // Compress the reply and adjust headers.
  //
  ByteArrayOutputStream output = null;
  GZIPOutputStream gzipOutputStream = null;
  Throwable caught = null;
  try {
    output = new ByteArrayOutputStream(responseBytes.length);
    gzipOutputStream = new GZIPOutputStream(output);
    gzipOutputStream.write(responseBytes);
    gzipOutputStream.finish();
    gzipOutputStream.flush();
    setGzipEncodingHeader(response);
    responseBytes = output.toByteArray();
  } catch (IOException e) {
    caught = e;
  } finally {
    if (null != gzipOutputStream) {
  gzipOutputStream.close();
    }
    if (null != output) {
  output.close();
    }
  }

  if (caught != null) {
    servletContext.log("Unable to compress response", caught);
response.sendError(HttpServletResponse.SC_INTERNAL_SERVER_ERROR);
    return;
  }
    }

    // Send the reply.
    //
    response.setContentLength(responseBytes.length);
    response.setContentType(CONTENT_TYPE_APPLICATION_JSON_UTF8);
    response.setStatus(HttpServletResponse.SC_OK);
    response.setHeader(CONTENT_DISPOSITION, ATTACHMENT);
*response.getOutputStream().write(responseBytes);*
  }

And the return message on my console is:

200 - POST /spotgwt/spotData (127.0.0.1) 501 bytes
   Request headers
  Host: 127.0.0.1:8887
  User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) 
Gecko/20100101 Firefox/92.0

  Accept: */*
  Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3
  Accept-Encoding: gzip, deflate
  Content-Type: text/x-gwt-rpc; charset=utf-8
  X-GWT-Permutation: A082E84D087467DED16699006D694A7B
  X-GWT-Module-Base: http://127.0.0.1:8887/spotgwt/
  Content-Length: 228
  Origin: http://127.0.0.1:8887
  DNT: 1
  Connection: keep-alive
  Referer: http://127.0.0.1:8887/SpotGWT.html
  Sec-Fetch-Dest: empty
  Sec-Fetch-Mode: cors
  Sec-Fetch-Site: same-origin
   Response headers
  Date: Tue, 12 Oct 2021 16:57:51 GMT
  Content-Encoding: gzip
  Content-Length: 501
  Content-Type: application/json; charset=utf-8
  Content-Disposition: attachment

Can you help me.

Thanks a lot

Antonio
--
You received this message because you are subscribed to the Google 
Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to google-web-toolkit+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/9073c1bb-20b6-4c19-90af-d462e8034716n%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/69bfd13b-3ddd-74a4-98ab-1e9eaa37f698%40newsrx.com.


Re: GWT Eclipse plug in

2021-10-08 Thread Michael Conrad
I vote for Gradle.

On Fri, Oct 8, 2021 at 6:47 AM Craig Mitchell 
wrote:

> 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*
>
> On Friday, 8 October 2021 at 7:47:03 pm UTC+11 lofid...@gmail.com wrote:
>
>> 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:
>>
>>> 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
> 

Re: Frequent Java runtime crashes when compiling GWT code

2021-08-06 Thread Michael Conrad
*ouch*

I'm not sure where to proceed from here without being able to recreate the
issue.

On Fri, Aug 6, 2021 at 10:15 AM mmo  wrote:

> On Thursday, August 5, 2021 at 6:14:25 PM UTC+2 m.conr...@gmail.com wrote:
>
>> Can you try testing with adoptopenjdk?
>>
>> I've had issues with stock openjdk before with odd crashes that don't
>> happen with adoptopenjdk.
>>
>
> I *am* using AdoptOpenJDK (jdk8u292-b10 )
>
>
> --
> 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/be7a6b23-6b40-4d07-8864-c51603002a5bn%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/CAFHWztz%2BHSTYFdZGLV9yd5EiNTDc-d1q_BxeYpNNzpPoVvjCEQ%40mail.gmail.com.


Re: Frequent Java runtime crashes when compiling GWT code

2021-08-05 Thread Michael Conrad
Can you try testing with adoptopenjdk?

I've had issues with stock openjdk before with odd crashes that don't
happen with adoptopenjdk.

On Thu, Aug 5, 2021 at 11:28 AM mmo  wrote:

> We are seeing frequent Java runtime crashes (and I *really* mean often:
> about 2 in 3 compilations crash) while building our GWT-based application.
>
> I haven't been able to figure out, precisely *what* is triggering this
> (see the log-snippet below). It happens more or less right at the beginning
> of that goal and from what I read there it seems to be in the Maven plugin
> that jars up our module with the GWT stuff in it.
>
> Are others seeing this or similar Java runtime crashes as well? I recently
> upgraded the JDK that our CI-environment is using (we are bound to Java-8
> for the time being) hoping this would improve the situation, but its still
> the same and it getting mighty tedious!
>
> Any ideas or suggestions?
>
> Just in case: it's NOT a HW-issue! The build environment is running in an
> OpenShift-based virtual environment and these crashes happen for *this*
> project only. We have other GWT-based applications and these build fine in
> the same environment. I have seen similar crashes before (but really *very*
> seldom only). But with *this* projects it's getting out-of-hand lately.
>
>
> ...
> 16:57:22 [INFO] 16:57:22 [INFO] --- maven-jar-plugin:2.4:jar (default-jar)
> @ module-gwt-jar ---
> 16:57:22 *** Error in
> `/tmp/tools/hudson.model.JDK/jdk8u292/jdk8u292-b10/bin/java': realloc():
> invalid next size: 0x7fabb8829570 ***
> 16:57:22 *** Error in
> `/tmp/tools/hudson.model.JDK/jdk8u292/jdk8u292-b10/bin/java': realloc():
> invalid next size: 0x7fabb8829570 ***
> 16:57:22 === Backtrace: =
> 16:57:22 === Backtrace: =
> 16:57:22 /lib64/libc.so.6(+0x7f474)[0x7fac2976c474]
> 16:57:22 /lib64/libc.so.6(+0x7f474)[0x7fac2976c474]
> 16:57:22 /lib64/libc.so.6(+0x84861)[0x7fac29771861]
> 16:57:22 /lib64/libc.so.6(+0x84861)[0x7fac29771861]
> 16:57:22 /lib64/libc.so.6(realloc+0x1d2)[0x7fac29772e12]
> 16:57:22 /lib64/libc.so.6(realloc+0x1d2)[0x7fac29772e12]
> 16:57:22 /lib64/libnss_wrapper.so(+0x388f)[0x7fac2a0f688f]
> 16:57:22 /lib64/libnss_wrapper.so(+0x388f)[0x7fac2a0f688f]
> 16:57:22 /lib64/libnss_wrapper.so(+0x58e9)[0x7fac2a0f88e9]
> 16:57:22 /lib64/libnss_wrapper.so(+0x58e9)[0x7fac2a0f88e9]
> 16:57:22 /lib64/libnss_wrapper.so(+0x5dcd)[0x7fac2a0f8dcd]
> 16:57:22 /lib64/libnss_wrapper.so(+0x5dcd)[0x7fac2a0f8dcd]
> 16:57:22 /lib64/libnss_wrapper.so(+0x5edb)[0x7fac2a0f8edb]
> 16:57:22 /lib64/libnss_wrapper.so(+0x5edb)[0x7fac2a0f8edb]
> 16:57:22 /lib64/libnss_wrapper.so(getgrgid_r+0x59)[0x7fac2a0fac99]
> 16:57:22 /lib64/libnss_wrapper.so(getgrgid_r+0x59)[0x7fac2a0fac99]
> 16:57:22
> /tmp/tools/hudson.model.JDK/jdk8u292/jdk8u292-b10/jre/lib/amd64/libnio.so(Java_sun_nio_fs_UnixNativeDispatcher_getgrgid+0x8e)[0x7fac0b7f529e]
> 16:57:22
> /tmp/tools/hudson.model.JDK/jdk8u292/jdk8u292-b10/jre/lib/amd64/libnio.so(Java_sun_nio_fs_UnixNativeDispatcher_getgrgid+0x8e)[0x7fac0b7f529e]
> 16:57:22 [0x7fac149c0087] 16:57:22 [0x7fac149c0087]
> 16:57:22 === Memory map: 
> 16:57:22 === Memory map: 
> 16:57:22 e000-e3f0 rw-p  00:00 0
> 16:57:22 e3f0-f558 ---p  00:00 0
> 16:57:22 f558-1 rw-p  00:00 0
> 16:57:22 1-10036 rw-p  00:00 0
> 16:57:22 10036-14000 ---p  00:00 0
> 
>
> --
> 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/2fe00c4c-77a1-46b9-988a-c99724b9fb9cn%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/CAFHWzty7nO2Bo4S6o9PCg%3DhRCC5eTD1c30N71fmSsyquDfHZkg%40mail.gmail.com.


Re: Java Method Overloading

2021-04-21 Thread Michael Conrad
The error reads like you need to mark one the methods as not exported to JS

On Wed, Apr 21, 2021 at 3:45 PM lofid...@gmail.com 
wrote:

> Hi,
>
> I could confirm your problem. Here is an example:
>
>
> https://github.com/lofidewanto/gwt-overloading/blob/main/src/main/java/com/github/lofi/client/Calculator.java
>
> [INFO] --- gwt-maven-plugin:1.0.0:compile (default) @
> jsinterop-simple-example ---
> [INFO] Compiling module com.github.lofi.Calculator
> [INFO]Errors in com/github/lofi/client/Calculator.java
> [INFO]   [ERROR] Line 33: 'void Calculator.setValue(Float)' and 'void
> Calculator.setValue(Integer)' cannot both use the same JavaScript name
> 'setValue'.
> [INFO]   [WARN] Line 33: [unusable-by-js] Type of parameter 'value' in
> 'void Calculator.setValue(Float)' is not usable by but exposed to
> JavaScript.
> [INFO]   [WARN] Line 37: [unusable-by-js] Type of parameter 'value' in
> 'void Calculator.setValue(Integer)' is not usable by but exposed to
> JavaScript.
> [INFO][WARN] Suppress "[unusable-by-js]" warnings by adding a
> `@SuppressWarnings("unusable-by-js")` annotation to the corresponding
> member.
>
> pierre...@gmail.com schrieb am Mittwoch, 21. April 2021 um 08:50:31 UTC+2:
>
>> The value was an Integer but is now an Float:
>>
>> private  Float  value;
>>
>> The "normal" setter is now:
>> public void setValue(Float value) {
>> this.value = value;
>> }
>> Then, I added this method  to accomodate the current app   :
>> public void setValue(Integer value) {
>> this.value = value.floatValue();
>> }
>> Thanks for any hint
>> Pierre
>>
>>
>> Le mardi 20 avril 2021 à 18:54:28 UTC+2, lofid...@gmail.com a écrit :
>>
>>> Could you show me the whole class?
>>>
>>> this.value cannot be an Integer...
>>>
>>> 
>>>
>>> // This won't work in Java - Type mismatch...
>>> private Integer value;
>>>
>>> public void setValue(Integer value) {
>>>this.value = value.floatValue();
>>> }
>>>
>>> pierre...@gmail.com schrieb am Dienstag, 20. April 2021 um 11:34:57
>>> UTC+2:
>>>
 I have a model class Item with a Integer value. I builded an app using
 this model.
 For a new particular case, the value should be a Float as well.
 So I changed the type of value to Float and regenerate setter/getter.
 In order to not change the current app, I try to create a overloading
 method :
 public void setValue(Integer value) {
 this.value = value.floatValue();
 }
 At java level, everything seems ok, all compile errors are solved. But
 at GWT compilation, the call of this method complains with :
 [ERROR] Line 93: The method setValue(Float) in the type
 Item is not applicable for the arguments (Integer)
  like if GWT doesnot see my method setValue(Integer).

  Am I missing something ? Is there a way to make this works without
 creating a second separate attribute ?
 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/eef0bc47-a2a3-4cf7-b5fb-5a65d2b77163n%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/CAFHWztyTERMjnuqO4-1XzY_SoVs2NO_xJMyFuLs%2BOYM0NHPOPw%40mail.gmail.com.


Re: [gwt-contrib] Asking for decision on DevMode embedded Jetty support

2021-04-15 Thread Michael Conrad

  
  
Ok,

Sounds like we wouldn't be affected, we always run our stuff via
TomCat with a one liner using the gretty Gradle plugin.

-Mike

On 4/15/21 10:07 AM, Thomas Broyer
  wrote:


  
  If you use the gwtSuperDev task, or if you use the
gwtDev task but set noserver=true, then it won't impact you.
You're then already starting another web server to serve your
server-side code (and your host page).
If you use the gwtDev task and did not set
  noserver=true, then you'd have to move to gwtSuperDev and a
  separate server (e.g. through the Gretty plugin); or move to
  the de.ecoso.gwt plugin which does not use DevMode yet
  provides a single task that starts both CodeServer and a
  separate Jetty server: https://github.com/esoco/gwt-gradle-plugin
  
  
  
On Thu, Apr 15, 2021 at 3:04
  PM Michael Conrad <mich...@newsrx.com> wrote:


   How would this impact Super Dev Mode in Gradle?

We use Gradle with
'org.wisepersist:gwt-gradle-plugin:1.1.8'.


  
On Thu, Apr 15, 2021,
  09:56 Paul Robinson <ukcue...@gmail.com>
  wrote:


  I used the built in Jetty server until
a year or so ago. Occasionally I have to use the
older version in development as we haven't upgraded
everybody in production to the new version yet.


From a development perspective, I
  find running a separate code server and Jetty to
  be much more productive.


Whenever I need to restart, it's
  usually only Jetty I need to restart, and it's
  much faster to not restart the code server part as
  well.


So there may be an extra step, but
  I'm much happier with it this way.


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

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


  
  -- 
  You received this message because you are subscribed to a
  topic in the Google Groups "GWT Contributors" group.
  To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit-contributors/iU9hckIab2o/unsubscribe.
  To unsubscribe from this group and all its topics, send an
  email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
  To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/e226962d-8433-2e7a-9622-353baddea646%40newsrx.com.

  
  
  
  
  -- 
  Thomas Broyer
/tɔ.ma.bʁwa.je/
  -- 
  You received this message because you are subscribed to the Google
  Groups "GWT Contributors" group.
  To unsubscribe from this group and stop receiving emails from it,
  send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
  To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEayHEOHFCL4YfWG2Gb--H3d9Amxr8BhPrwCF35QYu9RwpJKWQ%40mail.gmail.com.


  




-- 
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit htt

Re: [gwt-contrib] Asking for decision on DevMode embedded Jetty support

2021-04-15 Thread Michael Conrad

  
  
How would this impact Super Dev Mode in Gradle?

We use Gradle with 'org.wisepersist:gwt-gradle-plugin:1.1.8'.


  
On Thu, Apr 15, 2021, 09:56
  Paul Robinson  wrote:


  I used the built in Jetty server until a year
or so ago. Occasionally I have to use the older version in
development as we haven't upgraded everybody in production
to the new version yet.


From a development perspective, I find
  running a separate code server and Jetty to be much more
  productive.


Whenever I need to restart, it's usually
  only Jetty I need to restart, and it's much faster to not
  restart the code server part as well.


So there may be an extra step, but I'm much
  happier with it this way.


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

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


  




-- 
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/e226962d-8433-2e7a-9622-353baddea646%40newsrx.com.


Re: New Article "10 Best Java Frameworks to Use in 2021"

2021-03-10 Thread Michael Conrad
At work we started out with Maven and quickly discovered you couldn't do
dependencies to other projects unless they shared a parent POM. Things
quickly started becoming unwieldy. Discovered "loosely coupled" projects
with Gradle. We haven't looked back.

On Wed, Mar 10, 2021 at 10:25 AM Thomas Broyer  wrote:

>
>
> On Wednesday, March 10, 2021 at 4:13:03 PM UTC+1 pavel@gmail.com
> wrote:
>
>> We had the same problem with maven but at the end, maven's multi-module
>> project and profiles helped to solve *hack around* it.
>>
>
> There, fixed it for you 
>
> Also see https://www.cloudbees.com/blog/maven-profiles-and-maven-way and
> https://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/
> among others, by prominent Maven PMC members.
> (and yet, gwt-maven-archetypes use a "dev" profile 路, but it's know to be
> kind of hackish in places due to Maven and jetty-maven-plugin's limitations)
>
> --
> 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/cd2b1c5a-f10a-4200-85d0-e9ed96279585n%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/CAFHWztxdgKt%3DC%2BzHM%3DcOuaaKvs4%3D0fzLShK_u-fWSUg8aDB1hg%40mail.gmail.com.


Re: New Article "10 Best Java Frameworks to Use in 2021"

2021-03-09 Thread Michael Conrad
JDBI3 is the answer to ORMS.

It's not an ORM. per-se :-)

And the Sql Object component allows strong typing in a much easier way.

You use annotations to define sql statements with parameters in interface
classes. Or, optionally, sql files.

https://jdbi.org/

At work I ended up converting all our DB accesses, both raw and JPA over to
JDBI3.

Here is an example:
https://github.com/CherokeeLanguage/AudioQualityVote/blob/main/audio-quality-vote-db/src/main/java/com/cherokeelessons/audio/quality/db/AudioQualityVoteDao.java


On Tue, Mar 9, 2021 at 3:10 AM Gordan Krešić 
wrote:

> On 09. 03. 2021. 08:29, Craig Mitchell wrote:
> >
> > Too late.  Flame war!  ;P  But seriously, what's wrong with using
> Hibernate
> > as JPA provider?  Okay, yes, there is nothing to learn, it does all its
> > magic behind the scenes, but is there something better?  Or maybe using
> JPA
> > is bad, and we go back to pure SQL?  I'm curious.
>
> I did try various ORMs, including some for non-relational databases (but
> then it's not an ORM, but... what?) but never figured out the benefits.
> They
> all demo well, but when I go past most basic usage, they always felt more
> like an obstacle than a tool.
>
> Only case where I would agree using ORM saves time are projects with high
> number of tables compared to complexity of their usage (simple SELECTs on
> hundreds or thousands of tables). But, I don't have such a project in my
> portfolio.
>
> Can you name few other benefits? Type safety? "Compile-time checks" of SQL
> "queries"? I can see *some* benefits there, but hardly ones that justifies
> learning another, fairly complex, DSL on top of SQL.
>
>  From time to time I found a survey with question like "Which ORM do you
> use?" and there are usually low-double-digits of percentages of users who
> claim to be using "raw JDBC with SQL". It gives me hope that I'm not a
> lone
> lunatic, but still, 80+% of users must know *something*, right?
>
> So, if we assume that someone already knows SQL (and it's an 'if', I
> know),
> what would be the benefits of using ORM of any kind?
>
> Bonus question: I've been looking for years for a most simplistic SQL
> templating library, mainly for things like reusing WHERE clauses (i
> usually
> end up with fairly complex ones used in multiple queries), linking '?'
> with
> setters on PreparedStatements and things like that. I even wrote small lib
> because I was tired of experimenting, but I seriously doubt that I'm the
> only one with this need and would instead like to contribute to already
> existing project rather than maintain my own.
>
> -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/21b217be-c3b1-884e-8a98-4709ae383d7b%40steatoda.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/CAFHWztzuWPOsC2Wh%3DM4a-tGgi_tS8s-pqi9%2B9_jiS31-x9yvPg%40mail.gmail.com.


Re: GWT-apps and OAuth 2.0

2021-03-04 Thread Michael Conrad
For the client/GWT Maven info see:
https://jitpack.io/#CherokeeLanguage/gwt-oauth2

For the server side I'm using com.google.api-client:google-api-client





On Thu, Mar 4, 2021 at 2:18 AM Luca Morettoni  wrote:

> is there a maven package with that patch or you have included directly the
> source code?
> Thanks!
>
> On 3 Mar 2021, at 13:42, Michael Conrad  wrote:
>
> Yes.
>
> I had to apply a fix to the code for inter-window communications.
>
>
>
> --
> Luca Morettoni  | http://www.morettoni.net
> http://it.linkedin.com/in/morettoni/ | http://twitter.com/morettoni
>
> --
> 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/A55646C2-F8EC-41CC-8E37-038F0EE8268A%40morettoni.net
> <https://groups.google.com/d/msgid/google-web-toolkit/A55646C2-F8EC-41CC-8E37-038F0EE8268A%40morettoni.net?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/CAFHWztzBV2JYUbQows68jBLNt3m21c85Ucj-QaDM6Hmv0r_Qfw%40mail.gmail.com.


Re: GWT-apps and OAuth 2.0

2021-03-03 Thread Michael Conrad
Yes.

I had to apply a fix to the code for inter-window communications.

See: https://github.com/freddyboucher/gwt-oauth2/pull/13

On Wed, Mar 3, 2021 at 6:51 AM Luca Morettoni  wrote:

> seems forked from the one I posted… 
>
> On 2 Mar 2021, at 19:18, Michael Conrad  wrote:
>
> I'm using a version of gwt-oauth2 for Google OAUTH logins in this project:
>  https://github.com/CherokeeLanguage/AudioQualityVote.
>
> The version of gwt-oauth2 I'm using is at:
> https://github.com/CherokeeLanguage/gwt-oauth2
>
>
>
> --
> Luca Morettoni  | http://www.morettoni.net
> http://it.linkedin.com/in/morettoni/ | http://twitter.com/morettoni
>
> --
> 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/FF1B76C6-C286-47BA-AB9B-9B9848909238%40morettoni.net
> <https://groups.google.com/d/msgid/google-web-toolkit/FF1B76C6-C286-47BA-AB9B-9B9848909238%40morettoni.net?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/CAFHWztypTRzdcXtvnxiOA%3DpUhUWgOCZwNcv3Um%3DvO61dq2MGyA%40mail.gmail.com.


Re: GWT-apps and OAuth 2.0

2021-03-02 Thread Michael Conrad
I'm using a version of gwt-oauth2 for Google OAUTH logins in this project:
https://github.com/CherokeeLanguage/AudioQualityVote.

The version of gwt-oauth2 I'm using is at:
https://github.com/CherokeeLanguage/gwt-oauth2

On Tue, Mar 2, 2021 at 11:28 AM Luca Morettoni  wrote:

> Hello, I have a quite old application that actually uses an internal
> implementation to manage the user access to the system: a login screen that
> send to the server username/password and gets a token used around in the
> different functionalities of the application.
> Now a customer instead of using this “server-side” authentication  wants
> to use his own OAuth 2.0 server inside his network.
>
> Looking around I found this project:
> https://github.com/freddyboucher/gwt-oauth2 but if you have any other
> recommendation and/or projects I will appreciate it a lot!
>
> Thanks in advance to all!
>
> --
> Luca Morettoni  | http://www.morettoni.net
> http://it.linkedin.com/in/morettoni/ | http://twitter.com/morettoni
>
> --
> 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/DAF84368-2EE6-4C27-AC35-FA308B3F50C4%40morettoni.net
> 
> .
>

-- 
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/CAFHWztxXw9eOR5xs0cqKjK1mez6Aw-rC_t8dVjTnH%2BJBF0rHPA%40mail.gmail.com.


Re: gwt-places annotation processor in Eclipse

2021-02-27 Thread Michael Conrad
I think you need to add the "goomph" plugin to your build.gradle, close the
project, then run the shell script below, then open the project and do a
clean.

- buildscript {
-   repositories {
- //...
- }}
- dependencies {//...
- classpath "com.diffplug.gradle:goomph:3.24.0" //Required for
apt processing in Eclipse.
- }
- }

apply plugin: 'com.diffplug.eclipse.apt' //Required for apt processing
in Eclipse.

The shell script:

#!/bin/bash

- set -e
- set -o pipefail
-
- cd "$(dirname "$0")"
-
- rm .settings/org.eclipse.jdt.apt.core.prefs || true
- rm .settings/org.eclipse.jdt.core.prefs || true
- ../gradlew eclipseJdtApt
-
- rm .factorypath || true
- ../gradlew eclipseFactorypath
-
- ../gradlew eclipseJdt


On Sat, Feb 27, 2021 at 5:06 AM Gordan Krešić 
wrote:

> Did anyone got Eclipse to invoke annotation processor from gwt-places
> module
> that should generate PlaceHistoryMapper implementations?
>
> I have interface that extends
> org.gwtproject.place.shared.PlaceHistoryMapper
> and is annotated with org.gwtproject.place.shared.WithTokenizers. I'm
> creating instances by instancing class with my class name suffixed with
> "Impl".
>
> However, it seems Eclipse doesn't run annotation processor and
> consequently
> can't find implementation class.
>
> Gradle build works fine.
>
> I even explicitly specified gwt-places-processor.jar in project settings
> in
> Eclipse (Java Compiler -> Annotation Processing -> Factory Path), but
> folder
> where generated files should be placed (.apt_generated) is still empty.
>
> Any ideas?
>
> Sidenote: it seems Eclipse has some issue with annotation processors
> classpath, because I had to add auto-common.jar
> (PlaceHistoryMapperProcessor
> is based on BasicAnnotationProcessor from auto-common) on Factory Path,
> too.
>
> -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/0ff5fa68-0de1-f84e-8298-5c6a16c19b64%40steatoda.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/CAFHWztzM_aSvmBC-ZxCapSvYesXHA9wvV-11gV2POdroPuw%3DsA%40mail.gmail.com.


Re: GWT 2.9, java 11, tomcat 10.0.2 - standard gwt example having RPC error, 404

2021-02-22 Thread Michael Conrad
It is usually /CONTEXT-AKA-WAR-NAME/URL-PATTERN

On Mon, Feb 22, 2021 at 8:49 AM 'Michel Pikkaart' via GWT Users <
google-web-toolkit@googlegroups.com> wrote:

> Thank you for reading. I tried for serveral days but I cannot find why
> this is going wrong.
>
> I have build a standard Tomcat v10.0.2 server. I have setup my Eclipse
> with java jdk 11 and using GWT 2.9.0
>
> I Generated the sample code of GWT 2.9.0 with java jdk 11. I compile this
> succes fully. I deployed the war file to the tomcat server, but then it
> give me a RPC 404 error.
>
> According to the tutorials which I read on http://gwtproject.org/ this
> should all be in the right place, right coded...still I got the a 404 error
> on a RPC call.. which means the service isn't there where it suppose to be.
>
> Could somebody please point me in the right direction...
>
> I already tried. /local.appletree.Banana/greet
> but I have a rename-to in the gwt.xml so banana should be allright.
>
> Thank you in advance Michel.
>
> Banana.gwt.xml
> 
>"http://gwtproject.org/doctype/2.9.0/gwt-module.dtd;>
> 
>   
>   
>   
>   
>   
>   
> 
>
> WEB.XML
> 
> http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>   http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd;
>  version="2.5"
>  xmlns="http://java.sun.com/xml/ns/javaee;>
>   
> greetServlet
>
> local.appletree.server.GreetingServiceImpl
>   
>   
> greetServlet
> /banana/greet
>   
>   
> Banana.html
>   
> 
>
> Java interface..
> package local.appletree.client;
> import com.google.gwt.user.client.rpc.RemoteService;
> import com.google.gwt.user.client.rpc.RemoteServiceRelativePath;
> @RemoteServiceRelativePath("greet")
> public interface GreetingService extends RemoteService {
> String greetServer(String name) throws IllegalArgumentException;
> }
>
> --
> 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/976b7279-2e77-4842-b96e-efd4c2ee4797n%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/CAFHWztwNhpFALQ2%2Bqpm2da%3DAhrMXeSUAFoY1m_w8JOnQQZ0zkQ%40mail.gmail.com.


Re: How to pass a build number to a gwt app?

2020-11-05 Thread Michael Conrad
Any particular reason to not use an annotation processor? Especially as
GWT.create is deprecated?

On Thu, Nov 5, 2020 at 2:36 AM Joker Joker  wrote:

> I want to share solution for gradle based project.
> This solution allows to get any build's properties on client/server.
>
> *1) Add to build.gradle*
> ...
> task createProperties(dependsOn: processResources) {
> doLast {
>  new
> File("$buildDir/resources/main/yourmodule/shared/IVersion.properties").withWriter
> { w ->
>   Properties p = new Properties()
>   p['version'] = project.version.toString()
>   p.store w, null
>  }
> }
> }
>
> classes {
>   dependsOn createProperties
> }
> ...
> *2) Add IVersion.java:*
>
> package yourmodule.shared;
> import com.google.gwt.i18n.client.Constants;
> public interface IVersion extends Constants {
>String version();
> }
>
> *3) Add to your code*
> *...*
> public static final IVersion versionResource = GWT.create(IVersion.class);
> ...
> *4) Get version value on client side:*
> *...*
> versionResource.version();
> ...
> *5) Get version on server side:*
> *...*
> InputStream stream = this.getClass().getResourceAsStream(
> "/yourmodule/shared/IVersion.properties");
> InputStreamReader readerIs;
> try {
>   readerIs = new InputStreamReader(stream, "UTF-8");
>   messageInstance = new PropertyResourceBundle(readerIs);
>   messageInstance.getString("version");
> } catch (Exception e) {
>   e.printStackTrace();
> }
> *...*
>
> вторник, 13 марта 2018 г. в 13:12:30 UTC+4, Bruno Salmon:
>
>> Thanks Thomas, I'm using GWT 2.8.2 so I tried your first suggestion and
>> it works :-)
>>
>> I just declared the property in my gwt.xml module file:
>>
>> 
>>
>>
>>  and set its value (with the maven property which is set by Jenkins) when
>> calling your plugin in the configuation section:
>>
>> 
>> 
>> -setProperty
>> build.number=${build.number}
>> 
>> 
>>
>>
>> Then System.getProperty("build.number") returns the expected value :-)
>>
>> Thank you
>>
>> On Monday, 12 March 2018 23:27:17 UTC+1, Thomas Broyer wrote:
>>>
>>> Easiest with recent GWT version would be to declare a
>>> , get it using System.getProperty(), and set it
>>> with --property.
>>>
>>> With older versions, use Maven filtering on a properties file you use
>>> with a com.google.gwt.i18n.client.Constants; or have a look at Mojo's Java
>>> template plugin.
>>>
>> --
> 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/aa760b0f-d641-4741-bb50-d58fb5585499n%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/CAFHWzty%2BkAFxBiL3g08fBx%3DCbr0eRKYBcoLGSGncPOWAeai2rA%40mail.gmail.com.


Re: Strange GWT-RPC bug upgrading from 2.7 to 2.8+

2020-10-06 Thread Michael Conrad
I don't know if this applies to your situation, but we had an issue similar
to this (a long time ago) that was caused by shadowing properties from
parent classes in child classes.

On Tue, Oct 6, 2020 at 2:15 PM lofid...@gmail.com 
wrote:

> If you need a fast solution I would recommend to use professional help
> like Vertispan: https://www.vertispan.com
>
> Colin knows the transpiler inside out 
>
> @Jens: thanks for your debugging tips, I would add your tips to my GWT
> deck.
> pha...@gmail.com schrieb am Sonntag, 4. Oktober 2020 um 05:16:11 UTC+2:
>
>> Thanks Jens, I did what you asked and have the following in the debugger:
>>
>> [image: Screen Shot 2020-10-03 at 8.11.01 PM.png]
>>
>> [image: Screen Shot 2020-10-03 at 8.11.17 PM.png]
>>
>> What do you make of this?
>>
>> I don't see any duplicate GWT on the classpath (project is a pretty
>> simple maven setup).
>>
>> Thanks,
>> Aaron
>>
>> On Friday, October 2, 2020 at 4:31:37 AM UTC-7 Jens wrote:
>>
>>> And there you have it... absolutely no idea why it's malfunctioning in
 this way. Any help is greatly appreciated!

>>>
>>> Ok in sourcemaps it looks indeed a bit weird. However there will be
>>> additional JS code executed to convert java.lang.Integer into a primitive
>>> int which is represented by JS number. That conversion seems to produce
>>> undefined.
>>>
>>> Please use newest GWT SDK and either launch SuperDevMode or GWT compiler
>>> with these additional command line parameters: "-strict -style PRETTY
>>> -XmethodNameDisplayMode ABBREVIATED".
>>>
>>> When doing so you make sure that no compile issue will be skipped
>>> (-strict), your JS code will be more readable (-style PRETTY) and you can
>>> more easily search for Java method names in the generated JS code
>>> (-XmethodName...). Next you should disable JS Source Maps support in Chrome
>>> Dev Tools to see the JS code.
>>> To find the above method you would search the JS for
>>> "AbstractSerializationStreamWriter.addString" and should find a JS line
>>> that sets a displayName property. Above that line you will find the method
>>> implementation.
>>>
>>> In the typical case to convert java.lang.Integer to primitive int, GWT
>>> should have generated JS that calls the intValue() method of Integer.
>>>
>>>
>>> If something looks weird you might also want to double check that you do
>>> not have multiple versions of GWT in class path. That sometimes happened
>>> people when upgrading GWT and also using a bunch of third party libraries.
>>> Sometimes 3rd party libraries also emulate JRE classes which then do not
>>> match the JRE emulation in GWT SDK. This can be an additional possibility
>>> for unexpected JS behavior.
>>>
>>>
>>> -- J.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/e6492c9f-e3e1-4933-b1eb-5bbaca5e1866n%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/CAFHWztxx3AoAFwe7zLL9cR8xJeZ-fnwj%3DSH7CPJLF8QA02U-WQ%40mail.gmail.com.


Re: GWT history with push state

2020-10-03 Thread Michael Conrad
Have you looked at "nalu"?

https://github.com/NaluKit/nalu

Starting with version 1.1.0 Nalu supports the use of hash less URLs.

Not sure about the Domino-Kit stuff


On Sat, Oct 3, 2020 at 7:00 AM jhon tonini  wrote:

> Is possible to use push state in GWT history  (Es. /users, /newuser)
> instead of "#" ?
>
>
> --
> 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/a929a4a1-d268-436a-baa6-4dab200a6c40n%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/CAFHWztwFZXd7pL8-TdALSYmgBSKoapk%2BEKuvc5GXXHSaOW4bCw%40mail.gmail.com.


Re: Pbs with Debug GWT application with Eclipse

2020-08-24 Thread Michael Conrad

  
  
Modern GWT is debugged in the Browser using "SuperDev Mode".

There is an SDM add-on for Eclipse, but I've never used, so can't
attest to its effectiveness.

On 8/24/20 1:47 PM, Guillen Antonio
  wrote:


  
  Hi all
  I use the last 2020-06 version of eclipse, with the modelling
tools (EMF), I use the Eclipse plugin define in the picture
below.The application work fine, but just for the fun if I want
try to debug it:
  

  I select break points, in the moduleLoad method.
  I launch using Debug AS  Devlopment mode with Jetty

The appli run like is I lauch it wit(h Run As  Devlopment
  mode with Jetty.


I don't understand where I do a mistake.
Can you help me please.


Antonio

  
  
  
  
  
  -- 
  You received this message because you are subscribed to the Google
  Groups "GWT Users" group.
  To unsubscribe from this group and stop receiving emails from it,
  send an email to google-web-toolkit+unsubscr...@googlegroups.com.
  To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/62c0c823-efff-43b6-a135-de207fa5ed59n%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/ac33e9d9-7bf6-d976-fc6a-4e8be3000781%40newsrx.com.


Re: GWT SDM hanging on recompiles?

2020-08-07 Thread Michael Conrad
Yes. 2.9

Was also having this issue sometimes with 2.8.x

On Thu, Aug 6, 2020, 7:15 PM Peter Donald  wrote:

> Are you on GWT 2.9.x? I have seen this intermittently after upgrading
> to GWT 2.9.x. Unfortunately I always forget to get a thread dump to
> see where it has got stuck.
>
> FWIW We run under JDK8, with no server component from IntelliJ IDE.
>
> On Fri, Aug 7, 2020 at 6:18 AM Michael Conrad  wrote:
> >
> > Greetings everyone.
> >
> > Hopefully someone can tell me what I need to change.
> >
> > When running SDM via Gradle, after so many recompiles, it will stop with
> something similar to:
> >
> >  GET /recompile/gwt
> >Job com.newsrx.ButterAdmin_1_7
> >   starting job: com.newsrx.ButterAdmin_1_7
> >
> > and never actually do the compile.
> >
> > A non-hung recompile looks like:
> >
> > GET /recompile/gwt
> >Job com.newsrx.ButterAdmin_1_6
> >   starting job: com.newsrx.ButterAdmin_1_6
> >   binding: locale=default
> >   binding: user.agent=safari
> >   Compiling module com.newsrx.ButterAdmin
> >  Unification traversed 876 fields and methods and 394 types. 17
> are considered part of the current module and 26 had all of their fields
> and methods traversed.
> >  Compiling 1 permutation
> > Compiling permutation 0...
> > Linking per-type JS with 17 new/changed types.
> > Source Maps Enabled
> >  Compile of permutations succeeded
> >  Compilation succeeded -- 2.086s
> >   Linking into
> /home/michael/git/ButterAdmin/ButterAdmin-client/build/gwt/work/com.newsrx.ButterAdmin/compile-8/war/gwt;
> Writing extras to
> /home/michael/git/ButterAdmin/ButterAdmin-client/build/gwt/work/com.newsrx.ButterAdmin/compile-8/extras/gwt
> >  Link succeeded
> >  Linking succeeded -- 0.186s
> >   2.475s total -- Compile completed
> >
> >
> > To fix the issue I have to kill it and start it over.
> >
> > Pointers as to what might be causing this?
> >
> > AdoptOpenJDK11 -> with -release 8.
> >
> > --
> > 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/b4f358f7-3783-db02-e31b-be305b5e9119%40newsrx.com
> .
>
>
>
> --
> Cheers,
>
> Peter Donald
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc6c%2Bpp0VdqOujvPN4vcAkYSxusEuBwkOgUDtrOsBxWAaQ%40mail.gmail.com
> .
>

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


GWT SDM hanging on recompiles?

2020-08-06 Thread Michael Conrad

  
  
Greetings everyone.

Hopefully someone can tell me what I need to change.

When running SDM via Gradle, after so many recompiles, it will stop
with something similar to:

 GET /recompile/gwt
   Job com.newsrx.ButterAdmin_1_7
  starting job: com.newsrx.ButterAdmin_1_7

and never actually do the compile.

A non-hung recompile looks like:

GET /recompile/gwt
   Job com.newsrx.ButterAdmin_1_6
  starting job: com.newsrx.ButterAdmin_1_6
  binding: locale=default
  binding: user.agent=safari
  Compiling module com.newsrx.ButterAdmin
 Unification traversed 876 fields and methods and 394 types.
17 are considered part of the current module and 26 had all of their
fields and methods traversed.
 Compiling 1 permutation
    Compiling permutation 0...
    Linking per-type JS with 17 new/changed types.
    Source Maps Enabled
 Compile of permutations succeeded
 Compilation succeeded -- 2.086s
  Linking into
/home/michael/git/ButterAdmin/ButterAdmin-client/build/gwt/work/com.newsrx.ButterAdmin/compile-8/war/gwt;
Writing extras to
/home/michael/git/ButterAdmin/ButterAdmin-client/build/gwt/work/com.newsrx.ButterAdmin/compile-8/extras/gwt
 Link succeeded
 Linking succeeded -- 0.186s
  2.475s total -- Compile completed


To fix the issue I have to kill it and start it over.

Pointers as to what might be causing this?

AdoptOpenJDK11 -> with -release 8.
  




-- 
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/b4f358f7-3783-db02-e31b-be305b5e9119%40newsrx.com.


Re: How to migrate gwt 2.8.1 project to gwt 2.9.0 in eclipse?

2020-07-28 Thread Michael Conrad
   java project.



I have only src and war directories in the repository, so
  no files in the root dir.
In the src there are numerous gwt modules directories, and
  in the war, there are html/css static files for gwt modules
  and in the WEB-INF dir:


c:\p\eclipse\fejlesztoi2>dir /b /s  "war/WEB-INF"
  c:\p\eclipse\fejlesztoi2\war\WEB-INF\glassfish-web.xml
  c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib
  c:\p\eclipse\fejlesztoi2\war\WEB-INF\web.xml
  c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\activation.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\commons-fileupload-1.2.1.jar
  c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gchart.jar
  c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gwt-ajaxloader.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gwt-maps-api-3.10.0-alpha-8-SNAPSHOT.jar
  c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\gwt-servlet.jar
c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\javax.xml.soap-api-1.4.0.jar
  c:\p\eclipse\fejlesztoi2\war\WEB-INF\lib\mail.jar




    what's next?





On Tuesday, July 28, 2020 at 5:46:07 PM UTC+2, Michael Conrad
wrote:

  Use Maven or Gradle to configure the project
and let Eclipse import it as a Maven or Gradle project.
  
  
  
On Tue, Jul 28, 2020 at 11:42 AM mb user <muse...@gmail.com> wrote:


  
Hi,


After a storage crash, I had to reinstall my
  development computer.


Now I have eclipse 4.16 and a gwt 2.8.1 project
  source imported from svn.


This project was built with the eclipse gwt plugin,
  but I cannot install it to eclipse 4.16.


What is the recommended way to achieve compile and
  deploy (create war file) in eclipse, if you have the
  project source?






  
  -- 
  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/b10ca891-b6d0-4fdf-a2ee-e0296cb03fc2o%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/60e9fd36-d19e-400b-905a-19f8ba068d16o%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/71d879f4-98a1-c1fb-d83d-1f12b281aafd%40newsrx.com.


Re: How to migrate gwt 2.8.1 project to gwt 2.9.0 in eclipse?

2020-07-28 Thread Michael Conrad
Use Maven or Gradle to configure the project and let Eclipse import it as a
Maven or Gradle project.

On Tue, Jul 28, 2020 at 11:42 AM mb user  wrote:

> Hi,
>
> After a storage crash, I had to reinstall my development computer.
>
> Now I have eclipse 4.16 and a gwt 2.8.1 project source imported from svn.
>
> This project was built with the eclipse gwt plugin, but I cannot install
> it to eclipse 4.16.
>
> What is the recommended way to achieve compile and deploy (create war
> file) in eclipse, if you have the project source?
>
>
>
> --
> 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/b10ca891-b6d0-4fdf-a2ee-e0296cb03fc2o%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/CAFHWztyMZY2ozMHTkBnCDs2m0fuqLPWzXFV4VhbEODYT%3D3wvVQ%40mail.gmail.com.


Re: Is there any way to use GWT 2.9 with Java 11 using Eclipse GWT plugin?

2020-07-27 Thread Michael Conrad
I use Gradle to configure Eclipse.
For JDK11 to be used as if it were JDK8 in Eclipse I have added:

sourceCompatibility = JavaVersion.VERSION_1_8
targetCompatibility = JavaVersion.VERSION_1_8
if (JavaVersion.current() > JavaVersion.VERSION_1_8) {
tasks.withType(JavaCompile) {
   options.compilerArgs.addAll(["--release", "8"])
}
}

On Mon, Jul 27, 2020 at 6:12 PM Shahram Zadeh 
wrote:

> We have a huge GWT project (GWT 2.7, JDK 1.7, Eclipse) everything works
> perfect. We are planning to upgrade to Java 11 and GWT 2.9 which has been
> recently released. However Java 1.7 is retiring and getting obsolete we
> have to move on and upgrade. Since last week we are trying to create a
> development environment like the existing one but there is no success. I
> was wondering whether anyone out there is struggling with the same issue,
> any hint, solution or hacking the eclipse plugin would be greatly
> appreciated.
>
> Eclipse plugin comes with GWT (2.7 and 2.8.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/1bdedb59-090d-4c8c-ba72-258e991ae060n%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/CAFHWztwN%3D%2BcH2DUNG56FvsNgqzTTBGs%3DLTT-GegwykR0zWyJ8Q%40mail.gmail.com.


Re: Do Google Web Toolkit's touch events support Windows tablets?

2020-07-27 Thread Michael Conrad
you will need to check and see what event is actually generated for the
windows 10 tablet in the dom and hook those.

On Mon, Jul 27, 2020 at 2:52 PM Andy Langer  wrote:

> Hi all. Currently working on a webapp using GWT. I currently have a
> feature working with touch events on a Canvas. The feature itself works
> perfectly fine on every device but windows tablets (surface pro). Is there
> something special I have to do for this, or does GWT have no way of doing
> 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/940db851-82c2-4f1a-99b8-8ef653d1dadao%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/CAFHWztyTiqrHbn8YUP10tbyEZcJ8dZ-%2BLu%3DTnKdos9Jgax3R_w%40mail.gmail.com.


Re: java.sql.Date - java.util.Date serialization issue

2020-07-23 Thread Michael Conrad

  
  
From experience here, passing java.sql.Date as java.util.Date is
opening a barrel of woe.

Weird timezone issues start cropping up as java.sql.Date is not
supposed to have an hour/minute/second component with meaning and
would be better if timezone agnostic like LocalDate or
LocalDateTime, but it isn't.

Keep in mind when getting back dates from the client, that the time
zone of the client can cause you to generate a sql date that is off
by a day + or -.

If you need to pass dates back and forth that are being used in
database operations, make sure you take this into account, or just
use wrapped strings that are parsed on the client and server to
each's local time zone as needed.

Casting a subclass to a superclass is pretty much a no-op.


On 7/23/20 9:46 AM, Ralph Fiergolla
  wrote:


  
  I know it is quite some time ago since you posted
this, but I just now (2020!) ran into the very same issue (using
the very same workaraound). Is there any real solution for this
by now?

On Tuesday, August 22, 2006 at 2:32:24 AM UTC+2, StudyBlue
wrote:
Casting
  'non-serializable' objects to 'serializable' objects alone is
  not enough!
  1.  According to the serialization documentation for the
GWT,
java.util.Date is serializable.
(
http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.DeveloperGuide.RemoteProcedureCalls.SerializableTypes.html
)
2.  According to the java docs, java.sql.Date is a subclass
of
java.util.Date.
( http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Date.html
)
3.  According to you-can-look-it-up-yourself you can validly
cast a
subclass to the type of the superclass.
  Intuitively, you should be able to send java.sql.Dates
across the RPC
boundary simply by casting them.  Unfortunately, the
reflection calls
appear to look for the most specific type possible, not
necessarily
whatever it was cast to last.  (Maybe that's intended.
 Maybe I'm
totally off on my blind guess for what's causing this.)  No
matter how
I cast I java.sql.Date to java.util.Date, the call would
always throw
an exception claiming I was trying to send a java.sql.Date.
 Eventually
I got fed up with that and created a new java.util.Date from
the
java.sql.Date's getTime() method.  Creating an entirely new
object
solved the problem, but I'm assuming that's taking more time
and
processing than a simple cast.  If there's any way to make a
sufficient
cast, I'd love to hear it.

  
  -- 
  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/f971938a-06f4-403f-b737-161835da1bf8o%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/34f86b72-5e32-062e-7dbe-6271c0b1f7ce%40newsrx.com.


Re: [gwt-contrib] Thurs July 16 2020 GWT community call

2020-07-21 Thread Michael Conrad

  
  
How did it go?

On 7/15/20 5:02 PM, Colin Alworth
  wrote:


  
  
We have a shorter itinerary this week - I'll record a short
  piece on j2cl-maven-plugin and how to start a project with it,
  try using pieces from the ecosystem.


Dmitrii, Ahmad and I will continue our brainstorming about
  efficiently producing both optimized output and minimizing the
  work the compiler does for i18n/cldr generated code.



  


  




-- 
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/864efc55-2de0-3db7-be88-e3fe9170da42%40newsrx.com.


Re: [gwt-contrib] Resolving cycle dependency between gwt-safehtml & gwt-safecss

2020-06-26 Thread Michael Conrad

  
  
As CSS and HTML are so closely tied to each other
in use, having them as separate modules makes me think of
excessive DB normalization (and the potential evils thereof).

On 6/25/20 4:43 PM, Matt Davis wrote:


  
  +1 to merge. 
  
  
On Thu, Jun 25, 2020, 4:26 PM
  Juan Pablo Gardella 
  wrote:


  +1 to merge them. It seems the simplest
solution.
  
  
  
On Thu, 25 Jun 2020 at
  17:23, Colin Alworth 
  wrote:


  One potential option could be moving the tests into
gwt-safecss, and only release them together - the
release process through sonatype will permit you to push
more than one set of artifacts, test them in the staging
repo, and then release to central together. That would
imply using either local artifacts to build gwt-safecss
(instead of pulling from central), or temporarily adding
the staging repo to the pom.
  
  
  It does seem simpler to just merge to gwt-safehtml -
especially since I doubt that gwt-safecss is often used
by itself.
  
  
  
On Thursday, June 25,
  2020 at 3:19:05 PM UTC-5 juan_pablo_gardella wrote:


  
Not too much options I think, see https://stackoverflow.com/questions/55429921/how-to-fix-cyclic-dependency-between-java-modules


Maybe a new common shared module (maven
  artifact in this case) or merge safehtml and
  safecss into a new one and let them deprecated.



Juan

  
  
  
On Thu, 25 Jun
  2020 at 17:14, 'Frank Hossfeld' via GWT
  Contributors 
  wrote:

  
  

  
To prepare GWT for j2cl we need to move the
  modules out of GWT, replace generators with
  ATP, etc. This is in progress and the first
  modules (SNAPSHOT) are released.


Migrating gwt-safehtml and gwt-safecss runs
  into a problem, cause gwt-safehtml depends on
  gwt-safecss and gwt-safecss depends on
  gwt-safehtml. This is a serious issue, cause
  one can not be build and tested without the
  other. 


To solve this issue, we are looking for
  solutions.


One solution might be to move the tests out
  of gwt-safehtml. But then gwt-safehtml needs
  to be build and deployed before the tests run
  and might be deployed with failing tests. That
  looks like a bad solution.  At the moment the
  idea is to move the sources and tests from
  gwt-safecss into gwt-safehtml and delete
  gwt-safecss. This will remove the cycle
  dependency between these two modules, but
  doing so, the module will be the first module
  that contains two old modules in one new.


Any other ideas how to solve this issue?
  

  
  

  -- 
  You received this message because you are
  subscribed to the Google Groups "GWT Contributors"
  group.
  To unsubscribe from this group and stop receiving
  emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
  To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/a8d6c785-c8d9-4eba-8cc2-0b42ecac1124o%40googlegroups.com.

  

  
  -- 
  

Re: [gwt-contrib] Re: Is there a doc which indicates which licenses are acceptable for imported code for use by the JRE Emulation?

2020-06-16 Thread Michael Conrad
While I haven't been considering any particular sources, should I have 
to time and the inclination at the same time to look into it, was 
wanting to have a clearer picture of what is or isn't a good path to follow.


On 6/16/20 11:42 AM, Colin Alworth wrote:


As an example, there is code included in GWT emulation that isn't 
copyrighted by Google, such as some emulation for javax.validation and 
hibernate validation implementation. These are licensed under APLv2 also.


Beyond this, I would suggest asking about specific cases/ideas you 
have in mind?


On Tuesday, June 16, 2020 at 9:57:06 AM UTC-5, Michael Conrad wrote:

Is there a doc which indicates which licenses are acceptable for
imported code for use by the JRE Emulation?

--
You received this message because you are subscribed to the Google 
Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to 
google-web-toolkit-contributors+unsubscr...@googlegroups.com 
<mailto:google-web-toolkit-contributors+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/cf078843-6da5-4ed1-8896-b5162becc90do%40googlegroups.com 
<https://groups.google.com/d/msgid/google-web-toolkit-contributors/cf078843-6da5-4ed1-8896-b5162becc90do%40googlegroups.com?utm_medium=email_source=footer>.


--
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/2b419363-87dd-7233-d0b9-c7886205085e%40newsrx.com.


[gwt-contrib] Is there a doc which indicates which licenses are acceptable for imported code for use by the JRE Emulation?

2020-06-16 Thread Michael Conrad
Is there a doc which indicates which licenses are acceptable for 
imported code for use by the JRE Emulation?


--
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/321a7b63-f8f3-722a-052b-d91c40453d10%40newsrx.com.


Re: GWT Super devmode is not working for me

2020-06-11 Thread Michael Conrad
I'm really not sure how well SDM in the much older GWT 2.6.1 works in 
comparison with most recent stable release of GWT 2.9.0. There do exist 
SDM plugins for both Eclipse and IntelliJ I believe.


On 6/11/20 10:36 AM, ruwan samaraweera wrote:

Hi,
I'm using gwt since so many years back. To debug my application those 
days I've used gwt devmode. But now the plugin is not support in 
modern browser(Im using lates version of Chrome). So I tried to used 
super devmode. But unfortunately I couldn't able to configure it 
correct way. It is given many errors and I cant debug my application.
Actually Im developing web application using gwt 2.6.1 and java 1.8 
and deploying it in tomcat9 webserver.

My configuration as follows.

gwt.xml file
--
















name="com.smartclient.theme.enterpriseblue.EnterpriseBlueResources"/>










value='FALSE'/>










Hear I've add xsiframe linker and other configuration tag as well
Apart from that I've added following tags in my host page.

script src="App/sc/modules/ISC_Core.js">











Im using ant target to build application and making war file and place 
it tomcat9. So same way Im using ant target to run superdevmode as 
follows.


classname="com.google.gwt.dev.codeserver.CodeServer">

   
  
  
   
   
   
   
   
   value="-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=${proj.gwt.debug.client.debug.port}" 
/>


   
 



 In properties.xml file
 name="proj.gwt.debug.sdk" location="D:Project\myApp\gwt\gwt-2.6.1" /> 
 


But when I'm running ant target it is giving following error
 [ERROR] The Cross-Site-Iframe linker does not support 

Re: GWT 2.9 compatiblity with GXT 2.3.1a

2020-06-11 Thread Michael Conrad
Even if other GXT users share their experiences with that framework in 
combination with GWT 2.9.0, especially considering the old version of 
GXT specified, unless the GXT team runs tests and validates against 
2.9.0 and the GXT team specifically gives the "officially supported" 
label. You should not consider the combination officially supported. And 
I think it would be for the GXT team to determine that, not the GWT team.


On 6/11/20 8:13 AM, Priya Kolekar wrote:

Hi All,

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

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

--
You received this message because you are subscribed to the Google 
Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to google-web-toolkit+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2829460d-9008-4a2a-a09c-8fcbdd76e3f7o%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/e876f60c-1520-34c8-dac4-de6fecc19307%40newsrx.com.


Re: GWT RPC Serialization on web and app server

2020-06-05 Thread Michael Conrad
Does your servlet context path exactly match the request path as sent by 
the browser?


On 6/5/20 3:23 AM, Snehalkumar Rangnenwar wrote:

Hey Entlog ,
 what was the solution you applied in jmeter to fix the 
incompatibility issue ? please let us know as well.


Thank in advance,
skay


On Wednesday, January 15, 2014 at 7:10:34 PM UTC+5:30, Benoit 
GUILLOTIN wrote:


HI Entlog,

How did U fix ur problem on Jmeter with the .gwt.rpc file ?
Im still looking for fixing this IncompatibleRemoteServiceException.

Thanks for ur answer.
Benoit

Le jeudi 23 mai 2013 12:30:21 UTC+2, Entlog a écrit :

Awesome!! Thanks. I was having problems with a jmeter test and
I saw your solution...it's really that! The jmeter captured
request had the reference to the hash for another deployed
environment and when trying to test against another deployed
war it was throwing the serializable error. Now I know how to
fix it :)...

El jueves, 1 de noviembre de 2012 10:27:54 UTC+1, Jens escribió:

Make sure that your app server can still find the
.rpc file. Thats your GWT-RPC serialization policy
file that the server must know in order to serialize
anything that implements Serializable. If it does not find
this file it falls back to the old IsSerializable
mechanism and if you do not have implemented that
interface serialization will fail.

Normally you should see a warning in the app server log on
the first RPC request when GWT's RemoteServiceServlet
tries to load the serialization policy file but can not
find it.

For example I often have to change the lookup of that file
because my deployment does not conform to GWT's standard
assumptions.

-- J.

--
You received this message because you are subscribed to the Google 
Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to google-web-toolkit+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/5c9d5947-af97-4b68-892c-b98f52de3033o%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/d50a6861-a180-1e49-4fe0-e5f9d2e2803e%40newsrx.com.


Fwd: Re: Who are the steering committee members?

2020-06-03 Thread Michael Conrad


Don't know if anyone saw this one.. but it appears the website needs 
updating? And the steering committe mailing list membership updated or 
list removed?


 Forwarded Message 
Subject:Re: Who are the steering committee members?
Date:   Tue, 2 Jun 2020 23:01:48 -0700 (PDT)
From:   'Goktug Gokdogan' via GWT Steering 
Reply-To:   gwt-steer...@googlegroups.com
To: GWT Steering 



Friendly ping.

GWT need a list of active members of Steering committee and functioning 
body; as it is it looks like GWT Steering Committee is silently 
disbanded and no longer making decisions.


On Monday, June 1, 2020 at 12:39:57 PM UTC-7, Julien Dramaix wrote:

   Hi,

   Who are the steering committee members right now ?

   The current list  on the
   website still contains names of people that either communicated
   their intention to leave the committee or are not active for years.

   -Julien

--
You received this message because you are subscribed to the Google 
Groups "GWT Steering" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to gwt-steering+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gwt-steering/0b3edba9-ec3a-4ff5-8045-b98761d33382%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/59372724-5d3d-f0ca-27a6-14c29a705cd0%40newsrx.com.


Re: Is the UI Binder DocType Broken?

2020-04-29 Thread Michael Conrad
I just accessed the URL directly in a browser and was prompted for an 
XML download. Connection issue of some sort?


Reading the header in the XML file it looks like they want you to use 
'https://dl-ssl.google.com/download/gwt/DTD/xhtml.ent' instead.


And the master copy is at 
'http://google-web-toolkit.googlecode.com/svn/trunk/user/src/com/google/gwt/uibinder/resources/xhtml.ent'


And looking through that file, I don't see UI Binder elements defined, 
only HTML entities.


On 4/28/20 12:18 PM, Scott Onyx Harmon wrote:

http://dl.google.com/gwt/DTD/xhtml.ent;>

No longer seems to be functioning properly, as I now get multiple 
"errors" in my XML files such as:

Element type "ui:UiBinder" must be declared.

Is there a new place to get the DTD?
--
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/50b54519-f3fb-438d-82ad-fd9b8cdd07d8%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/3d43a885-abfc-8e57-fcda-f911338d174f%40newsrx.com.


Re: GWT - Angular/React Migration & Integration

2020-04-21 Thread Michael Conrad
Don't know if this will help, but you can set the rootpanel for a GWT 
component using an id, say on a div tag.


On 4/20/20 8:00 PM, Thomas wrote:
Thanks Jens. If I paraphrase in my words, you would keep the "shell" 
(menu items etc) and have iFrames for new functionality?


Sounds like a reasonable approach, although I'd prefer to have the 
"shell" in the new technology and have iFrames for the old GWT modules.


Have you come across any resources/examples that you can share?

Cheers, Thomas

On Friday, April 17, 2020 at 9:11:03 PM UTC+8, Jens wrote:

Kind of in the same situation and I figured that using an iframe
approach is probably the best idea. So you would need to refactor
your app in a way that you can launch an external application in
an iframe for a given menu item, basically the content area in
your app should be an iframe. That way you could develop future
content using a different framework (or even multiple different
frameworks!) and also refactor current/old GWT content to fit into
the iframe solution which shortens the compile time for these new
minimal GWT content applications. Finally you get the freedom to
only update parts of your application instead the whole beast.

However when doing so and your app uses history tokens / pushstate
you need to figure out a good way to update the browser main
location bar from within the iframe.

Personally I would consider using Angular, Vue or Svelte (with
Sapper being the Svelte app framework). While Angular and Vue both
use virtual DOM, Svelte does only look like it would use a virtual
DOM but in reality it compiles down to direct DOM operations which
makes it more performant than a virtual DOM based solution. I
would only use React if there are thoughts about using React
Native as well, but then Flutter from Google might also be
interesting.

-- J.

--
You received this message because you are subscribed to the Google 
Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to google-web-toolkit+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/4a721edc-2b87-47a5-92d4-7541eca85726%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/4156ed96-0396-dc98-88f8-0b09a0c9f9a1%40newsrx.com.


Re: GWT/smartgwt app support with Firefox 74.0

2020-04-02 Thread Michael Conrad
Have you tried setting things up to only generate the chrome permutation 
along with setting the fallback user-agent permutation being set to chrome?


On 4/2/20 2:22 AM, sudarshan rai wrote:
we have web application based on gwt along with some smart-gwt 
components.The app used to be compatible with chrome and firefox. But 
after Firefox 74.0 update some of the functionalities have stopped 
working in firefox. But works fine in chrome.


Smart-gwt components such as calendar are not loading.There is no 
error stack in console apart from warnings.


 ```
11:40:04.582:WARN:Log:Uncaught exception escaped: 
com.google.gwt.core.client.JavaScriptException

(NotSupportedError)
 __gwt$exception: 
 code: 9
 result: 2152923145
 filename: 
https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html

 lineNumber: 13114
 columnNumber: 0
 data: null
 stack: 
ihh@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:13114:43

Dle@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:14538:49
HXd@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:15437:241
UJb@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:16221:290
Er@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:15125:28
$r@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:15556:210
bs@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:16859:1255
Mqj@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:16907:24578
quh@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:14048:142
xuh@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:16907:392
LQj/c.onreadystatechange<@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:10966:65
hdh@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:7982:30
ldh@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:14735:60
kdh/<@https://10.99.7.179/app/1C639C0B473EC335AF7C991184A464ED.cache.html:14216:56

 INDEX_SIZE_ERR: 1
 DOMSTRING_SIZE_ERR: 2
 HIERARCHY_REQUEST_ERR: 3
 WRONG_DOCUMENT_ERR: 4
 INVALID_CHARACTER_ERR: 5
 NO_DATA_ALLOWED_ERR: 6
 NO_MODIFICATION_ALLOWED_ERR: 7
 NOT_FOUND_ERR: 8
 NOT_SUPPORTED_ERR: 9
 INUSE_ATTRIBUTE_ERR: 10
 INVALID_STATE_ERR: 11
 SYNTAX_ERR: 12
 INVALID_MODIFICATION_ERR: 13
 NAMESPACE_ERR: 14
 INVALID_ACCESS_ERR: 15
 VALIDATION_ERR: 16
 TYPE_MISMATCH_ERR: 17
 SECURITY_ERR: 18
 NETWORK_ERR: 19
 ABORT_ERR: 20
 URL_MISMATCH_ERR: 21
 QUOTA_EXCEEDED_ERR: 22
 TIMEOUT_ERR: 23
 INVALID_NODE_TYPE_ERR: 24
 DATA_CLONE_ERR: 25: Operation is not supported
```
Is there no support for gwt/smart-gwt from firefox-74 onwards?

version:

GWT-2.6.1

smartgwt-6.0p-02-11

--
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/4e87fb8b-caf8-44c0-ac40-da4dc011b49d%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/f01331a4-82ae-481e-c9e8-086b8e0f6808%40newsrx.com.


Re: Need help debugging 2.0.3 (IE/Chrome - Eclipse Neon)

2020-01-17 Thread Michael Conrad

Suggestions:

a) request a dev box or context to host your debugging efforts that you 
can deploy to on demand.

=or=
b) setup a special project that can proxy via localhost requests to the 
API that you can deploy on your own machine that you also have setup to 
host the front-end you are working with

=then=
c) Convert entire project to version 2.8.2, make code adjustments to 
match 2.8.2, then you can debug via your dev setup using something like 
the GWT SuperDev debug via Eclipse chrome debug plugin or similar.


On 1/15/20 9:11 AM, Luis Soto Sepulveda wrote:

Hi Everyone:

I'm working on this web application (Intranet JEE / Rest Services 
application) and is using an OLD GWT version (probably 2.0.3 as i can 
see in the code)...


This application works fine running on Internet explorer and chrome, 
but here "development team" told me that i can "not perform direct 
debug in some java classes, mainly java files on Eclipse in front end 
(starting from GWT Entry Point and then...)


But i can debug some parts of back end with eclipse (rest services 
backend layer)...


So i need help with the following:

1) Can i debug GWT 2.0 using IE / chrome and Eclipse IDE (Neon) ???, 
IF YES please send me here any URL with this kind information...


As i can see i can not use "super dev mode" since i have no access to 
source maps in order to debug GWT and point this to JEE class files 
(because this is supported in GWT 2.5 or above)...


SO, how can i debug GWT if i have no access to Source maps ???

(i'm also not administrator user in my machine, so i can not install 
software using windows installers)


Best Regards.
--
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/d9be9ad7-7b2c-415e-a3f6-a4082c9f5583%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/dc10a529-d604-8ded-f6f2-aa71434ceeaa%40newsrx.com.


Re: [ANN] (Unofficial) GWT 2.8.2-v20191108 release

2019-11-12 Thread Michael Conrad

Is there a release notes link?

On 11/10/19 10:19 PM, Peter Donald wrote:

GWT is a development toolkit for building and optimizing complex
browser-based applications. Its goal is to enable productive
development of high-performance web applications without the
developer having to be an expert in browser quirks,
XMLHttpRequest, and JavaScript. It’s open-source, completely
free, and used by thousands of developers around the world.

https://github.com/gwtproject/gwt

This is an unofficial release to Maven Central with the groupId
prefixed with "org.realityforge.". The intent is to get the current
version of GWT into more people's hands earlier. Please don't bug
the GWT project. Versions are released on demand.

The one significant difference in the way that it has been packaged
is to release the jsinterop-annotations artifact with the coordinate

org.realityforge.com.google.jsinterop:jsinterop-annotations:jar:2.8.2-v20191108 



For most Maven users, it should be sufficient to update your
dependency declarations to something like:

    
org.realityforge.com.google.gwt
      gwt-user
      2.8.2-v20191108
    
    
org.realityforge.com.google.gwt
      gwt-dev
      2.8.2-v20191108
    

Hope this helps,

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


--
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/0bb1f4a8-f522-9d46-2267-7bb5db875104%40newsrx.com.