Re: How to debug the java code on the eclipse ide with the tbroyer gwt maven plugin ?

[Juan Pablo Gardella]

Did you check if that solves the problem of variable names?

On Tue, Dec 12, 2023 at 12:50 PM Colin Alworth 
wrote:

> That's great news! Related, I had understood that this didn't work at all,
> but I discovered via
> https://bugs.chromium.org/p/chromium/issues/detail?id=327092 that there
> is an "experimental" feature in chrome that lets locals be displayed.
> [image: screenshot867.png]
> However even with this enabled, only locals/params will show up with their
> correct names - any fields on those, or fields on "this" will still require
> finding their obfuscated names.
>
> On Tuesday, December 12, 2023 at 9:47:40 AM UTC-6 Thomas Broyer wrote:
>
>> On Tuesday, December 12, 2023 at 3:44:34 PM UTC+1 gardella...@gmail.com
>> wrote:
>>
>> Which limitation are you referring to? Is it something that can be fixed
>> or is it impossible to fix variable names there?
>>
>>
>>
>> https://ecma-international.org/news/ecma-tc39-ecmascript-initiates-a-new-task-group-to-standardize-source-maps/
>> > The group’s plan is to identify the gaps, bring completeness and
>> clarity to the current specification; and help source map debuggers,
>> generators and tools to adhere to the updated specification. The intent is
>> to work together on *adding long requested features such as passing
>> through function and variable names*, and debug IDs to quickly identify
>> source files or scope information.
>>
>> (emphasis mine)
>>
> --
> 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/a876be26-063e-4466-a5c5-5f5760293733n%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/CA%2BkiFseJx0yP%3DTLan5Nchq0b-1VXw49Zux75jjQCj%3DrWkSEmXg%40mail.gmail.com.

Re: How to debug the java code on the eclipse ide with the tbroyer gwt maven plugin ?

[Juan Pablo Gardella]

Which limitation are you referring to? Is it something that can be fixed or
is it impossible to fix variable names there?

On Tue, Dec 12, 2023 at 11:39 AM Colin Alworth 
wrote:

> The gwt-eclipse-plugin is maintained, but browsers removed the API that
> was previously used to let a Java debugger connect to a running GWT
> application. This API was used by a browser plugin that was shipped as part
> of GWT. Technically GWT still supports this, but I believe only IE11 (and
> htmlunit) can actually use it, and its use is discouraged, some other GWT
> features will not work with it.
>
> There is a separate plugin, https://sdbg.github.io/ that is also
> maintained, that allows eclipse to debug GWT apps via sourcemaps, much the
> same as the browser's own debugger will do.
>
> The issues you're observing with variable renaming making it difficult to
> inspect values is caused by limitations in JS sourcemaps themselves.
>
> On Tuesday, December 12, 2023 at 12:26:16 AM UTC-6 ralph.f...@gmail.com
> wrote:
>
>> Yes, unfortunately the Eclipse plug-in is no longer maintained. Debugging
>> in the browser is the way to go! It works the same as for other JavaScript
>> frameworks (e.g. Angular) using a standard feature to map generated
>> JavaScript onto the source code (be it Java or Typescript etc.). That is,
>> you can set breakpoints and inspect the runtime values of your variables.
>> There is just one issue with variable names which differ between Java and
>> JavaScript but this is mostly cosmetic.
>>
>> Marco Tenti (IoProgrammo88)  schrieb am Mo. 11. Dez.
>> 2023 um 13:31:
>>
>>> So this debug mode is deprecated
>>> https://www.gwtproject.org/doc/latest/tutorial/debug.html  ?
>>>
>>> When I launch the "gwt:codeServer" command, i  go to the sources panel
>>> of the browser chrome, and I can browse the code and set the breakpoints ,
>>> but I can not "see" the runtime values of the variables as it happens with
>>> standard javascript is this correct ?
>>>
>>>  [image: ErrorPskCallStack.png]
>>>
>>> Il giorno lunedì 4 dicembre 2023 alle 13:30:37 UTC+1 Ralph Fiergolla ha
>>> scritto:
>>>
 If I am not mistaken, you are mixing up things a little: the issue you
 were looking at here
 https://github.com/tbroyer/gwt-maven-plugin/issues/82 is not about
 debugging the generated client part of your application, but about the
 compiler that is actually generating the code you want to debug.

 To avoid wasting your time trying to set up the Eclipse Plugin I would
 suggest using your browser's built-in development tools (Ctrl+Shift+I). You
 will see your JAVA source code and can put your breakpoints etc. and step
 through your code. This works in Chrome, Firefox, Edge.

 Bon courage
 Ralph

 On Mon, Dec 4, 2023 at 1:16 PM Marco Tenti (IoProgrammo88) <
 tenti...@gmail.com> wrote:

> Hello everyone, I am updating some old gwt projects and I started to
> study about 15 days ago the gwt framework, this is to specify that I don't
> know all the secrets of the framework yet.
>
> Following Nalu's approach and starting from his example at
> https://github.com/NaluKit/nalu-examples/tree/main/nalu-simple-app-example,
> I was able to start with the gwt:codeserver both client and server part of
> my projects successfully.
>
> Unfortunately, I still haven't figured out what I need to do to
> enablethe  debugging on the client part of the project on the IDE eclipse.
>
> I've read in this issue
> https://github.com/tbroyer/gwt-maven-plugin/issues/82 a possible
> solution, but it doesn't seem to work, I'm 100% sure I'm doing something
> wrong myself., can anyone tell me looking at Nalu's example what 
> additional
> commands I need to set to configure to debugging on the client java code 
> in
> the eclipse 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-tool...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/3369c8a1-d86f-40de-9816-d35d865a1e4en%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-tool...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit/ed37a5ea-c5fa-4a74-9c37-3839311f410en%40googlegroups.com
>>> 

Re: [gwt-contrib] Re: Preparing for GWT 2.11 release

[Juan Pablo Gardella]

Thanks I will check using a snapshot then.

On Thu, Nov 23, 2023 at 1:03 PM Colin Alworth  wrote:

> We're still in the "please help us review the last few merges" phase
> (especially looking for notes on deprecating using DevMode as an app
> server, and comments on if tests added for other PRs seem sufficient), then
> we'll make some release artifacts (late next week is my guess). I'm hoping
> to merge most of the open PRs, so we want to not start testing until we've
> landed that changes that will make this release.
>
> That being said, we ship HEAD-SNAPSHOT every night off of main, you can
> add https://oss.sonatype.org/content/repositories/snapshots/ as a
> snapshot repository to your project to use that build (be certain you are
> using org.gwtproject groupids). If you need nightly download zips, they are
> available at
> https://github.com/gwtproject/gwt/actions/workflows/full-check.yml, click
> any build, scroll down artifacts, and download gwt-java17.zip. While this
> was built with Java 17, it is compatible with Java 8+ and will be used for
> the release. The other builds should be nearly identical - the main change
> should be in the javadoc output. The build produced from Java8 is
> substantially smaller since it doesn't include javadoc at all, since the
> APIs we now use are not compatible there.
>
> On Thursday, November 23, 2023 at 7:36:55 AM UTC-6 Juan Pablo Gardella
> wrote:
>
>> Hello, is gwt-2.11 artifacts available somewhere for testing against the
>> applications I am currently working on?
>>
>> On Tue, Nov 14, 2023, 11:37 PM Colin Alworth  wrote:
>>
>>> It has taken longer than we had hoped, but I think we're just about
>>> ready - GWT itself can build on Java 17 (and can run on Java 23), JRE
>>> emulation is nearly caught up to where we wanted with Java 11, and
>>> jakarta.servlet support is hopefully finished and partially tested in
>>> non-trivial apps.
>>>
>>> Here's my view of what might land before we cut a release:
>>>
>>>- The jakarta.servlet patch is now at
>>>https://github.com/gwtproject/gwt/pull/9845, and is effectively
>>>ready to land. To my knowledge, no jakarta project has tested the
>>>requestfactory-*.jars yet.
>>>- As above, we need confirmation that
>>>https://github.com/gwtproject/gwt/pull/9785 solves the problem it
>>>was created for.
>>>- As above https://github.com/gwtproject/gwt/pull/9799 (fixing some
>>>ternary expressions and other type unions) should get at least one more
>>>review, approval. This will be applicable for Java 17 language support.
>>>- Two more JRE emulation patches:
>>>https://github.com/gwtproject/gwt/pull/9860 needs a review, and
>>>https://github.com/gwtproject/gwt/pull/9862 needs follow-up and
>>>another review.
>>>
>>> If this is the last release that can run the compiler and dev mode on
>>> Java 8, we will want to update Jetty in the next release as well. That
>>> might suggest one more change, deprecating the use of "-server" in DevMode.
>>> Please see https://github.com/gwtproject/gwt/issues/9863 for more
>>> details. In the coming days I'll put together a patch for this.
>>>
>>> After we've merged or deferred these PRs, the next step will be asking
>>> for testing volunteers and cutting an RC release. I'm hoping we can begin
>>> that process within two weeks - if you're interested in helping us test
>>> this release, please reply to this message or directly with the
>>> OS/JVM/Browsers you have at your disposal, and I'll make sure you are
>>> included. As usual, the testing process will probably take a week or so to
>>> get the desired coverage, and then we'll formally release GWT 2.11.0.
>>>
>>> On Tuesday, May 23, 2023 at 3:11:51 PM UTC-5 Rocco De Angelis wrote:
>>>
>>>> Hi Colin,
>>>>
>>>> if you need some help, I'm feeling to help.
>>>> Specially the jakarta stuff is important for us.
>>>> Do you find the time to have a look to the open PR?
>>>>
>>>> BR
>>>> Rocco
>>>>
>>>> Colin Alworth schrieb am Mittwoch, 17. Mai 2023 um 16:44:58 UTC+2:
>>>>
>>>>> There have been a few suggestions of making a release in the near
>>>>> future, and it seemed like it might be a good idea to summarize pending
>>>>> development, ask for help to land these, and see if anything else needs to
>>>>> be addressed before shipping.
>>&g

Re: [gwt-contrib] Re: Preparing for GWT 2.11 release

[Juan Pablo Gardella]

Hello, is gwt-2.11 artifacts available somewhere for testing against the
applications I am currently working on?

On Tue, Nov 14, 2023, 11:37 PM Colin Alworth  wrote:

> It has taken longer than we had hoped, but I think we're just about ready
> - GWT itself can build on Java 17 (and can run on Java 23), JRE emulation
> is nearly caught up to where we wanted with Java 11, and jakarta.servlet
> support is hopefully finished and partially tested in non-trivial apps.
>
> Here's my view of what might land before we cut a release:
>
>- The jakarta.servlet patch is now at
>https://github.com/gwtproject/gwt/pull/9845, and is effectively ready
>to land. To my knowledge, no jakarta project has tested the
>requestfactory-*.jars yet.
>- As above, we need confirmation that
>https://github.com/gwtproject/gwt/pull/9785 solves the problem it was
>created for.
>- As above https://github.com/gwtproject/gwt/pull/9799 (fixing some
>ternary expressions and other type unions) should get at least one more
>review, approval. This will be applicable for Java 17 language support.
>- Two more JRE emulation patches:
>https://github.com/gwtproject/gwt/pull/9860 needs a review, and
>https://github.com/gwtproject/gwt/pull/9862 needs follow-up and
>another review.
>
> If this is the last release that can run the compiler and dev mode on Java
> 8, we will want to update Jetty in the next release as well. That might
> suggest one more change, deprecating the use of "-server" in DevMode.
> Please see https://github.com/gwtproject/gwt/issues/9863 for more
> details. In the coming days I'll put together a patch for this.
>
> After we've merged or deferred these PRs, the next step will be asking for
> testing volunteers and cutting an RC release. I'm hoping we can begin that
> process within two weeks - if you're interested in helping us test this
> release, please reply to this message or directly with the OS/JVM/Browsers
> you have at your disposal, and I'll make sure you are included. As usual,
> the testing process will probably take a week or so to get the desired
> coverage, and then we'll formally release GWT 2.11.0.
>
> On Tuesday, May 23, 2023 at 3:11:51 PM UTC-5 Rocco De Angelis wrote:
>
>> Hi Colin,
>>
>> if you need some help, I'm feeling to help.
>> Specially the jakarta stuff is important for us.
>> Do you find the time to have a look to the open PR?
>>
>> BR
>> Rocco
>>
>> Colin Alworth schrieb am Mittwoch, 17. Mai 2023 um 16:44:58 UTC+2:
>>
>>> There have been a few suggestions of making a release in the near
>>> future, and it seemed like it might be a good idea to summarize pending
>>> development, ask for help to land these, and see if anything else needs to
>>> be addressed before shipping.
>>>
>>>
>>>- There is a pending branch (not yet a PR for GWT itself) working on
>>>adding a new gwt-servlet-jakarta.jar and 
>>> requestfactory-server-jakarta.jar
>>>as part of https://github.com/gwtproject/gwt/issues/9727. There is
>>>no plan at this time to update the DevMode server to Jakarta, though that
>>>will eventually be inevitable if we move to a newer version of Jetty. 
>>> Work
>>>on this can be found at https://github.com/niloc132/gwt/pull/3.
>>>- There is a pending fix for eliminating a false positive from using
>>>some internals of protobuf to deobfuscate client side exceptions
>>>https://github.com/gwtproject/gwt/pull/9785. This is probably safe
>>>to land without more testing, but none of the reporters of this bug have
>>>verified the fix.
>>>- There's a pending fix for a bug in type unions, which can be
>>>caused by some ternary expressions and var type declarations
>>>https://github.com/gwtproject/gwt/pull/9799. A review found a few
>>>oversights in testing, and I'd appreciate another look.
>>>- There's a pending fix for a bug where debugging in firefox when
>>>assertions are enabled (for example in SDM). It turns out the bug can
>>>happen in other cases too in more subtle ways. A draft fix it at
>>>https://github.com/gwtproject/gwt/pull/9800.
>>>- GWT itself can now be built on Java 11, but not yet 17. There are
>>>a few changes pending that will permit this. Additionally, this will 
>>> enable
>>>adding more Java 9-11 JRE emulation, see the list at
>>>https://github.com/gwtproject/gwt/issues/9547.
>>>
>>>
>>> Finally, we have an open question about future Java 8 support. Beyond
>>> this release, we likely will no longer support running the compiler in Java
>>> 8, which will enable adding support for Java 12-17 language features. We
>>> can likely still build jars that will run on a Java 8 server, but just
>>> can't compile newer JS. To that end, this 2.11 release branch may be
>>> longer-lived than usual, depending on feedback and support to continue
>>> bugfix releases after 2.12 eventually ships.
>>>
>>> Are there other changes that 2.11 should included, or other
>>> 

Re: DominoKit release 1.0.0

[Juan Pablo Gardella]

Thanks!!! That is amazing!

On Wed, Jul 19, 2023 at 2:21 PM Vegegoku  wrote:

> We are thrilled to announce the first major release of DominoKit toolset :
>
>
>- domino-jackson  : 1.0.0
> Generate
>JSON mappers that works for both client and server side, works with both
>GWT/J2CL.
>- domino-history  : 1.0.0
> A
>wrapper around browser history state API that allow you to work smoothly
>with browser URL for routing, works with both GWT/J2CL.
>- domino-rest  : 1.0.0
> Generate
>REST API clients from jax-rs interfaces and use them to make REST calls
>from browser to server or JVM to server, works with both GWT/J2CL.
>- domino-ui  : 1.0.0
> Build rich
>web user interfaces using java and use a large set of feature rich
>components to make building apps easier. demo here
>, works with both GWT/J2CL.
>- domino-mvp  : 1.0.0
> All in
>one framework that combines DominoKit toolset to control your app pages
>life-cycle and routing, works with both GWT/J2CL.
>- domino-cli  : 1.0.0
> CLI tool
>to create new GWT/J2CL projects that uses DominoKit tools.
>
>
> With this milestone we are already set to start a new development cycle to
> bring more tools and features to DominoKit tools set.
>
> I also would like to thank everyone who supported us through the years to
> get to this point. and special thanks to Vertispan
>  for sponsoring a large portion of the work.
>
> --
> 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/7b022b17-efe5-4a9a-87af-32c26a41914en%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/CA%2BkiFsczVGt52tnNvSGi%3DbhwqOnjB3wB0o%2BC0oAQDB2kpSA_vg%40mail.gmail.com.

Re: JavaFX for GWT

[Juan Pablo Gardella]

Impressive!

On Tue, Nov 8, 2022 at 11:38 AM Bruno Salmon  wrote:

> Hi,
>
> I'm working on a JavaFX transpiler powered by GWT.
> It lets you use JavaFX as a UI toolkit in your GWT apps.
> The JavaFX API is far from completely covered, but you can already see
> some interesting results.
>
> The project is on GitHub for those who are interested.
> https://github.com/webfx-project/webfx
>
> If you have any questions, please let me know.
>
> --
> 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/8210a6a2-ad1a-4b2d-ba68-19dcc5fbeef3n%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/CA%2BkiFse5BWFG3R0g7iY1NKmyZNMhHhzge5DaUsPLCJbeZEz6KQ%40mail.gmail.com.

Re: [gwt-contrib] Re: Testing for GWT 2.10.0 release

[Juan Pablo Gardella]

Thanks Colin!

On Wed, Jun 22, 2022 at 5:11 PM Colin Alworth  wrote:

> The last step of the release process is under way, Google's 2.10.0 release
> is underway, we're just waiting for the release to be performed and
> synchronized to Maven Central. When that has finished we can formally
> announce the release.
>
> I've created an issue for next steps to finish our transition to GitHub at
> https://github.com/gwtproject/gwt/issues/9756 and will follow up with a
> few proposed pull requests to make these changes.
>
> Thanks for everyone's support and patience with this process!
>
> On Sunday, May 22, 2022 at 11:00:14 AM UTC-5 mcmi...@gmail.com wrote:
>
>> Hi,
>> I could test on Windows 10 (and maybe Windows 11)
>> Browser :
>> - Firefox
>> - Edge (but Chromium only)
>> - IE 11 (End of Support on June 15th)
>> - Chrome
>>
>> JVM:
>> - 11
>> - 17
>> - 18
>> - 19 eap
>> Boris Brudnoy schrieb am Freitag, 20. Mai 2022 um 14:33:02 UTC+2:
>>
>>> I'll test. I'm on macOS Monterey 12.3.1. Can do whichever JVMs /
>>> browsers run on macOS, which AFAICT is everything but IE11.
>>>
>>> On Thursday, May 19, 2022 at 11:34:31 PM UTC-4 nilo...@gmail.com wrote:
>>>
 Hello all,

 All of the preliminary testing that I'm aware of for the upcoming
 release is complete, leaving us with a decent level of confidence in the
 changes. We have a document that outlines the release plan (with a link to
 the standard release steps and the testing process) that has undergone a
 few small tweaks, and I think is ready to go:

 https://docs.google.com/document/d/10Cn0Z7SDv0ZW5OVZdoIdw5EAEDUbtK6vracOOnxj7po/edit

 I'm now asking for volunteers who are able to test the final release
 once it is ready to go. We're hoping for a cross section of testing that
 verifies

- JVM Version: 8, 11, 17/18
- OS: Linux, OS X, Windows 8.1, 10, 11
- Browser: Chrome, Firefox, Safari, IE11, Edge (blink)

 Windows 8.1 and 10 VMs are available at
 https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/, I'm
 not presently aware of a source for Windows 11 VMs, so ideally we have a
 few people running that natively.

 Please reply to this or contact me off-list (co...@colinalworth.com)
 with the combinations you have access to and are able to test, and we'll
 organize in the next few days, and start the next steps.

 Thanks!

>>> --
> 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/5df0ff8b-6d48-4c44-a814-3e27cb98427dn%40googlegroups.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/CA%2BkiFseDOCx7tbdqQb2LUu0RYu3b6k-HstCUAOXvewxTv5L6KA%40mail.gmail.com.

Re: [gwt-contrib] Preliminary testing for GWT 2.10 release

[Juan Pablo Gardella]

After removing an old plexus-utils as suggested at #152
, I was able to
compile and run the application without issues so far. Great work!

On Mon, Apr 25, 2022 at 2:25 PM Freddy Boucher 
wrote:

> 2.10.0-new-groupid-3 works like a charm (in addition of
> net.ltgt.gwt.maven/gwt-maven-plugin 1.0.1)
> Thanks
>
> Le dimanche 24 avril 2022 à 21:34:23 UTC+2, juan_pablo_gardella a écrit :
>
>> Tried with Maven 3.8.5 and still fails with same issue. Reported at
>> https://github.com/tbroyer/gwt-maven-plugin/issues/152
>>
>> On Sun, Apr 24, 2022 at 3:59 PM Colin Alworth  wrote:
>>
>>> I've pushed a new build with version 2.10.0-new-groupid-3 that has
>>> several @SuppressWarnings("deprecation")s added, and hopefully will solve
>>> the WARN logging 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/28cff012-2206-48a8-8882-11b0ea945046n%40googlegroups.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/051780f4-fa98-45c2-ad36-1ebb40a38f7an%40googlegroups.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/CA%2BkiFsengmip-YpVegW-6CP1TOeVQTnnS5OU-D%2B26c4ru1G2gQ%40mail.gmail.com.

Re: [gwt-contrib] Preliminary testing for GWT 2.10 release

[Juan Pablo Gardella]

Tried with Maven 3.8.5 and still fails with same issue. Reported at
https://github.com/tbroyer/gwt-maven-plugin/issues/152

On Sun, Apr 24, 2022 at 3:59 PM Colin Alworth  wrote:

> I've pushed a new build with version 2.10.0-new-groupid-3 that has several
> @SuppressWarnings("deprecation")s added, and hopefully will solve the WARN
> logging 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/28cff012-2206-48a8-8882-11b0ea945046n%40googlegroups.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/CA%2BkiFsdpiEDJOdjMYg52WnmDi-zt%3DPipSk9LXb_T-Ben9A5QYQ%40mail.gmail.com.

Re: [gwt-contrib] Preliminary testing for GWT 2.10 release

[Juan Pablo Gardella]

I tested and I updated from net.ltgt.gwt.maven:gwt-maven-plugin:1.0.0 to
net.ltgt.gwt.maven:gwt-maven-plugin:1.0.1 in order to see the proper error (*
Value 'ie10' in not a valid value for property 'user.agent'*) instead of
[1]. After that I see following error:

[ERROR] Failed to execute goal
net.ltgt.gwt.maven:gwt-maven-plugin:1.0.1:package-app (default-package-app)
on project xxx-client: Execution default-package-app of goal
net.ltgt.gwt.maven:gwt-maven-plugin:1.0.1:package-app failed: An API
incompatibility was encountered while executing
net.ltgt.gwt.maven:gwt-maven-plugin:1.0.1:package-app:
java.lang.NoSuchMethodError:
org.codehaus.plexus.util.DirectoryScanner.setFilenameComparator(Ljava/util/Comparator;)V

Using either java8 or java11 as default java but java8 with toolchains
 for the
project. Reverted to net.ltgt.gwt.maven:gwt-maven-plugin:1.0.0 I still see
NPE[1]. No luck from my side to switch. Any ideas? I am using Apache Maven
3.6.3.

Juan

[1]
Caused by: java.lang.NullPointerException
at
net.ltgt.gwt.maven.GenerateModuleMojo.generateInheritsFromDependencies
(GenerateModuleMojo.java:251)
at net.ltgt.gwt.maven.GenerateModuleMojo.execute
(GenerateModuleMojo.java:180)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)

On Fri, Apr 22, 2022 at 3:35 PM Colin Alworth  wrote:

> I could revert the deprecations (though they were specifically added at
> your request ;) ).
>
> That said, those changed when the old IE versions were removed, and I
> didn't see the showcase start to emit those errors then. Even with the JDT
> upgrade, I still don't see them for the showcase:
>
> https://github.com/niloc132/gwt/runs/6124099314?check_suite_focus=true#step:5:3295
>
> The error also does not appear to happen when running from ant, at least
> not in the showcase sample.
>
> At a glance I can't see anything explicitly disabling deprecation warnings
> in that code. The warning is coming from JsniReferenceResolver. The linked
> log above is emitting warnings, but clearly not one for the code you see,
> even though the showcase references those types. Showcase's CwRichText
> explicitly uses the RichText widget.
>
> However, both maven and gradle projects do correctly include the warnings,
> if you happen to include those gwt modules in your project. That does make
> the iteration time a bit longer to test, but it appears we can suppress the
> warnings on a per-usage basis. I'll propose a patch (and upload a new build
> to test) as soon as I'm able.
>
>
> On Friday, April 22, 2022 at 9:12:58 AM UTC-5 Thomas Broyer wrote:
>
>> I tried changing only the version (from com.google.gwt:gwt:2.8.2 to
>> com.google.gwt:2.10.0-new-groupid-2).
>> Looking at a dependency graph (./gradlew dependencies), I can see the
>> com.google.gwt dependencies properly "relocated" to their org.gwtproject
>> equivalent 
>> Java compilation passes without warning or error, same for JVM tests (I
>> don't have much that use GWT though), and even GWT tests!  (I only have a
>> couple of them though)
>> GWT compilation emits a few unexpected warnings though:
>>[WARN] Warnings in

Re: [gwt-contrib] gwtproject.org migration, https support

[Juan Pablo Gardella]

Thanks Colin! Great work

On Mon, Mar 28, 2022 at 12:37 PM Colin Alworth  wrote:

> We've successfully migrated the gwtproject.org website to a new domain
> name server and new hosting, at Google's request. There are a few small
> differences from the old hosting:
>
>
>- HTTPS is now supported and enabled, though not yet mandatory, to
>allow a period of migration, and making sure that no downstream tools will
>break as a result of these changes. HSTS is also disabled for now. I
>propose that mid-week I will update this to always redirect to HTTPS, and
>then in another two or three weeks consider enabling HSTS if there have
>been no reported issues.
>- The samples.gwtproject.org domain now redirects to the showcase,
>rather than giving a confusing 500 error. The samples are still at this
>time hosted as static content rather than servlets.
>- The GWT application that enhances the documentation has been
>updated, picking up changes published ~2 years ago.
>- Deep links that omit "www." (for example
>gwtproject.org/doc/latest/DevGuide.html) will now redirect to the
>expected page (in this case www.gwtproject.org/doc/latest/DevGuide.html)
>rather than redirecting only to www.gwtproject.org.
>
>
> Building and deployment of the new site is currently described at
> https://github.com/Vertispan/gwtproject.org, and should be hostable with
> or without DNS entries or HTTPS (though handling your own dns for "
> gwtproject.org" itself may eventually conflict with HSTS). The README
> contains some basic details on how the hosting is structured and how to run
> on any arbitrary server. There is also a TODO list at
> https://github.com/Vertispan/gwtproject.org/blob/main/TODO.md, which
> could eventually be migrated to actual github issues.
>
> This could have been implemented through a similar build process that then
> pushed to github-pages, but at least for now we decided against this. Once
> some kind of continuous integration is in place to create pre-built
> artifacts for gwt-site-webapp and gwt-site itself, it might make sense to
> reconsider this, but for samples it still may make sense to use custom
> hosting to phase out the current static-only samples and provide some
> samples which can interact in some way with the server.
>
> If there are no objections to the current layout, configuration,
> deployment, and documentation, I propose migrating this project to
> github.com/gwtproject, as well as following up on the bullet points of
> the TODO list.
>
> --
> 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/94a1c877-78ac-40ea-9084-405514b8b3d4n%40googlegroups.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/CA%2BkiFsf5SR%2BvhiEPWUJK8vWiwPfSPfuOUxAXnTzX0MBqp0eWXQ%40mail.gmail.com.

Re: Micro-Frontends Session with GWT example

[Juan Pablo Gardella]

Thanks for sharing!

On Tue, Mar 22, 2022 at 11:23 AM lofid...@gmail.com 
wrote:

> Here are the slides... enjoy 
>
> https://bit.ly/MicrofrontendsNavigate2022
>
> lofid...@gmail.com schrieb am Samstag, 19. März 2022 um 11:40:33 UTC+1:
>
>> Hi All,
>>
>> Friendly reminder: next week I have a session for Micro-Frontends. Free,
>> online, language German but the slides are in English  I'll show a short
>> demo in GWT: https://navigate-kongress.de/class/web-micro-frontends/
>>
>> Here is the example: https://github.com/gwtboot/microfrontends-example
>>
>> Enjoy, Lofi
>>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/46423608-f45e-4e65-ba20-4e1c9e4421dbn%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/CA%2BkiFsdQKucmKUeqQDNE_3sFSAt%2BTv25z3g7xau%2BvrOq4GxAKA%40mail.gmail.com.

Re: [gwt-contrib] Re: GWT 2.10 release?

[Juan Pablo Gardella]

@co...@colinalworth.com   do yo know any ETA on
this?

On Tue, Oct 12, 2021, 5:28 AM Rocco De Angelis 
wrote:

>
> Nice +1
> chani...@gmail.com schrieb am Dienstag, 5. Oktober 2021 um 16:38:08 UTC+2:
>
>> Thank a millon, looks great ! +1
>>
>> On Friday, October 1, 2021 at 2:55:21 p.m. UTC-4 krypto...@gmail.com
>> wrote:
>>
>>> awesome +1
>>>
>>> On Fri, Oct 1, 2021 at 2:31 PM mcmi...@gmail.com 
>>> wrote:
>>>
 Sound greats +1


 nilo...@gmail.com schrieb am Donnerstag, 30. September 2021 um
 21:22:13 UTC+2:

> We've got a few changes that have been brewing or waiting to be made
> available, and it sounds like it is about time to collectively push to 
> make
> these things happen. Given the nature of some of these, I am suggesting
> that they not be folded into a bugfix release, but instead that the next
> release be 2.10.0.
>
>
> Changing Maven Central groupId
> One of the big ones is work to migrate off of the "com.google.gwt"
> groupId (note that we are not adjusting packages) and into our own
> namespace in maven, "org.gwtproject.gwt". Google's efforts to open 
> sourcing
> and encourage GWT has been very accommodating for the community, and this
> change is long past due, so that releases of GWT do not need someone with
> access to the com.google groupId in Maven Central to perform the release
> process for us. If successful, this will be the final release which uses
> the old groupId.
>
> To that end, Thomas Broyer has done a lot of work to make sure this
> path will be as smooth as possible. That work can be seen discussed
> in the mailing list
> 
> and in a github repo he wrote
>  to demonstrate
> approaches and their relative merits. No final summary was officially
> posted, but from discussions in gitter chat
> , the
> cleanest proposed option is to follow Experiment #3 for today, and
> optionally later to roll out the last two options to more easily 
> facilitate
> updates from older releases.
>
> This means that the next release will be performed first on
> org.gwtproject, and then later we will request that someone at Google
> perform the final com.google.gwt release, consisting only of pom files 
> that
> indicate relocation to the new groupId. Applications and dependencies will
> need to switch to this new groupId over time, but in theory at least, 
> using
> the researched relocation mechanism should make that fairly painless.
>
> Finally, I suggest that any release candidate that goes out only exist
> on org.gwtproject, to avoid needing to iterate with com.google releases, 
> in
> case we end up needing more than one RC in the release process.
>
> --
>
> Chrome debugging bugs
> There are a few changes in Chrome made over the last year or so that
> impact GWT development and debugging in various ways.
> https://gwt-review.googlesource.com/c/gwt/+/23500 fixes SDM (and
> cross origin apps) stack traces being lost, and unhandledrejection events
> are entirely lost in some cases.
> https://gwt-review.googlesource.com/c/gwt/+/23580 tracks a newer
> change in Chrome dev tools, where the unofficial Function.displayName
> property no longer works when debugging obfuscated code with GWT's
> -XmethodNameDisplayMode flag, and transitions to the standard 
> Function.name
> property instead.
>
>
> --
>
> IE8/IE9/IE10 removal
> Another thread on this mailing list
> 
> tracks the ongoing discussion of removing three end-of-life'd browsers 
> from
> GWT. It has been suggested that IE11 support remain for at least a little
> while longer. According to
> https://docs.microsoft.com/en-us/lifecycle/faq/internet-explorer-microsoft-edge,
> IE11 as a desktop application will no longer be supported after June 2022,
> though that may change, and even if it does not, it may make sense to
> continue support for some time after that.
>
> --
>
> Dropping Java 7 support, and upgrading Jetty 9 and HtmlUnit
> Building GWT itself with something newer than Java 8 is going to
> require additional work (see
> https://github.com/gwtproject/gwt/issues/9683), but the time has come
> to no longer support Java 7, and require 8 as the minimum version for
> building and using GWT. I have a work in progress patch
> 
> which upgrades both Jetty 9 and HtmlUnit to their latest respective
> versions in order to deal with several 

Re: [gwt-contrib] Re: Goodbye IE 8–9 

[Juan Pablo Gardella]

+1 drop IE 11 increases the effort to include new stuff. IE +11 can still
use GWT 2.9.0

On Thu, 30 Sept 2021 at 16:55, Vegegoku  wrote:

> I vote to even drop support for IE11.
>
> On Thursday, September 30, 2021 at 7:49:56 PM UTC+3 nilo...@gmail.com
> wrote:
>
>> I've just filed https://github.com/gwtproject/gwt/issues/9739, where a
>> workaround exists in java.util.Date that nearly doubles the time it takes
>> to parse date strings and build date objects. This workaround exists for
>> IE8 and IE9, as all more recent browsers implement the same behavior as we
>> already would expect. Dropping support for those two browsers would
>> simplify the code required here
>>
>> From the age of this thread and the discussion so far, it sounds like
>> there is interest in keeping IE11 still, but no one has spoke up about IE10
>> or below.
>>
>> Additionally, java.util.Random emulation was changed to require
>> Date.now(), which isn't available in IE8, so neither GWT 2.8.2 nor GWT
>> 2.9.0 are apparently compatible with IE8 anyway, at least in this small
>> way. This should give us some confidence (along with the lack of opposition
>> in this thread) that at least IE8 is definitely safe to drop.
>>
>> So, is there any objection at this time to dropping what remains of IE8,
>> IE9, and IE10 support from GWT? Then, we can reevaluate IE11 at some later
>> date, for GWT itself? Various migrated GWT modules have focused their
>> efforts on well-supported browsers, and are likely to only support IE11 by
>> accident anyway.
>>
>> On Friday, March 12, 2021 at 1:20:02 AM UTC-6 stuckagain wrote:
>>
>>> We still need IE11 support in the banking sector. We still have a
>>> majority of customers that use IE11 due to technical reasons (plugins
>>> needed for accessing secure token don’t install properly in Chrome without
>>> internet access amongst others).
>>>
>>> What do you mean with “next version of GWT” if that is 3.x then I don’t
>>> care at this point. We have been waiting for that release for a few years
>>> now. But 2.x releases should not drop IE11 support it is supposed to be a
>>> long-term supported version.
>>> On 12 Mar 2021, 07:54 +0100, bernhar...@schubec.com <
>>> bernhar...@schubec.com>, wrote:
>>>
>>> Hi all!
>>>
>>> I think IE11 support should be dropped soon if it blocks (or makes it
>>> difficult) to implement new features in the next version of GWT.
>>> I understand, that there are enterprises who still use IE11 internally,
>>> but developers who service such enterprises should use the current version
>>> of GWT, which is not going away. Nobody is forced to upgrade to the next
>>> version of GWT.
>>>
>>> Thanks,
>>> Berni
>>>
>>> tony.be...@gmail.com schrieb am Donnerstag, 11. März 2021 um 22:26:21
>>> UTC+1:
>>>
 IE 11 is still widely used inside corporations, because it is the only
 browser that supports Java applets, and applications such as Oracle
 e-Business Suite still use applets extensively (for Oracle forms). While
 that segment does not move very fast, it does not mean other unrelated
 groups within the same corporation are not updating GWT regularly. It is
 hard to generalize In a multinational company  with tens of thousands of
 employees.

 Regards

 Tony

 On Thu, Mar 11, 2021 at 9:49 AM Jens  wrote:

> Dropping IE 8-10 shouldn't really hurt. Companies that require it are
> probably not upgrading GWT in a fast pace anyways.
>
> However I wouldn't drop IE 11 anytime soon. IE 11 itself is tied to
> the lifecycle of Microsoft's operating systems, which means for Windows 10
> it is supported until 2025 (for now). So just because MS and Google drop
> support for IE 11 in some/all of their products, the browser itself is
> still generally supported by MS. So we should think twice before removing
> IE 11 from a library such as GWT, even if it means to decline/revert
> certain commits if they break IE 11. From own experience I have usually
> seen something around 8% of IE 11 usage in GWT based apps.
>
> However I am pretty sure more and more companies will announce
> dropping IE 11 this year or next year. With MS and Google starting, this
> could easily have a domino effect. However GWT also also strongly used
> internally inside companies so it might not have that much of an effect in
> that area.
>
> If we ditch IE 8-10 and only leaving gecko1_8 and safari, can't we
> kill them both as well and put them together? Are there so many 
> differences
> in code between both? From my work migrating GWT code to
> elemental2/JsInterop I had the feeling that only some minor stuff is
> different between both. So there shouldn't be that much overhead in code
> size and performance doing (cached) runtime checks instead.
>
> -- J.
>
> --
> You received this message because you are subscribed to the Google
> Groups "GWT Contributors" 

Re: Frequent Java runtime crashes when compiling GWT code

[Juan Pablo Gardella]

I had issues and solved after switching to old java 8 oracle version v1xx

On Thu, Aug 5, 2021, 1:14 PM Michael Conrad  wrote:

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

-- 
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: [ANN] Akasha: Typed Browser API

[Juan Pablo Gardella]

That's awesome!! Thanks a lot Peter!

On Wed, May 26, 2021, 8:11 PM Peter Donald  wrote:

> What is Akasha?
>
> Akasha is a typed browser API layer that is always up to date with the
> latest web specifications. These API layers are intended to simplify
> writing web applications in languages other than pure-Javascript. Akasha
> currently provides:
>
>- Closure-compiler  externs
>so that the closure-compiler can perform type checking and advanced
>type-based optimizations.
>- Jsinterop annotated java classes that can be used in GWT
> projects.
>- Jsinterop annotated java classes that can be used in J2CL
> projects.
>
> In the near future, it is expected that bindings for other languages and
> frameworks will be produced (particularly to support WASM based toolkits).
> Support will also be re-enabled to generate React4j
>  element factories.
> Getting
> Started
>
> Getting started using the JsInterop annotated classes is relatively easy.
> The following sections give a basic overview of how to get started in a GWT
> or J2CL project.
> GWT
>
> First you add a dependency on the gwt library to your project. In a
> Maven-based project is as simple as adding the following dependency:
>
> 
>   org.realityforge.akasha
>   akasha-gwt
>   0.11
> 
>
> In a GWT project it is necessary to add a reference to the Akasha library
> the GWT module in your .gwt.xml file. This is just a single inherit:
>
> 
>   ...
>   
>   ...
> 
>
>
> J2CL/Closure
> Compiler
>
> First you add a dependency on the j2cl library to your project. In a
> Maven-based project is as simple as adding the following dependency:
>
> 
>   org.realityforge.akasha
>   akasha-j2cl
>   0.11
> 
>
> The closure compiler is shipped with a set of externs that do not align
> 100% with the externs produced by the Akasha project. Thus it is necessary
> to pass the arguments -env CUSTOM when running the closure compiler. It
> is also necessary to add the closure externs shipped as part of the
> akasha-java artifact. These are included in the artifact under the names;
> akasha/Akasha.externs.js and akasha/akasha_patches.extern.js. The exact
> way that these build steps are specified will depend upon the underlying
> tool but a simple example using Bazel is available at
> https://github.com/react4j/react4j-todomvc/tree/raw_bazel_j2cl
> Java
> Integration
>
> The easiest way to access browser APIs is to access the static fields or
> call static methods on the classes that represent the globalThis object
> within the javascript environment. The "namespaces" within the browser are
> also exposed as java classes containing static methods and static fields.
>
> For example the javascript:
>
> window.addEventListener( "online", e => console.log( "The network is 
> connected" ) )
>
> Would be translated into Akasha java as:
>
> WindowGlobal.addOnlineListener( e -> Console.log( "The network is connected" 
> ) );
>
> In this scenario, the WindowGlobal java class represents globalThis value
> in a browser window context and the Console class represents the console 
> namespace.
> Some browser types can also be created using the new keyword and where
> this is possible in javascript it is possible in Akasha java. i.e. new
> WebSocket("wss://..." ) is valid in both javascript and Akasha java.
> How
> does it work?
>
> Akasha is kept with evolving browser standards by fetching WebIDL and
> processing the WebIDL to generate source code and other artifacts.
>
> WebIDL  is used by various
> specifications to communicate the interfaces that are expected to be
> implemented in web browsers. Many web browsers also use a WebIDL variant to
> generate code to implement the specification.
>
> WebIDL published as part of the official specifications are not always
> perfect representations of the interfaces as implemented by the web
> browsers. Nor is there a central place that contains the complete WebIDL
> that a browser is expected to implement. The Akasha suite defines a
> pipeline for processing WebIDL schemas. The pipeline defines a series of
> stages. Each stage will either transform a schema, combine multiple schemas
> or perform an action for the schema. This capability allows the tool to
> process the WebIDL schemas fetched from the specifications and combine them
> into a consistent document.
>
> The Akasha suite also includes tools to fetch data from other locations
> and combine the data with the WebIDL in processing stages. 

Re: DominoKit release announcement

[Juan Pablo Gardella]

Awesome! Thanks!!

On Mon, 29 Mar 2021 at 16:10, Vegegoku  wrote:

> Dears
>
> DominoKit team are very happy to announce the first Dominokit toolset
> release candidate, it took us too long but it is finally here and all our
> tools are now available on maven center,
>
> the released supports *GWT 2.9.0* and *Java11*, find below a list of all
> tools and released versions :
>
> domino-ui 
> Release: *1.0.0-RC1*
> Development: *HEAD-SNAPSHOT*
>
> domino-rest 
> Release: *1.0.0-RC1*
> Development: *HEAD-SNAPSHOT*
>
> domino-jackson 
> Release: *1.0.0-RC2*
> Development: *HEAD-SNAPSHOT*
>
> domino-mvp 
> Release: *1.0.0-RC1*
> Development: *HEAD-SNAPSHOT*
>
> domino-history 
> Release: *1.0.0-RC2*
> Development: *HEAD-SNAPSHOT*
>
> domino-aggregator 
> Release: *1.0.2*
> Development: *HEAD-SNAPSHOT*
>
> domino-slf4j-logger 
> Release: *1.0.2*
> Development: *HEAD-SNAPSHOT*
>
> domino-keycloak 
> Release: *1.0.0*
> Development: *HEAD-SNAPSHOT*
>
> domino-immutables 
> Release: *1.0.0*
> Development: *HEAD-SNAPSHOT*
>
> Domino-cli  have also been
> updated to generate projects that use the new releases
>
> You can download the CLI from the project releases
>  page
>
> Your feedback and testing are very welcome.
>
> With regards
>
> DominoKit team
>
>
> --
> 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/b46a97ce-75b7-49b9-8209-490b1b60f910n%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/CA%2BkiFscqm0xvByT7sq3Wz%2Bj70kUCFOj3hBa6J9XNRpwrXAoEVA%40mail.gmail.com.

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

[Juan Pablo Gardella]

Hi Vegeoku,

Could you please elaborate on this?

*IMHO tests should help you improve the design of your code, Mockito is the
opposite of that, Once I converted some test cases to use manually writing
test doubles (spies, fakes, stubs) instead of Mockito to show the other guy
how it reduced the code in the test and improves the design. Mockito makes
it super easy to look away from design issues.*

Thanks,
Juan

P.S. Amazing thread.

On Wed, 10 Mar 2021 at 12:47, Josselin Bardet  wrote:

>
>
> Le mer. 10 mars 2021 à 16:42, Vegegoku  a écrit :
>
>>
>>>
>>> Spring: I think the thing I dislike the most about Spring is what many
>>> people like about it: it's an entire, wide, and fat, ecosystem. You can
>>> hardly use one piece of Spring without using everything else; I mean, each
>>> Spring piece builds on top of another Spring piece, so it's basically an
>>> all-or-nothing. I also fear that people doing mostly Spring won't know how
>>> to do things without it (like most big/fat framework actually).
>>>
>>
>>
>> That does really summaries it about spring, also I hate how it is being
>> overused for simple projects,  Like sucking this huge ecosystem just
>> because we need dependency injection or want to talk to the database (JPA
>> -> spring data) and it ends up building a huge complexity instead of
>> simplifying things.. (Tests for example), I once want to contribute to a
>> project that was using spring to find out that I had to inject a single
>> bean into 500+ other classes using the constructor where even the arguments
>> were not arranged to make this any easier and while doing that I had to
>> fight merge conflicts .. it is overrated and overused .. and I pretty sure
>> that most of spring project developer relay too much on mocking to make the
>> tests faster or avoid such dependency injection hell.
>>
>>
>
> Spring is well tested and works well, can handle your transctions, can
> help you to make AOP, can make dependency injection, etc...
> Spring is for me a killer feature, I can't imagine making a project, even
> simple, without using it.
>
> I don't think nowadays there is a good reason to "optimize" and don't use
> spring
>
> --
> 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/CAHDmNXFaUH815r4kDm64HPqDSnqErtPP41tsSHmT%3Dt%2BirNco%3Dg%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/CA%2BkiFsfC8y_JK2Gkayk-OKamH93HybgfGqSZEkZT%2B%2BJaciwQ9Q%40mail.gmail.com.

Re: A new article about GWT and IndexedDB with well known Design Patterns

[Juan Pablo Gardella]

Thanks Lofi!!

On Wed, 28 Oct 2020 at 19:11, lofid...@gmail.com 
wrote:

> A new article about GWT and IndexedDB with known Design Patterns, enjoy
> reading: http://bit.ly/GwtIndexedDBDesignPatterns
>
> Enjoy reading, thanks.
> Lofi
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/7011834c-e30e-4c2a-aaa1-bbd7bee0a3ecn%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/CA%2BkiFseUtQqYC-xAVZkjt8Fwm6AS_4uq4obxCYxiOwC6Z9c3uA%40mail.gmail.com.

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

[Juan Pablo Gardella]

+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 <
>> google-web-tool...@googlegroups.com> 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
>>> 
>>> .
>>>
>> --
> 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/8b4addde-bf52-4a88-b38f-fd2c0493f9f9n%40googlegroups.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/CA%2BkiFscwn64KFDxxoqNx5hKRWCVQZ08HkS9GkbZvw6%3D%3D_5YcWA%40mail.gmail.com.

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

[Juan Pablo Gardella]

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 <
google-web-toolkit-contributors@googlegroups.com> 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-contributors+unsubscr...@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
> 
> .
>

-- 
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/CA%2BkiFsd7i9fZj5tXLTDN5hE0yCe%2BvtDuEt7Ydu%3DxafJe35jycQ%40mail.gmail.com.

Re: Padlet for GWT / J2CL

[Juan Pablo Gardella]

Great! Thanks for sharing

On Mon, 27 Apr 2020 at 16:01, Dr. Lofi Dewanto 
wrote:

> Hi All,
>
> I build a Padlet for GWT / J2CL for Dummies... You can add an item but I
> need to take a look at it first.
>
> Here you are: https://bit.ly/GWTIntroPadlet
>
> Hope to get more beginners coming to GWT / J2CL 
>
> Cheers,
> Lofi
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/4affcf7c-ea3f-4701-a9ec-f7958e28d7df%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/CA%2BkiFsf0U_9G8_UYqAJjr1dsfgZ_CnnJiSpzF6uU76YWBZkF6g%40mail.gmail.com.

Re: [gwt-contrib] Testing GWT 2.9.0 for release

[Juan Pablo Gardella]

I verified GWT 2.9.0-RC1 in one of my applications without issues. The
tests I could not complete due an ant issues to build the samples.

Juan

On Sun, 19 Apr 2020 at 22:01, Colin Alworth  wrote:

> We're having an issue related to the java7->java8 update, the build isn't
> properly including the full sources for the included sample projects. By
> itself, not a big deal, but it could imply that other assumptions of the
> ant build are broken too. I'm looking into it, we'll have an updated
> release candidate when we figure it out.
>
> https://github.com/gwtproject/gwt/issues/9682: The 2.9 candidate was cut
> before the java.io changes came in, so this will not be included in the
> first 2.9 at least, though will likely show up later (See the 4th point in
> this email).
>
> Removing validation: as a rule, the main GWT project rarely, if ever,
> removes anything within a major release. This is very deliberate, so that
> updating to the latest release (to fix security issues, to support
> newer/changing/breaking browsers, improve performance) is accessible to
> stable projects in maintenance mode, with no surprises. Since gwt-dev and
> gwt-user are strongly tied to each other, it isn't feasible to even suggest
> that someone update part of their project, but continue to use older jars
> (such as updating the compiler to fix some issue, but still keeping an old
> gwt-user so that the now-deprecated validation doesn't change or
> disappear). This is why each module that is being broken out will now live
> in its own git repo, own jar, and be versioned separately from the others.
> My best guess here is that we can try for a "minimal gwt-user" which just
> has enough to let the compiler work, and assume that developers switch to
> the org.gwtproject modules that they want, plus anything thirdparty like
> validation. That said, validation is basically the only thing that _isn't_
> ready for j2cl, and there is a small gwt-validation project that has gotten
> started that is compatible with both gwt2 and j2cl - do you have plans to
> finish https://gitlab.com/ManfredTremmel/gwt-bean-validators/-/issues/3?
> Both topics (further modularizing gwt-user, and apt for validation) are
> probably better discussed in another thread, or in gitter.
>
> CL 19800: Agreed, sucks that this fell through the cracks. Two thoughts:
> lets get that into gwt-i18n as soon as possible, and lets try to land that
> patch after 2.9.0 is cut and shipped. The plan is that 2.9.x gets updated
> regularly (6-8 weeks sort of thing) with any changes, and marked with a
> date rather than just an occasional version.
>
> --
> 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/9b91b87d-4ff7-483a-99cc-356bb4ce00d9%40googlegroups.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/CA%2BkiFscYV4and2TSffgBA65x-hwucVkpi51Opzex3AtZ0WU%3D5w%40mail.gmail.com.

Re: [gwt-contrib] Testing GWT 2.9.0 for release

[Juan Pablo Gardella]

Hi Colin,

Could you please share the spreadsheet again?

Juan

On Mon, 13 Apr 2020 at 23:43, Colin Alworth  wrote:

> Hi all,
> We have a build ready to test for GWT 2.9.0, and are looking for
> volunteers to verify that things are behaving properly on a variety of
> platforms. If you have an hour or two free and can help us out, we would
> appreciate it.
>
> We're hoping for a cross-section of testing that verifies
>  * JVM version: 8, 11, 14
>  * Operating System: Linux, OS X, Windows (8, 8.1, 10)
>  * Browser: Chrome, Firefox, Safari, IE11, Edge
>
> If a tester has access to more than one of these at a time, the tests will
> probably go more quickly than two individuals testing the same setup.
> Please note that while Microsoft still provides virtual machines for
> testing purposes, only Windows 10 appears to be available, though with both
> IE11 and Edge (
> https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/).
>
> Please send me an email off-list with the various options you are able to
> test, and I'll get you on the testing spreadsheet.
>
> Thanks!
>
> --
> 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/c0e7162a-5217-4e89-8c50-ee3c051202c2%40googlegroups.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/CA%2BkiFseb94LNZo8-vqXD6KTTHApRq8jAAnL7gW18EoTHygzz3w%40mail.gmail.com.

Re: GWT SuperDev sourcemaps suddenly not being loaded by Chrome/FireFox/IE/Edge

[Juan Pablo Gardella]

Did you try if org.realityforge.com.google.gwt release has the same problem?

On Fri, 24 Jan 2020 at 14:12, David Nouls  wrote:

> I am using GWT for many years now. My project uses 2.8.2 and we are using
> SDM for debugging.
> For some reason suddenly I can no longer debug my application in any of my
> browsers on my machine.
> I was working up to 2 weeks ago and now it no longer works.
>
> I have searched the internet for any hints what might be causing this...
> but found nothing that helps.
>
> The strange thing is that it works when I connect from another PC to the
> same server that it works.
>
> When SDM starts it prints that sourcemaps are available... but Chrome
> never even tries to download them.
> In IE11 the button to download sourcemaps is disabled (and the mouseover
> says that there are no sourcemaps available).
>
> Anybody a clue on what is driving the browser to decide that there are
> sourcemaps or not ?
>
> What I don't get is that the problem is only on my machine (accessing the
> same server) and the problem is across all the browsers I have installed on
> 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/5ce2b53e-6c9e-46ec-9e88-8b57da873ef0%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/CA%2BkiFsc2u%2BecGZem3L7Hw6_cRVG21JAp17H%3DBm5XJ%3DJibf%3DVjQ%40mail.gmail.com.

Re: Nalu v2.0.0 is released!

[Juan Pablo Gardella]

Thanks Frank!

On Sun, 1 Dec 2019 at 08:17, Frank Hossfeld  wrote:

> The next version of Nalu  (v2.0.0) is
> released.  A complete list of changes can be found here: release-notes
> .
>
> Maven Central is updated. Please use the Gitter room
>  in case of questions.
>
> Thanks to anyone who helped!
>
> --
> 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/ac6a9f7d-ca3d-44b1-967c-8bb7edf42752%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/CA%2BkiFsc0SSFNHrFStXq4jk7EA7s2TD6sYXDhvLtck9vkVZN4yQ%40mail.gmail.com.

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

[Juan Pablo Gardella]

Thanks!

On Mon, 11 Nov 2019 at 00:19, 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/CA%2BkiFseMCfobEA4aXga-UB1ZcSKWO%3DDStXeNdtfK5F%3DZgcA6sw%40mail.gmail.com.

Re: Has anyone come up with an annotation processor that can mimic the functionary of resources?

[Juan Pablo Gardella]

Thanks Jens,

Do you know if there is a resource where all modules and its repository are
documented? I saw some google doc before, but I do not know if it is the
last resource with all github repo.

Juan

On Tue, 22 Oct 2019 at 03:17, Jens  wrote:

> The migrated (J2CL / GWT3 ready) version of GWT Resources uses annotation
> processing: https://github.com/treblereel/gwt-resources/
>
> -- 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/aff146ac-f8d2-4b58-a5e1-b8d909507d42%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/CA%2BkiFsezTm%3DTG3NcdrqoHGg0wNygneZyKho4%3DoGw5Y6oxSDa%3Dg%40mail.gmail.com.

Re: Building a GWT project in Eclipse 2019-03+ with Java 11.

[Juan Pablo Gardella]

not Jenkins, Jetty webapp I mean.

On Wed, 24 Jul 2019 at 12:45, Juan Pablo Gardella <
gardellajuanpa...@gmail.com> wrote:

> Hi Jim,
>
> I am working with GWT 2.8.2 + Java11 in a multi module maven project. You
> can use https://tbroyer.github.io/gwt-maven-plugin/ to create a simple
> archetype from it and start putting your classes according it usage (that
> information is described in the links shared by Thomas).  To run/debug the
> project, I execte *mvn gwt:codeserver *from parent project (pom artifact)
> and I created a Eclipse launcher at server artifact (it starts a Jenkins
> webapp). Let me know if it is clear.
>
> In my case, the server is a spring boot application. There are some tricks
> to handle the static content, but you workaround them by adding some
> properties. I could provide a simple sample if you want.
>
> Juan
>
>
> On Wed, 24 Jul 2019 at 12:40, Thomas Broyer  wrote:
>
>>
>>
>> On Wednesday, July 24, 2019 at 5:14:42 PM UTC+2, Jim Douglas wrote:
>>>
>>> > Sure. Use a build tool of your choice and use the maven dependencies.
>>>
>>> I don't know what that means. As far as I've ever known, developing a
>>> GWT application in Eclipse implies installing the GWT Plugin for Eclipse
>>> and picking a GWT SDK.
>>>
>>> http://www.gwtproject.org/usingeclipse.html
>>>
>>
>> Nope.
>> Install the GWT Eclipse Plugin (
>> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html;
>> note that the SDKs are optional).
>> Create (
>> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/maven/Maven.html)
>> or import (
>> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/workspace/Importing.html)
>> a Maven project using GWT.
>> You're all set; the plugin will use the GWT dependencies from the Maven
>> project.
>>
>> --
>> 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/1659e95f-d41b-4dc4-9787-95d50bc5a120%40googlegroups.com
>> <https://groups.google.com/d/msgid/google-web-toolkit/1659e95f-d41b-4dc4-9787-95d50bc5a120%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/CA%2BkiFsfjGPz9m0yN-6ywt6OMLXijwCr8HkjCVU4mnvhzdFJ2BQ%40mail.gmail.com.

Re: Building a GWT project in Eclipse 2019-03+ with Java 11.

[Juan Pablo Gardella]

Hi Jim,

I am working with GWT 2.8.2 + Java11 in a multi module maven project. You
can use https://tbroyer.github.io/gwt-maven-plugin/ to create a simple
archetype from it and start putting your classes according it usage (that
information is described in the links shared by Thomas).  To run/debug the
project, I execte *mvn gwt:codeserver *from parent project (pom artifact)
and I created a Eclipse launcher at server artifact (it starts a Jenkins
webapp). Let me know if it is clear.

In my case, the server is a spring boot application. There are some tricks
to handle the static content, but you workaround them by adding some
properties. I could provide a simple sample if you want.

Juan


On Wed, 24 Jul 2019 at 12:40, Thomas Broyer  wrote:

>
>
> On Wednesday, July 24, 2019 at 5:14:42 PM UTC+2, Jim Douglas wrote:
>>
>> > Sure. Use a build tool of your choice and use the maven dependencies.
>>
>> I don't know what that means. As far as I've ever known, developing a GWT
>> application in Eclipse implies installing the GWT Plugin for Eclipse and
>> picking a GWT SDK.
>>
>> http://www.gwtproject.org/usingeclipse.html
>>
>
> Nope.
> Install the GWT Eclipse Plugin (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html;
> note that the SDKs are optional).
> Create (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/maven/Maven.html)
> or import (
> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/workspace/Importing.html)
> a Maven project using GWT.
> You're all set; the plugin will use the GWT dependencies from the Maven
> project.
>
> --
> 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/1659e95f-d41b-4dc4-9787-95d50bc5a120%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/CA%2BkiFsdDxNkOBiBLoRX78w8g2QKKAvqb_QQ3rCwea-zgK5M4Vw%40mail.gmail.com.

Re: [ANN] (Unofficial) Elemental2 1.0.0-b21-6a027d2 release

[Juan Pablo Gardella]

Thanks Peter!

On Sun, 7 Apr 2019 at 23:41, Peter Donald  wrote:

> Elemental2 provides type checked access to browser APIs for Java
> code. This is done by using closure extern files and generating
> JsTypes, which are part of the new JsInterop specification that
> is both implemented in GWT and J2CL.
>
> https://github.com/google/elemental2
>
> This is an unofficial release to Maven Central under a different groupId.
> Please don't bug the original authors. Versions are released on demand.
>
> API Changes relative to Elemental2 version 1.0.0-b20-bfe6e22
>
> elemental2-core: Full details at
> https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-core=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
>   4 non breaking changes.
>   4 potentially breaking changes.
> elemental2-dom: Full details at
> https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-dom=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
>   38 non breaking changes.
>   149 potentially breaking changes.
>   49 breaking changes.
> elemental2-media: Full details at
> https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-media=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
>   3 non breaking changes.
>   3 potentially breaking changes.
>   8 breaking changes.
> elemental2-promise: Full details at
> https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-promise=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
>   1 non breaking changes.
>   2 breaking changes.
> elemental2-svg: Full details at
> https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-svg=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
>   137 breaking changes.
> elemental2-webgl: Full details at
> https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-webgl=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
>   8 non breaking changes.
>   4 potentially breaking changes.
>   8 breaking changes.
>
> The Maven dependencies can be added to your pom.xml via
>
> 
>   org.realityforge.com.google.elemental2
>   ${artifact-id}
>   1.0.0-b21-6a027d2
> 
>
> where artifact-id is one of
>
> * elemental2-core
> * elemental2-dom
> * elemental2-promise
> * elemental2-indexeddb
> * elemental2-svg
> * elemental2-webgl
> * elemental2-media
> * elemental2-webstorage
> * elemental2-webassembly
>
> Hope this helps,
>
> Peter Donald
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Question about SuperDevMode/codeserver

[Juan Pablo Gardella]

I added in a local maven profile an extra property file to instruct sprint
boot where check the static resources.

spring.resources.static-locations=${gwtBasePathLocation},classpath:/META-INF/resources/,classpath:/resources/,classpath:/static/,classpath:/public/


On Wed, 6 Mar 2019 at 11:13 Bryan Bende  wrote:

> I was able to set the launcherDir to server/target/classes/static and that
> seems to make it work the way I was expecting.
>
> On Tuesday, 5 March 2019 13:55:54 UTC-5, Bryan Bende wrote:
>>
>> Hello,
>>
>> I have a multi-module Maven project setup similar to the multi-module
>> archetype, but created before I knew about that, using GWT 2.8.2 and the
>> gwt-maven-plugin 1.0-rc-9.
>>
>> shared - Contains DTOs with JS interop annotations, packaged as gwt-lib
>> client - GWT code, depends on shared as gwt-lib
>> server - spring-boot application which depends on client and shared
>> modules, packages the nocache.js from client into target/classes/static at
>> build time, also serves the index.html
>>
>> I launch the application from IntelliJ using a standard run configuration
>> to start the server, and then a "mvn gwt:codeserver" from the root module
>> where launcherDir is pointing to
>> "{project.build.Directory}/gwt/launcherDir" of the root module.
>>
>> The first time I load the application in Chrome it will automatically
>> compile and then load fine. If I then make a change to something in the
>> client module and refresh the page, it does not automatically compile. If I
>> then click the bookmark for "Dev Mode On", it will pop up the dialog and if
>> I click compile it works fine.
>>
>> I'm trying to figure out what the difference is between the first page
>> load and the subsequent ones. Looking in Chrome Dev Tools after the first
>> page load, I can see that some script elements get injected at the top of
>> the head element related to recompile, but then when I do the next refresh
>> some of those elements are no longer there, but there is still one element
>> pointing to the codeserver for the nocache.js.
>>
>> Is there anything obvious that I'm missing preventing the auto-compile on
>> refresh?
>>
>> One thing I tried was altering the server's locations for static
>> resources by setting
>> spring.resources.static-location=file://../target/gwt/launcherDir,classpath:/static/
>> so that it would load the nocache.js from the launcherDir, but doesn't seem
>> to really change the behavior. Maybe that part isn't working the way I
>> think it is.
>>
>> Thanks,
>>
>> Bryan
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [ANN] (Unofficial) elemental2-webassembly release

[Juan Pablo Gardella]

Thanks Peter!

On Fri, 22 Feb 2019 at 06:57 Peter Donald  wrote:

> Elemental2 provides type checked access to browser APIs for Java
> code. This is done by using closure extern files and generating
> JsTypes, which are part of the new JsInterop specification that
> is both implemented in GWT and J2CL.
>
> https://github.com/google/elemental2
>
> This is an unofficial release to Maven Central under a different groupId
> and is completely unofficial so please don't bug the original authors. A
> new version is released on demand.
>
> This release includes the first release of elemental2-webassembly. Huzzah!
> Please take it for a test drive and report any bugs.
>
> API Changes relative to Elemental2 version 1.0.0-b17-6897368
>
> elemental2-core: Full details at
> https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-core=1.0.0-b17-6897368=1.0.0-b18-f3472e7
>   7 non breaking changes.
>   4 potentially breaking changes.
>   2 breaking changes.
>
> The Maven dependencies can be added to your pom.xml via
>
> 
>   org.realityforge.com.google.elemental2
>   ${artifact-id}
>   1.0.0-b18-f3472e7
> 
>
> where artifact-id is one of
>
> * elemental2-core
> * elemental2-dom
> * elemental2-promise
> * elemental2-indexeddb
> * elemental2-svg
> * elemental2-webgl
> * elemental2-media
> * elemental2-webstorage
> * elemental2-webassembly
>
> Hope this helps,
>
> Peter Donald
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Happy to announce general access for J2CL!

[Juan Pablo Gardella]

Thanks!

On Tue, 13 Nov 2018 at 22:39 'Goktug Gokdogan' via GWT Users <
google-web-toolkit@googlegroups.com> wrote:

> Dear GWTers!
>
> We are happy to announce that we have opened up J2CL repository for
> general access:
> http://github.com/google/j2cl
>
> Please see the README for details and instructions.
>
> I also would like to use this opportunity to thank all Googlers who
> contributed over the years and made this happen.
>
> Enjoy!
>
> Goktug, on behalf of J2CL team
>
> PS: If you are using Windows, you might have a bumpy road but should get
> better over time with your feedback and contributions.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Elemental2 Error

[Juan Pablo Gardella]

Did you include elemental2.dom.Dom  module? Check at
https://github.com/google/elemental2#gwt

On Wed, 6 Dec 2017 at 19:34 Joe Wu  wrote:

> I have been using GWT for a while but I am new to elemental2, I have tried
> the following code to create new navigator object in GWT:
>
> import elemental2.dom.Navigator;
>
>
> and for entrypoint
>
>
> private Navigator Nav = new Navigator();
>
>
> the following are the first several lines of the error message I got
> during compile:
>
>
>
> [ERROR] elemental2.dom.Navigator cannot be resolved to a type
>
>  [ERROR] Errors in 'elemental2/dom/Navigator.java'
>
> [ERROR] elemental2.dom.ServiceWorkerContainer cannot be
> resolved to a type
>
>  [ERROR] Errors in 'elemental2/dom/BatteryManager.java'
>
> [ERROR] elemental2.dom.EventTarget cannot be resolved to a
> type
>
>
> can anyone help?
>
>
> Thanks,
>
> Joe
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [gwt-contrib] Last call for GWT 2.8.2 patches, and testers needed!

[Juan Pablo Gardella]

How can I contribute to test?

On Tue, 3 Oct 2017 at 07:28 Colin Alworth  wrote:

>

-- 
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/CA%2BkiFse7CgsakT%2B7OGzLt_3gjnAF2YOTt2dij5sFWfH1gih3Og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: First beta release of Vue GWT

[Juan Pablo Gardella]

Awesome! Great work

On Thu, 7 Sep 2017 at 10:42 Adrien Baron 
wrote:

> Hi!
>
> We have just released the first beta version of Vue GWT
> .
> Vue GWT integrates Vue.js  with GWT 2.8 using
> JsInterop. It lets you write Vue.js components in Java.
>
> *Features*
>
>- HTML template, with *2-way data binding*
>- Template expressions *type checking* at compile time
>- Use *regular* *Java Objects and Collections* in your templates
>- Support *injection* in Components
>- Integrates with GWT Resources and Widgets
>- HTML templates are compiled to JavaScript during Java Compilation
>(only requires Vue.js runtime)
>- Supports most of Vue.js features
>- Supports Vue Router integration with Vue Router GWT
>
>
> *Want to see what it looks like?*
>
> We have a pretty detailed documentation
>  with live examples.
>
> *Who is using this?*
>
> We have been using it internally at GenMyModel
>  on some projects.
> We would be very happy to get more feedback from you, we have a gitter
> available  in case you have any
> questions.
>
> *Is it stable?*
>
> Vue GWT is in Beta. Which means it still requires some testing and may
> contain some bugs.
> For now we recommend trying it on internal projects, or in non critical
> parts of your apps in production.
>
> We hope you'll enjoy using it as much as we do!
> The GenMyModel team.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Progressive Web App with Caching and Code Splitting

[Juan Pablo Gardella]

+1

On Mon, 7 Aug 2017 at 15:05 Slava Pankov  wrote:

> It would be really nice if you share details or even code of your
> implementation.
>
>
> On Monday, August 7, 2017 at 7:21:19 AM UTC-7, Gernot Pansy wrote:
>>
>> I got it myself working, with a extended Linker and the using of
>> XhrFragementLoader.
>>
>> On Friday, August 4, 2017 at 12:00:55 AM UTC+2, Gernot Pansy wrote:
>>>
>>> Hi,
>>>
>>> I wan't to convert my GWT (2.8.1) application to an progressive web app
>>> and add code splitting. I already build a custom Linker which creates a
>>> service worker file automatically and the caching is working except of the
>>> deferred fragemnts.
>>> My service worker is not called if the are loaded, it seems they are
>>> loaded outside of the scope.
>>>
>>> The same happens in this demo:
>>> http://www.g-widgets.com/2016/08/11/progressive-web-apps-recipes-for-gwt/
>>>
>>> If you look in the chrome console, all request are loaded trough the
>>> service worker but not the fragments (only once in install phase, because
>>> the are all files cached).
>>>
>>> Seems that this is the relevant code:
>>> https://github.com/gwtproject/gwt/blob/master/dev/core/src/com/google/gwt/core/ext/linker/impl/runAsync.js
>>> Here is still the old language property used on the script tag.
>>>
>>> Has anyone an idea how to fix that?
>>>
>>> cheers,
>>> gernot
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Problems with Eclipse Oxygen and GWT Plugin

[Juan Pablo Gardella]

I'm using https://github.com/gwt-plugins/gwt-eclipse-plugin without
problems. Try with this.



On Fri, 7 Jul 2017 at 06:30 JP  wrote:

> Hello,
>
> I have installed Eclipse Oxygen Release Java EE IDE for Web Developers (64
> bit) and found GWT Eclipse Plugin 3.0.0 in the Marketplace.
>
> After successfully installation of the plugin, I tried to create a new GWT
> Web Application Project *without *sampe code. The result was an error
> "Creation of element failed".
>
> I tried another project creation, this time *with* sample code. It
> worked! However, when I tried to add a GWT module, I got another error
> (extract from log file):
>
> !MESSAGE Problems occurred when invoking code from plug-in:
> "org.eclipse.jface".
> !STACK 0
> java.lang.ClassCastException: org.eclipse.jdt.internal.core.JarEntryFile
> cannot be cast to org.eclipse.core.resources.IFile
> at
> com.google.gwt.eclipse.core.modules.AbstractModule.getShortName(AbstractModule.java:294)
> at
> com.google.gwt.eclipse.core.modules.AbstractModule.getQualifiedName(AbstractModule.java:272)
> at
> com.google.gwt.eclipse.core.modules.ModuleJarResource.getQualifiedName(ModuleJarResource.java:1)
> at
> com.google.gwt.eclipse.core.modules.AbstractModule.getSimpleName(AbstractModule.java:342)
> at
> com.google.gwt.eclipse.core.modules.ModuleJarResource.getSimpleName(ModuleJarResource.java:1)
> at
> com.google.gwt.eclipse.core.modules.ModuleUtils$3.visit(ModuleUtils.java:220)
> at
> com.google.gwt.eclipse.core.modules.ModuleUtils$3.visit(ModuleUtils.java:1)
> ...
>
> How can I create a module? Is there a way around this error?
>
> Kind regards,
>
> JP
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: MS Edge - readEntries() doesn't work

[Juan Pablo Gardella]

See https://groups.google.com/forum/#!topic/google-web-toolkit/5KrtRLw6gYo for
usage of gwt 2.8.x with java6

On Wed, 7 Jun 2017 at 12:10 Daniel Kln  wrote:

> Hello everyone,
>
> i want to traverse a file system like in following example:
>
> function traverse(entry, path) {
>   path = path || "";
>   if (entry.isFile) {
> // Get file
> item.file(function(file) {
>   console.log("File:", path + file.name);
> });
>   } else if (entry.isDirectory) {
> // Get folder contents
> var dirReader = entry.createReader();
> dirReader.readEntries(function(entries) {
>   for (var i = 0; i < entries.length; i++) {
> traverse(entries[i], path + entry.name + "/");
>   }
> });
>   }
> }
>
> dropArea.addEventListener("drop", function(e) {
>   e.preventDefault();
>   var items = event.dataTransfer.items;
>   for (var i = 0; i < items.length; i++) {
> var entry = items[i].webkitGetAsEntry();
> if (entry) {
>   traverse(entry);
> }
>   }
> }, false);
>
>
> My problem is, that in MS Edge it doesn't work. the error callback just 
> returns 'unknown error'.
> And i have really no idea why it is not working in MS Edge. FF and Chrome are 
> ok.
>
> I am using GWT 2.7 --> an update to 2.8 is not possible because i have to use 
> Java 6.
>
> I really hope that anyone of you has any idea for me
>
> Best Regards
>
> Daniel
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GWT/Maven development cycle takes much too long

[Juan Pablo Gardella]

I suggest to make a POC using
https://github.com/tbroyer/gwt-maven-archetypes/ archetype, using
modular-webapp.

On Fri, 21 Apr 2017 at 14:38 Magnus  wrote:

>
>>> So, "mvn package" should Just Work™ (package the lib, then package the
>> app using the lib's jar).
>>
>
> Yes, works!
>
>
>> "mvn gwt:devmode" and "mvn gwt:codeserver" should work without too much
>> configuration (configure warDir/launcherDir, possibly projects/modules)
>>
>
> Actually, it gives an error (see below):
>
> Could not find goal 'devmode' in plugin
> org.codehaus.mojo:gwt-maven-plugin:2.8.0 among available goals...
>
>
> I believe I have to extend the minimal top-level pom.xml, but how?
> And I'd like to leave the pom.xml in the sub folders as is, because they
> are working for their own... Is this possible?
>
>
>> This is also the point with the development cycle: When debugging,
>>> eclipse doesn't "see" the changed library source code, because it fetches
>>> the library source code from the jar file in its own target folder.
>>>
>>
>> Actually the one from your local repository (~/.m2/repository/), not
>> directly the one from the target/ folder.
>>
>
> This is an important point! If the app used the library jar from the
> repository and not from its own target directory, there would be no need to
> "mvn package" the app and this takes most of the time...
>
>
>> Wouldn't it be better for developing if the original library code was
>>> used instead? Could it be that this is the core of the problem?
>>>
>>
>>
>
>> And the problem is that Eclipse errors when importing your app project
>> when using the default configuration for resolving dependencies from the
>> workspace; which is why you turned that setting off.
>>
> If you figure out how to get this working, then it should (hopefully work)
>> the same with or without a reactor.
>>
>
> I can enable it for the lib project without problems. But as soon as I
> enable it for the app project, the error reappears.
> It's hard to figure it out when even the experts in this group have no
> idea. But I see that this is an essential point, so I have documented the
> error as detailed as possible again (see below). I hope there will be a
> solution...
>
> Thanks
> Magnus
>
>
>
> *Maven error when executing "mvn gwt:devmode" at the top-level:*
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] msm-lib-acs
> [INFO] msm.app.bcs.Application
> [INFO] msm
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] msm-lib-acs ... SKIPPED
> [INFO] msm.app.bcs.Application ... SKIPPED
> [INFO] msm ... SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 2.603s
> [INFO] Finished at: Fri Apr 21 19:13:32 CEST 2017
> [INFO] Final Memory: 10M/241M
> [INFO]
> 
> [ERROR] Could not find goal 'devmode' in plugin
> org.codehaus.mojo:gwt-maven-plugin:2.8.0 among available goals clean,
> compile, compile-report, css, debug, eclipse, eclipseTest, generateAsync,
> help, i18n, mergewebxml, resources, run, run-codeserver, source-jar, test
> -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoNotFoundException
>
>
>
>
>
> *Error in the application project's pom.xml when "resolve dependencies" is
> enabled:*
>
> The pom.xml has an error marker at the packaging tag:
>
>
> 
>
> The error behind this error marker is this:
>
> Failed to copy file for artifact
> [msm.lib.acs:msm-lib-acs:jar:1.0-SNAPSHOT:compile]
> (org.apache.maven.plugins:maven-war-plugin:2.2:war:default-war:package)
>
> org.apache.maven.plugin.MojoExecutionException: Failed to copy file for
> artifact [msm.lib.acs:msm-lib-acs:jar:1.0-SNAPSHOT:compile]
> at
> org.apache.maven.plugin.war.packaging.ArtifactsPackagingTask.performPackaging(ArtifactsPackagingTask.java:131)
> at
> org.apache.maven.plugin.war.packaging.WarProjectPackagingTask.handleArtifacts(WarProjectPackagingTask.java:190)
> at
> org.apache.maven.plugin.war.packaging.WarProjectPackagingTask.performPackaging(WarProjectPackagingTask.java:109)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:472)
> at
> org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:404)

Re: Maven/GWT - How to access resources in the resources folder?

[Juan Pablo Gardella]

Remove  * section.

Try to follow maven convention. The resources for GWT web app should be
placed in public folder, see
http://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.html#DevGuideDirectoriesPackageConventions


For ui binder xml files, I put them in java src folder (I can't make
Eclipse works if I put in resources folder)

Regards



On Mon, 17 Apr 2017 at 13:30 Magnus  wrote:

> Ok, I created the directory src/main/resources and added some xml files
> there.
> But they don't get into the jar file...
>
> Below is my pom.xml.
> What's wrong?
>
> Magnus
>
> -
>
> http://maven.apache.org/POM/4.0.0; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
>   4.0.0
>   msm.lib.acs
>   msm-lib-acs
>   jar
>   1.0-SNAPSHOT
>   msm-lib-acs
>   http://maven.apache.org
>
>   
>UTF-8
>1.8
>1.8
>   
>
>
>   
>
> 
>   junit
>   junit
>   3.8.1
>
> 
> 
>
> 
>  javax.mail
>  javax.mail-api
>  1.5.6
> 
>
> 
>  javax.servlet
>  javax.servlet-api
>  3.1.0
> 
>
> 
>  com.google.gwt
>  gwt-user
>  2.8.0
>  provided
> 
>
>
> mysql
> mysql-connector-java
> 6.0.6
>
>
>
> org.postgresql
> postgresql
> 42.0.0
>
>
>
>   
>
> 
>   
> 
>   src/main/resources
> 
> 
>   src/main/java
>   
> msm/lib/acs/awi/**/*.java
> 
> msm/lib/acs/**/*.xml
> msm/lib/acs/awi/**/*.css
> msm/lib/acs/awi/**/*.png
> msm/lib/acs/awi/**/*.js
>   
> 
>   
>
>   
>
>
> org.apache.maven.plugins
> maven-source-plugin
>  
>   
>   attach-sources
>   
> jar
>   
>  
> 
>
>
> 
>   org.apache.maven.plugins
>   maven-javadoc-plugin
>   
> 
>   attach-javadocs
>   
> jar
>   
> 
>   
> 
>
>   
>
>  
>
> 
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: JNDI lookup issue when upgrade GWT from 2.2 to 2.8

[Juan Pablo Gardella]

Gwt 2.8 uses java7. Are you using this version? The jndi name AFAIK is
defined in jboss-web.xml file for jboss

El dom., 16 de abr. de 2017 21:26,  escribió:

> We used GWT for many years and not upgrade it for far.
> We want to upgrade it to the latest GWT 2.8 and Java 1.8. We had a lot of
> issues.
>
> Currently we had problem to create a data source with Spring under JBoss
> 6.4. It used to work on under GWT 2.2.
>
> The data source is defined in JBoss and it bounds to the database without
> issue. It specified JNDI name there.
>
> In Spring context we reference the jndi name defined in JBoss data source:
>
>  class="org.springframework.jndi.JndiObjectFactoryBean">
> 
> java:jboss/datasources/oe
> 
> 
>
> This used to work in GWT 2.2 but not in GWT 2.8. It tried to look in the
> jetty environment.It failed to find the jndi name.
> Do I need to specify something special to let it looking for the JBoss
> defined jndi name?
>
> 23:39:32,746 DEBUG
> [org.springframework.beans.factory.support.DefaultListableBeanFactory]
> (ServerService Thread Pool -- 53) Invoking afterPropertiesSet() on bean
> with name 'dataSource'
> 23:39:32,746 DEBUG [org.springframework.jndi.JndiTemplate] (ServerService
> Thread Pool -- 53) Looking up JNDI object with name
> [java:jboss/datasources/oe]
> 23:39:32,746 DEBUG [jndi] (ServerService Thread Pool -- 53)
> InitialContextFactory.getInitialContext()
> 23:39:32,746 DEBUG [jndi] (ServerService Thread Pool -- 53) Created
> initial context delegate for local namespace:
> org.eclipse.jetty.jndi.local.localContextRoot@7f559695
> 23:39:32,746 DEBUG [jndi] (ServerService Thread Pool -- 53) Looking up
> name="java:jboss/datasources/oe"
> 23:39:32,777 ERROR [org.springframework.web.context.ContextLoader]
> (ServerService Thread Pool -- 53) Context initialization failed:
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'departmentCodeDAOImpl': Injection of persistence
> dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'entityManagerFactory' defined in ServletContext resource
> [/WEB-INF/classes/resources/database-context.xml]: Cannot resolve reference
> to bean 'dataSource' while setting bean property 'dataSource'; nested
> exception is org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'dataSource' defined in ServletContext resource
> [/WEB-INF/classes/resources/database-context.xml]: Invocation of init
> method failed; nested exception is javax.naming.NameNotFoundException;
> remaining name 'java:jboss/datasources/oe'
> Related cause: org.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'dataSource' defined in ServletContext
> resource [/WEB-INF/classes/resources/database-context.xml]: Invocation of
> init method failed; nested exception is javax.naming.NameNotFoundException;
> remaining name 'java:jboss/datasources/oe'
> at
> org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor.postProcessPropertyValues(PersistenceAnnotationBeanPostProcessor.java:342)
> [org.springframework.orm-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1106)
> [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517)
> [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
> [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
> [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
> [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
> [org.springframework.beans-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913)
> [org.springframework.context-3.1.1.RELEASE.jar:3.1.1.RELEASE]
> at
> 

Re: Maven/GWT - How to access resources in the resources folder?

[Juan Pablo Gardella]

Check
https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html

On Thu, 13 Apr 2017 at 11:08 Magnus  wrote:

> Hello,
>
> I would like to follow the Maven conventions and place my resources into
> the resources folder.
>
> How can I access a file in the resources folder server-side so that I have
> an InputStream then?
>
> My projects were created with maven and webAppCreator, and they do not
> contain a resources folder. So I have to create it.
> What's the standard location? src/main/resources?
>
> Thanks
> Magnus
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Debug library code in eclipse

[Juan Pablo Gardella]

Using eclipse you don't need do that. Simply include all the projects
(including pom artifact if you have one) and configure by using "workspace
resolution". Check
https://books.sonatype.com/m2eclipse-book/reference/eclipse.html

On Tue, 11 Apr 2017 at 14:06 Magnus  wrote:

> Hi Jens,
>
> I added the plugins to pom.xml and configured eclipse to download the
> sources.
> I did a mvn install for the lib and I can verify that the files
> *-sources.jar and *.-javadoc.jar are created.
> But when starting a debug session for the app in eclipse, I still get the
> message "Source not found".
>
> The JAR file
> /home/.../.m2/repository/msm/lib/acs/1.0-SNAPSHOT/msm-lib-acs-1.0-SNAPSHOT.jar
> has no source attachment.
>
>
> What may be still wrong?
>
> Magnus
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Compilation of a large GWT application?

[Juan Pablo Gardella]

Also check the classes that are used by GWT-RPC. For example if those
classes are using List instead of ArrayList for example, will generate more
JS output.

On Tue, 11 Apr 2017 at 12:13 Jens  wrote:

>
> Our optimized output with collapse all is 23 MB. Things are reused though,
> which is visible in left-over taking 6 MB.
>
>
> How large is a single permutation (= not using collapse-all)? Our app is
> roughly 300KLOC and results in roughly 6-7MB optimized JS for a single
> permutation when doing a production build. In total we generate 3
> permutations (Firefox, IE, Chrome). However we use SuperDevMode / GWT
> compiler with just 4GB Heap space configured for the JVM. Seems weird that
> you need 16GB for a build that probably isn't that different.
>
> Libraries are kind of standard I guess: GWT-RPC, UiBinder, Google GIN, a
> 3rd party JS lib for graphs.
>
> Maybe your issue is some 3rd party generator that simply consumes way to
> much memory and should be fixed / optimized? Have you run SDM / GWT
> Compiler in debug mode and attached a debugger to it so you can make a heap
> dump once heap is quite high to see who is consuming all the memory?
>
> -- 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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: How to deal with transitive maven dependencies?

[Juan Pablo Gardella]

Remove provided at

 
  msm.lib.acs
  msm-lib-acs

…

  1.0-SNAPSHOT
  provided



On Wed, 29 Mar 2017 at 14:28 Magnus  wrote:

> Yes! It's taken from the maven repository!
>
> What about the dependencyManagement thing?
>
> Magnus
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: How to deal with transitive maven dependencies?

[Juan Pablo Gardella]

Are you sure postgres library group/artifactid/version is ok? Chek at
https://mvnrepository.com/artifact/postgresql/postgresql

On Wed, 29 Mar 2017 at 14:15 Magnus  wrote:

> I have everything in the dependency section.
>
> Here are the complete pom files.
> Note that "mylib" is "msm-lib-acs" and "myapp" is "msm-app-mcs" (I am
> still struggeling with the Maven naming conventions.):
>
> *mylib aka msm-lib-acs, pom.xml:*
>
> http://maven.apache.org/POM/4.0.0; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
>   4.0.0
>   msm.lib.acs
>   msm-lib-acs
>   jar
>   1.0-SNAPSHOT
>   msm-lib-acs
>   http://maven.apache.org
>
>   
>UTF-8
>1.8
>1.8
>   
>
>
>   
>
> 
>   junit
>   junit
>   3.8.1
>
> 
> 
>
> 
>  javax.mail
>  javax.mail-api
>  1.5.6
> 
>
> 
>  javax.servlet
>  javax.servlet-api
>  3.1.0
> 
>
> 
>  com.google.gwt
>  gwt-user
>  2.8.0
>  provided
> 
>
>
> mysql
> mysql-connector-java
> 6.0.6
>
>
>
>
> org.postgresql
> postgresql
> 42.0.0
>
>
>
>   
>
> 
>   
> 
>   src/main/resources
> 
> 
>   src/main/java
>   
> msm/lib/acs/awi/**/*.java
> msm/lib/acs/**/*.gwt.xml
> msm/lib/acs/awi/**/*.css
> msm/lib/acs/awi/**/*.png
>   
> 
>   
> 
> 
>
>
>
> *myapp aka msm-app-mcs, pom.xml:*
>
>
> 
> http://maven.apache.org/POM/4.0.0; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance;
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd;>
>
>   
>   4.0.0
>   msm.app.mcs
>   msm-app-mcs
>   war
>   1.0-SNAPSHOT
>   msm.app.mcs.Application
>
>   
>
> 
> 1.8
> 1.8
>
> 
> UTF-8
>
> UTF-8
>   
>
>   
> 
>   
>   
> com.google.gwt
> gwt
> 2.8.0
> pom
> import
>   
> 
>   
>
>   
> 
>   com.google.gwt
>   gwt-servlet
>   runtime
> 
> 
>   com.google.gwt
>   gwt-user
>   provided
> 
> 
>   com.google.gwt
>   gwt-dev
>   provided
> 
> 
>   junit
>   junit
>   4.11
>   test
> 
>
> 
>   msm.lib.acs
>   msm-lib-acs
>
>   1.0-SNAPSHOT
>   provided
> 
>
>
>   
>
>   
> 
>
> ${project.build.directory}/${project.build.finalName}/WEB-INF/classes
>
> 
>
>   
>   
> net.ltgt.gwt.maven
> gwt-maven-plugin
> 1.0-rc-6
> 
>   
> 
>   import-sources
>   compile
>   import-test-sources
>   test
> 
>   
> 
> 
>   msm.app.mcs.Application
>   Application
>   true
>   
>   1.8
>   
>   
> 
> -compileReport
> -XcompilerMetrics
>   
>   
>
> ${project.build.directory}/${project.build.finalName}
>   compile+runtime
>   
>   
> Application.html
>   
> 
>   
>
>   
>   
> maven-surefire-plugin
> 2.17
> 
>   true
> 
>   
>
> 
>   
> 
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: How to deal with transitive maven dependencies?

[Juan Pablo Gardella]

Did you put it in dependency or dependencyManagement section ? Share the
complete pom files if you can-

On Wed, 29 Mar 2017 at 13:55 Magnus  wrote:

> Hello,
>
> my app uses a separate jar library, which in turn uses another jar file,
> e. g. a postgresql driver:
>
> *Maven project "mylib", pom.xml:*
>
>
> org.postgresql
> postgresql
> 42.0.0
>
>
> *Maven project "myapp", pom.xml:*
>
> 
>   mylib
>   mylib
>   1.0-SNAPSHOT
>   provided
> 
>
> When I build mylib with mvn package install, the PostgreSQL jar file is
> not included or downloaded.
> Also when I build myapp with mvn package, the PostgreSQL jar is not
> fetched.
> So I end up with a missing jar file.
>
> I think (and also strongly hope) that it's one of the strengths of Maven
> that I do not have to repeat the dependency in the myapp project?
>
> Maybe this has something to do with the fact, that no class of the
> PostgreSQL jar file is referenced directly, and therefore not seen by the
> compiler. When the PostgreSQL driver is needed, it's loaded by a String:
>
> Class.forName ("org.postgresql.Driver");
>
>
> How can you include all dependent libraries in the final app package?
>
> Thanks
> Magnus
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GWT 2.8.0 Eclipse

[Juan Pablo Gardella]

I switched without problems (I didn't update anything in eclipse)


On Thu, 23 Feb 2017 at 08:19 prashant fulara 
wrote:

> Given link (https://github.com/gwt-plugins/gwt-eclipse-plugin
> ),
> seems not opening.
>
>
> On Saturday, 18 February 2017 02:32:33 UTC+5:30, Slava Pankov wrote:
>
> This one works with GWT 2.8 perfectly:
> http://storage.googleapis.com/gwt-eclipse-plugin/v3/release
>
> Sources are here: https://github.com/gwt-plugins/gwt-eclipse-plugin
>
> On Friday, February 17, 2017 at 8:45:25 AM UTC-8, l.s...@behaimits.com
> wrote:
>
> Hi, I have noticed that GWT 2.7 is 3 years old. GWT 2.8 final was released
> like half a year ago. How should one develop GWT applications - in which
> IDE? Will there be an update for GWT Eclipse plugin this year?
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: compiler errors after upgrade to gwt 2.8.0

[Juan Pablo Gardella]

The plugin is actually included out of box in eclipse. You can try by
downloading eclipse neon or reinstall the plugin in mars

El vie., 17 de feb. de 2017 01:09, Magnus 
escribió:

> Hello Juan,
>
> ok, I understand that eclipse:eclipse is retired.
>
> I installed m2eclipse from the repository site, but after that there is
> nothing about "maven" in the eclipse menus. Even the option "Import
> existing maven projects" is gone!
> Even after uninstalling m2eclipse the option didn't come back. So my
> eclipse installation (Mars) seems to be corrupted now?
>
> (I did the installation as recommended by starting eclipse as root first.)
>
> Thanks
>
> Magnus
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: compiler errors after upgrade to gwt 2.8.0

[Juan Pablo Gardella]

Check http://maven.apache.org/plugins/maven-eclipse-plugin/

On Thu, 16 Feb 2017 at 15:24 Magnus  wrote:

> Hello Juan,
>
> sorry, it seems that I didn't point out that my problem is solved!
>
> After executing "mvn eclipse:eclipse" the errors are gone!
> So what's wrong with "eclipse:eclipse" then?
>
> Thanks
>
> Magnus
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: compiler errors after upgrade to gwt 2.8.0

[Juan Pablo Gardella]

I suggest the following:

1) Copy src/ + pom.xml file to another directory. (or remove the project
from the eclipse and delete eclipse related files).
2) Import the project again.

Do not use *mvn eclipse:eclipse, *it's better to use m2e plugin. Let me
know also if mvn clean package works (execute that command in console).

Regards,
Juan

P.S. If you are interested in learning maven, I suggest to read *Better
builds with maven, *it's a bit old but very easy to read and free. You can
pick it from https://maven.apache.org/articles.html

On Thu, 16 Feb 2017 at 13:18 Magnus  wrote:

> Hello,
>
> I found that the .classpath file in the root directory of my maven library
> project contains a reference to gwt 2.7.0:
>
> 
> 
>  path="src/test/java">
> 
> 
> 
> 
> 
>  path="src/main/java">
> 
> 
> 
> 
> 
>  path="M2_REPO/javax/mail/javax.mail-api/1.5.6/javax.mail-api-1.5.6.jar"/>
>  path="M2_REPO/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1.0.jar"/>
>  path="M2_REPO/javax/validation/validation-api/
> 1.0.0.GA/validation-api-1.0.0.GA.jar"
> sourcepath="M2_REPO/javax/validation/validation-api/
> 1.0.0.GA/validation-api-1.0.0.GA-sources.jar"/>
>  path="M2_REPO/javax/validation/validation-api/
> 1.0.0.GA/validation-api-1.0.0.GA-sources.jar"/>
>  path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.7">
> 
> 
> 
> 
>  path="M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar"/>
> 
>  path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER">
> 
> 
> 
> 
> 
> 
>
> However, I executed "mvn eclipse:eclipse" and this .classpath file was
> regenerated with the correct gwt version!
> Is this the way to go? Sorry, I am still new to maven...
>
> Magnus
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: compiler errors after upgrade to gwt 2.8.0

[Juan Pablo Gardella]

Share the pom file.

On Thu, 16 Feb 2017 at 13:03 Magnus  wrote:

> Hi Thomas,
>
> I have created a new GWT WebApplication project using the eclipse plugin
> ("New -> Project -> Web Application Project"), and it compiles fine!
> As soon as I add my library project to the build path, the compilation
> error occurrs! So the error must be caused by this library project.
>
> The library project is a maven project with server-side and client-side
> (GWT) code. I upgraded it to GWT 2.8.0 by editing the pom.xml and executing
> "mvn package".
> Where should I look next?
>
> Thanks
>
> Magnus
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: compiler errors after upgrade to gwt 2.8.0

[Juan Pablo Gardella]

Also try mvn clean package

On Thu, 16 Feb 2017 at 13:17 Juan Pablo Gardella <
gardellajuanpa...@gmail.com> wrote:

> Share the pom file.
>
> On Thu, 16 Feb 2017 at 13:03 Magnus <alpineblas...@gmail.com> wrote:
>
> Hi Thomas,
>
> I have created a new GWT WebApplication project using the eclipse plugin
> ("New -> Project -> Web Application Project"), and it compiles fine!
> As soon as I add my library project to the build path, the compilation
> error occurrs! So the error must be caused by this library project.
>
> The library project is a maven project with server-side and client-side
> (GWT) code. I upgraded it to GWT 2.8.0 by editing the pom.xml and executing
> "mvn package".
> Where should I look next?
>
> Thanks
>
> Magnus
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>
>

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

Re: Which maven archetype for GWT applications?

[Juan Pablo Gardella]

It's only enabled in Project explorer view (in package explorer view
doesn't work)

[image: pasted1]


On Mon, 13 Feb 2017 at 14:15 Magnus  wrote:

> Hi Juan,
>
> thanks, but my package presentation is already set to "hierarchical".
> I would be glad if I could fix this with an eclipse setting...
>
> Magnus
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: JsInterop Question regarding execution in index.html

[Juan Pablo Gardella]

Check if this flag is activated  -[no]generateJsInteropExports Generate
exports for JsInterop purposes (defaults to OFF)


On Mon, 13 Feb 2017 at 14:01 Paul Mazzuca <paul.j.mazz...@gmail.com> wrote:

> Thanks for the quick reply.  This was my first inclination, which does not
> work.
>
> @JsMethod(namespace = JsPackage.GLOBAL, name = "handleOpenUrl")
>
> public void runMe(String url) {
>
> Window.alert("Success");
>
> }
>
>
>
> Perhaps, I am doing it wrong, but I had always thought the JsInterop wraps
> existing javascript. I am trying to declare a new javascript function in
> the global namespace so that a cordova plugin can call it.  handleOpenUrl
> does NOT exist, but I am responsible for creating it.
>
>
> Below js code does work inside my index.html.  I need to emulate that is
> GWT.
>
>
> function handleOpenURL(url) {
>
>  alert("received url: " + url);
>
> }
>
>
>
>
> On Mon, Feb 13, 2017 at 8:41 AM, Juan Pablo Gardella <
> gardellajuanpa...@gmail.com> wrote:
>
> You can use jsinterop
> <https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#heading=h.o7amqk9edhb9>
> .
>
> On Mon, 13 Feb 2017 at 13:24 Paul Mazzuca <paul.j.mazz...@gmail.com>
> wrote:
>
> I need to create a javascript function called "handleOpenUrl(url)" that
> will be called from a Cordova plugin (
> https://github.com/EddyVerbruggen/Custom-URL-scheme)  for a hand off from
> a mobile browser.  If I create the function inside my index.html, it is
> called successfully. The challenge is how do I move the execution into my
> GWT module?
>
> My ideas are...
>
> 1:  Somehow create a GWT method that is recognized in the global js
> namespace as "handleOpenUrl"?  I know method names get compiled out, so I
> am not sure how I would accomplish this.
>
> 2.  Leave the handleOpenUrl inside the index.html, but somehow call a GWT
> method from that?
>
> Any thoughts/ideas would be much appreciated.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/ycAylgf11zo/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit+unsubscr...@googlegroups.com.
>
>
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: JsInterop Question regarding execution in index.html

[Juan Pablo Gardella]

You can use jsinterop

.

On Mon, 13 Feb 2017 at 13:24 Paul Mazzuca  wrote:

> I need to create a javascript function called "handleOpenUrl(url)" that
> will be called from a Cordova plugin (
> https://github.com/EddyVerbruggen/Custom-URL-scheme)  for a hand off from
> a mobile browser.  If I create the function inside my index.html, it is
> called successfully. The challenge is how do I move the execution into my
> GWT module?
>
> My ideas are...
>
> 1:  Somehow create a GWT method that is recognized in the global js
> namespace as "handleOpenUrl"?  I know method names get compiled out, so I
> am not sure how I would accomplish this.
>
> 2.  Leave the handleOpenUrl inside the index.html, but somehow call a GWT
> method from that?
>
> Any thoughts/ideas would be much appreciated.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Native JsTypes with properties containing dashes

[Juan Pablo Gardella]

AFAIK is not possible. See
http://stackoverflow.com/questions/36867522/gwt-jsinterop-jstype-property-with-in-name

On Fri, 10 Feb 2017 at 06:23 Kenny  wrote:

> Hi,
>
> I am wrapping a js library, this library expects as a parameter for a
> function an object with properties that contain dashes.
>
> See an example here:
> http://dmitrybaranovskiy.github.io/raphael/reference.html#Element.animate
>
> How can I wrap this objects?
>
> @JsProperty(name = "fill-opacity") does not work.
>
> Regards
> Kenny
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GWT/Maven: No source code is available for type junit.framework.Test; did you forget to inherit a required module?

[Juan Pablo Gardella]

I believe you don't want compile junit classes.

 [ERROR] Line 26: No source code is available for type
junit.framework.Test; did you forget to inherit a required module?
 [ERROR] Line 28: No source code is available for type
junit.framework.TestSuite; did you forget to inherit a required module?
 [ERROR] Line 11: No source code is available for type
junit.framework.TestCase; did you forget to inherit a required module?


Remove them from the src path that you instructed GWT to process. See an
example at:
http://www.gwtproject.org/doc/latest/tutorial/create.html#components especially
at module xml, where you define the source path.

Regards,
Juan

On Wed, 25 Jan 2017 at 15:18 Magnus  wrote:

> Hello,
>
> I just moved a Java library, which uses GWT, into a Maven project.
> The Maven project was created like this:
>
> mvn archetype:generate -DarchetypeArtifactId=maven-archetype-quickstart
>
>
> Then, two code folders are created, main and test. I moved my library code
> into the main folder, and I created the mylib.gwt.xml file there.
> The test folder created by the Maven template contains a file
> AppTest.java, which uses junit.
>
> I imported the Maven project into eclipse and added it as a dependend
> project to an application project, which uses the library code.
>
> Now, when I try to compile the application, I get this error:
>
> Compiling module bcs.bcs
>Tracing compile failure path for type 'msw.lib.awi.AppTest'
>   [ERROR] Errors in
> 'file:/home/warker/dvl/prj/msw-lib-awi/src/test/java/msw/lib/awi/AppTest.java'
>  [ERROR] Line 26: No source code is available for type
> junit.framework.Test; did you forget to inherit a required module?
>  [ERROR] Line 28: No source code is available for type
> junit.framework.TestSuite; did you forget to inherit a required module?
>  [ERROR] Line 11: No source code is available for type
> junit.framework.TestCase; did you forget to inherit a required module?
>[ERROR] Aborting compile due to errors in some input files
>
>
> What's going on here? Why does the GWT compiler see the test folder,
> allthough there is no *.gwt-xml file referencing it?
> How can I resolve the problem?
>
> Thanks
> Magnus
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: styling Uibinder with external css using background image

[Juan Pablo Gardella]

Did you check
http://www.gwtproject.org/doc/latest/DevGuideClientBundle.html#ImageResource
?

On Thu, 5 Jan 2017 at 13:40 NewbieGwtUser  wrote:

> Hello everyone,
>
> Since two days, i'm struggling to find a tip for showing an image as a
> background within my uibinder file but I were unable to get it work.
>
> Actually I've a gwt-maven project with of course an src/main/java and
> src/main/resources structure. In this latter, I've made a public directory
> in which a set my images and external css files et defined a css class with
> a background-image.
>
> Then, when I called this style within a uibinder .ui.xml file, and tried
> to run it, the image used as the background fails to be loaded at the
> browser page.
>
> (error msg when I inspect with developer tool: Failed to load resource:
> the server responded with a status of 404 (Not Found))
>
> PS: I notice that external css file styles are already referenced in the
> module configuration file (with .gwt.xml extension) and work fine.
>
> Any idea will be very appreciated.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: /rpc/RemoteService : Unsupported major.minor version 51.0

[Juan Pablo Gardella]

See https://groups.google.com/forum/#!topic/Google-Web-Toolkit/5KrtRLw6gYo


On Sun, 1 Jan 2017 at 15:01 Lars  wrote:

> You could try to run the 2.7 gwt servlet jar in the production env and the
> 2.8 in the development env... this is for sure 100% not a supported
> solution, but it worked for me to get the 2.8 speed (in times until it was
> final) together with a 2.7 env :-)
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [gwt-contrib] GWT Plugin v3.0 and tbroyer maven integration ?

[Juan Pablo Gardella]

Did you check if it works by putting in Application.gwt.xml in
src/main/java instead of src/main/resources?

On Fri, 23 Dec 2016 at 06:48 stuckagain  wrote:

>
> Living behind a corporate firewall is hell as I cannot get my hands on the
> GWT plugin (I have a support case open for now 3+ months) unless I build it
> myself and produce a zip file of the eclipse plugin and somehow get it on
> my dev computer.
>
> I tried to build the 3.0-SNAPSHOT release on my computer at home but that
> one fails with:
>
> [ERROR] Failed to resolve target definition
> /Users/home/Projects/gwt-eclipse-plugin/eclipse/mars/gwt-eclipse-mars.target:
> Failed to load p2 metadata repository from location
> https://storage.googleapis.com/gcloud-for-eclipse-testing/: No repository
> found at https://storage.googleapis.com/gcloud-for-eclipse-testing. ->
> [Help 1]
>
> [ERROR]
>
> I tried to use the build on the brandon-release branch. Building went
> fine, I managed to install the plugin in my eclipse installation.
> But I can't get very far with starting the codeserver from eclipse.
>
> I am using the tbroyer maven plugin in a multi module maven project and I
> am using the module.gwt.xml approach that will generate the real gwt.xml
> file during build.
> When I try to launch the codeserver it just complains that it cannot find
> the Application.gwt.xml file in the classpath, even though the classpath is
> correct. So my guess that there is something wrong with the m2eclipse
> integration ? Since it does not appear to be generating the gwt.xml before
> launching as it should.
>
> How can I progress this painful exercise ?
> How can I get SNAPSHOT to properly build on the master branch ?
> How far does the tbroyer plugin support go ?
>
> --
> 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/54829475-70db-4e76-9a31-76d7c54cd9ac%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CA%2BkiFsfgTvUVy3vZVTcnTXGrGMd5sCA_cQD5xPGpuhBzWr8Vzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: IDEs, Dagger2 and annotationProcessorPaths

[Juan Pablo Gardella]

Check http://stackoverflow.com/a/35744298/741689


On Wed, 14 Dec 2016 at 20:03 Raphael André Bauer <
raphael.andre.ba...@gmail.com> wrote:

> Hi,
>
>
> I am just playing around with GWT 2.8 and Dagger 2.8. I added Dagger 2
> via the compiler plugin and the Dagger compiler to
> annotationProcessorPaths. When running mvn compile on the command line
> everything is fine. The generated DaggerMyAppComponent is generated
> properly and can be used in the source code. I can also use everything
> in GWT. Awesome.
>
> So far so good. Unfortunately neither Netbeans 8.2 nor Eclipse Neon
> recognize the generated Dagger files. I have those wonderful red lines
> below autogenerated components. And even though java and class files
> are present in the target directory - the IDEs do not want to
> recognize those classes. Clean compile in the IDEs does not seem to
> work.
>
> I am just wondering whether I am the only one with that problem, or
> how others solved that issue regarding the IDE integration.
>
>
> Thanks!
>
>
> Raphael
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GWT2.8 : org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration

[Juan Pablo Gardella]

Check
http://stackoverflow.com/questions/24805360/classcastexception-org-apache-xerces-parsers-xincludeawareparserconfiguration-c



On Fri, 2 Dec 2016 at 11:55 Peter Petranik  wrote:

> I have the Xerces library as dependency as part of gwt-dev.jar that is set
> by GWT SDK. I am not using the maven for a project. My dependencies are
> defined just by Eclipse in Project Settings (check the screenshot)
>
>
> 
>
>
>
> Am Donnerstag, 6. Oktober 2016 09:20:49 UTC+2 schrieb Darren Smith:
>
> Hi,
>
> I am developing a  that contains within it
>   - a vanilla HttpServlet
>   - a GWT RPC Service implementation (RemoteServiceServlet)
>
> I am currently using [GWT2.8rc1].
>
> Both servlets manipulate XML documents, and hence make calls to the
> following code
> DocumentBuilderFactory docfactory = DocumentBuilderFactory.newInstance();
> docfactory.setNamespaceAware(true);
>
> DocumentBuilder builder = docfactory.newDocumentBuilder();   // * problem
> here *
>
> When I launch the application in Eclipse, using the embedded
> Jetty container, the vanilla HttpServlet will fail at the line
> DocumentBuilder builder = docfactory.newDocumentBuilder();   // * problem
> here *
>
> The error message is
>   java.lang.ClassCastException:
> org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast
> to org.apache.xerces.xni.parser.XMLParserConfiguration
>
> Having done some research, this exception is typically raised when there
> are several Xerces implementations found on the classpath.
> (I can only see Xerces implementations in gwt-dev and in Eclipse as a
> plugin).
>
>
> For the GWT RPC Service implementation, launched as part of the same
> , the XML document processing works fine - i.e. no exception
> raised.
>
> If I comment out in the web.xml file the GWT-RPC servlet defintion, then
> the vanilla HttpServlet will perform the XML document processing without an
> exception.
>
>
> Has anyone encountered similar problems?
>
> Darren Smith.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GWT2.8 : org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration

[Juan Pablo Gardella]

Try by removing/exluding (if you have it in you r dependencies) xerces.

On Fri, 2 Dec 2016 at 07:10 Peter Petranik  wrote:

> Hi, I have a same problem after I updated my application from GWT 2.7 to
> 2.8
>
> That is the code that raises the exception:
> DocumentBuilderFactory.newInstance().newDocumentBuilder()
>
> And that is the exception:
> java.lang.ClassCastException:
> org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast
> to org.apache.xerces.xni.parser.XMLParserConfiguration
> at org.apache.xerces.parsers.DOMParser.(Unknown Source)
> at org.apache.xerces.parsers.DOMParser.(Unknown Source)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.(Unknown Source)
> at
> org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown
> Source)
> ...
>
> Has somebody already found some solution how to fix that ?
>
> Am Donnerstag, 6. Oktober 2016 09:20:49 UTC+2 schrieb Darren Smith:
>
> Hi,
>
> I am developing a  that contains within it
>   - a vanilla HttpServlet
>   - a GWT RPC Service implementation (RemoteServiceServlet)
>
> I am currently using [GWT2.8rc1].
>
> Both servlets manipulate XML documents, and hence make calls to the
> following code
> DocumentBuilderFactory docfactory = DocumentBuilderFactory.newInstance();
> docfactory.setNamespaceAware(true);
>
> DocumentBuilder builder = docfactory.newDocumentBuilder();   // * problem
> here *
>
> When I launch the application in Eclipse, using the embedded
> Jetty container, the vanilla HttpServlet will fail at the line
> DocumentBuilder builder = docfactory.newDocumentBuilder();   // * problem
> here *
>
> The error message is
>   java.lang.ClassCastException:
> org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast
> to org.apache.xerces.xni.parser.XMLParserConfiguration
>
> Having done some research, this exception is typically raised when there
> are several Xerces implementations found on the classpath.
> (I can only see Xerces implementations in gwt-dev and in Eclipse as a
> plugin).
>
>
> For the GWT RPC Service implementation, launched as part of the same
> , the XML document processing works fine - i.e. no exception
> raised.
>
> If I comment out in the web.xml file the GWT-RPC servlet defintion, then
> the vanilla HttpServlet will perform the XML document processing without an
> exception.
>
>
> Has anyone encountered similar problems?
>
> Darren Smith.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re:

[Juan Pablo Gardella]

Try by removing Xerces library. Check
http://stackoverflow.com/questions/14014989/java-lang-abstractmethoderror-org-apache-xerces-dom-elementimpl-gettextcontent

On Wed, 30 Nov 2016 at 15:48 Ed  wrote:

> Hi Group,
>
> Tried to update to GWT 2.8 Got some errors, so I reverted to GWT 2.7 and
> getting the following errors:
>
> How can I determine if it is my code or a library issue?
>
> I am beginning to believe it is a failing hard drive but dont know how to
> tell, hard drive checks do not show any issues.
>
> ERROR
>
> Compiling module com.CyberObjects.wrrw.WRRWWebMaterial
>[ERROR] An internal compiler exception occurred
> com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during
> visit.
> at
> com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:121)
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:296)
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128)
> at
> com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:67)
> at
> com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128)
> at
> com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse(JDeclarationStatement.java:49)
> at
> com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(JModVisitor.java:95)
> at
> com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(JModVisitor.java:351)
> at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:92)
> at
> com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:149)
> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:145)
> at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83)
> at
> com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
> at com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:600)
> at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:569)
> at
> com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381)
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293)
> at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285)
> at com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(UnifyAst.java:1505)
> at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:870)
> at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1305)
> at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1038)
> at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.precompile(JavaToJavaScriptCompiler.java:954)
> at
> com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptCompiler.precompile(MonolithicJavaToJavaScriptCompiler.java:303)
> at
> com.google.gwt.dev.jjs.JavaScriptCompiler.precompile(JavaScriptCompiler.java:38)
> at com.google.gwt.dev.Precompile.precompile(Precompile.java:286)
> at com.google.gwt.dev.Precompile.precompile(Precompile.java:229)
> at com.google.gwt.dev.Precompile.precompile(Precompile.java:145)
> at com.google.gwt.dev.Compiler.run(Compiler.java:206)
> at com.google.gwt.dev.Compiler.run(Compiler.java:158)
> at com.google.gwt.dev.Compiler$1.run(Compiler.java:120)
> 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:127)
> Caused by: java.lang.AbstractMethodError:
> org.apache.xerces.dom.ElementNSImpl.setUserData(Ljava/lang/String;Ljava/lang/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object;
> at
> com.google.gwt.uibinder.rebind.W3cDocumentBuilder.startElement(W3cDocumentBuilder.java:127)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
> Source)
> at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
> at
> 

Re: Where can I find a sample for multi-module GWT app built with maven?

[Juan Pablo Gardella]

Try to install last gwt eclipse plugin first:
http://gwt-plugins.github.io/documentation/

Regarding launchers:
http://eclipsesnippets.blogspot.com.ar/2007/07/tip-creating-and-sharing-launch.html
Basically, you have to create them.

Regards,
Juan


On Mon, 21 Nov 2016 at 16:27 vitrums <vitr...@gmail.com> wrote:

> Sorry, but I'm not sure where I can find these lines. Searched within my
> eclipse folder, but no match. Also, it looks like these settings are
>  global and may affect all other projects.
>
>
> On Monday, November 21, 2016 at 10:07:38 PM UTC+3, Juan Pablo Gardella
> wrote:
>
>
> Install GWT eclipse plugin and then use eclipse launchers to start them.
>
>
> *SDM launcher:*
>
> ...
>  value="com.google.gwt.dev.DevMode"/>
>  value="-war *YOURWRAR *-logLevel INFO -port auto -remoteUI
> ${gwt_remote_ui_server_port}:${unique_id} -codeServerPort 9997
> *ENTRYPOINTHERE* "/>
> ...
>
>
> Server launcher:
> (Execute maven goals)
>
> Regards,
> Juan
>
> On Mon, 21 Nov 2016 at 16:01 vitrums <vit...@gmail.com> wrote:
>
> Thank you. I tried it before, but I had a syntax error in that line
> (missed a "-" before a key).
>
> I wonder now though how to run this sample app within Eclipse with
> *gwt:devmode* goal on Jetty. Examining the modules with Project Explorer
> shows, that src/main/webapp is related to **-server* module and
> therefore, *mvn install* produces the target within this module. Hence,
> running mvn *gwt:devmode* on the project opens GWT Development Mode
> window but finds no startup URL:
>
> [WARN] No startup URLs supplied and no plausible ones found -- use
> -startupUrl
>
>
> On Monday, November 21, 2016 at 9:16:15 PM UTC+3, Juan Pablo Gardella
> wrote:
>
> Did you try?
>
> mvn archetype:generate \
>
> -DarchetypeCatalog=https://oss.sonatype.org/content/repositories/snapshots/ \
>-DarchetypeGroupId=net.ltgt.gwt.archetypes \
>-DarchetypeArtifactId=moduler-webapp \
>-DarchetypeVersion=1.0-SNAPSHOT
>
>
>
> On Mon, 21 Nov 2016 at 14:48 vitrums <vit...@gmail.com> wrote:
>
> In the latest GWT 2.8.0 distribution *webAppCreator *tool generates *pom.xml
> *for a sample project from
> *com\google\gwt\user\tools\templates\maven\pom.xmlsrc* located in
> *gwt-user.jar*. The *groupId* for *gwt-maven-plugin* is now set as
> *net.ltgt.gwt.maven*. According to
> https://tbroyer.github.io/gwt-maven-plugin/index.html this project
> disctincts itself from *Mojo's Maven Plugin for GWT*
> https://gwt-maven-plugin.github.io/gwt-maven-plugin/index.html. The
> provided documentation is very succinct compared to Mojo's; it says little
> if anything about multi-moduling (provides a link at
> https://github.com/tbroyer/gwt-maven-archetypes/, which I can't get my
> head around... simply how to use it). According to the site the latest
> update was made in Jan, while the Mojo's docs were updated in Oct. of this
> year. And I could find a ready to use example of multi-module GWT app with
> maven at https://github.com/steinsag/gwt-maven-example, which
> unfortunately uses *org.codehaus.mojo's gwt-maven-plugin*. May be I can
> adapt this solution to use *net.ltgt.gwt.maven **gwt-maven-plugin *somehow,
> or what should I do?
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
>
> To post to this group, send email to google-we...@googlegroups.com.
>
>
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-we...@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Where can I find a sample for multi-module GWT app built with maven?

[Juan Pablo Gardella]

Install GWT eclipse plugin and then use eclipse launchers to start them.


*SDM launcher:*

...


...


Server launcher:
(Execute maven goals)

Regards,
Juan

On Mon, 21 Nov 2016 at 16:01 vitrums <vitr...@gmail.com> wrote:

> Thank you. I tried it before, but I had a syntax error in that line
> (missed a "-" before a key).
>
> I wonder now though how to run this sample app within Eclipse with
> *gwt:devmode* goal on Jetty. Examining the modules with Project Explorer
> shows, that src/main/webapp is related to **-server* module and
> therefore, *mvn install* produces the target within this module. Hence,
> running mvn *gwt:devmode* on the project opens GWT Development Mode
> window but finds no startup URL:
>
> [WARN] No startup URLs supplied and no plausible ones found -- use
> -startupUrl
>
>
> On Monday, November 21, 2016 at 9:16:15 PM UTC+3, Juan Pablo Gardella
> wrote:
>
> Did you try?
>
> mvn archetype:generate \
>
> -DarchetypeCatalog=https://oss.sonatype.org/content/repositories/snapshots/ \
>-DarchetypeGroupId=net.ltgt.gwt.archetypes \
>-DarchetypeArtifactId=moduler-webapp \
>-DarchetypeVersion=1.0-SNAPSHOT
>
>
>
> On Mon, 21 Nov 2016 at 14:48 vitrums <vit...@gmail.com> wrote:
>
> In the latest GWT 2.8.0 distribution *webAppCreator *tool generates *pom.xml
> *for a sample project from
> *com\google\gwt\user\tools\templates\maven\pom.xmlsrc* located in
> *gwt-user.jar*. The *groupId* for *gwt-maven-plugin* is now set as
> *net.ltgt.gwt.maven*. According to
> https://tbroyer.github.io/gwt-maven-plugin/index.html this project
> disctincts itself from *Mojo's Maven Plugin for GWT*
> https://gwt-maven-plugin.github.io/gwt-maven-plugin/index.html. The
> provided documentation is very succinct compared to Mojo's; it says little
> if anything about multi-moduling (provides a link at
> https://github.com/tbroyer/gwt-maven-archetypes/, which I can't get my
> head around... simply how to use it). According to the site the latest
> update was made in Jan, while the Mojo's docs were updated in Oct. of this
> year. And I could find a ready to use example of multi-module GWT app with
> maven at https://github.com/steinsag/gwt-maven-example, which
> unfortunately uses *org.codehaus.mojo's gwt-maven-plugin*. May be I can
> adapt this solution to use *net.ltgt.gwt.maven **gwt-maven-plugin *somehow,
> or what should I do?
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
>
> To post to this group, send email to google-we...@googlegroups.com.
>
>
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Where can I find a sample for multi-module GWT app built with maven?

[Juan Pablo Gardella]

Did you try?

mvn archetype:generate \
   -DarchetypeCatalog=https://oss.sonatype.org/content/repositories/snapshots/ \
   -DarchetypeGroupId=net.ltgt.gwt.archetypes \
   -DarchetypeArtifactId=moduler-webapp \
   -DarchetypeVersion=1.0-SNAPSHOT



On Mon, 21 Nov 2016 at 14:48 vitrums  wrote:

> In the latest GWT 2.8.0 distribution *webAppCreator *tool generates *pom.xml
> *for a sample project from
> *com\google\gwt\user\tools\templates\maven\pom.xmlsrc* located in
> *gwt-user.jar*. The *groupId* for *gwt-maven-plugin* is now set as
> *net.ltgt.gwt.maven*. According to
> https://tbroyer.github.io/gwt-maven-plugin/index.html this project
> disctincts itself from *Mojo's Maven Plugin for GWT*
> https://gwt-maven-plugin.github.io/gwt-maven-plugin/index.html. The
> provided documentation is very succinct compared to Mojo's; it says little
> if anything about multi-moduling (provides a link at
> https://github.com/tbroyer/gwt-maven-archetypes/, which I can't get my
> head around... simply how to use it). According to the site the latest
> update was made in Jan, while the Mojo's docs were updated in Oct. of this
> year. And I could find a ready to use example of multi-module GWT app with
> maven at https://github.com/steinsag/gwt-maven-example, which
> unfortunately uses *org.codehaus.mojo's gwt-maven-plugin*. May be I can
> adapt this solution to use *net.ltgt.gwt.maven **gwt-maven-plugin *somehow,
> or what should I do?
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GWT 2.8.0 is not compatible with java6

[Juan Pablo Gardella]

Hi Marko,

I'm using GWT RPC, so it's required gwt-servlet in the WAR file. As it's
deployed in an old Jboss server with java6, by using retrolambda, it's
possible to use gwt-servlet 2.8 in the server.

Juan

On Fri, 4 Nov 2016 at 07:37 Thomas Broyer  wrote:

> With the exception of a few corner-cases, Java 6 source code is also Java
> 8 compliant; so the GWT Compiler should be able to process it even though
> it assumes Java 8 source code.
>
> But the question was about JVM requirements: gwt-servlet.jar is compiled
> as Java 7 bytecode in 2.8, so it requires a Java 7 JVM on your server; and
> similarly gwt-dev and gwt-user require a Java 7 JVM on your developers' and
> CI machines (and if you use GIN, because GWT will "internally" compile your
> sources to Java 8 bytecode and GIN will try to actually run that code,
> you'll need a Java 8 JVM)
> Retrolambda could possibly solve the issue of gwt-servlet at least,
> possibly also gwt-dev/gwt-user at compile-time.
>
>
> On Friday, November 4, 2016 at 11:25:46 AM UTC+1, Marko wrote:
>
> How can you use retrolambda for that? Isn't retrolambda transforming the
> compiled >>bytecode<>source code<< and not
> bytecode...
>
> Marko
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GWT 2.8.0 is not compatible with java6

[Juan Pablo Gardella]

Hi all,

A workaround to use gwt-2.8.0 in Java 6 is using retrololamda
<https://github.com/orfjackal/retrolambda>. Here how I configured it (using
maven), by adding a profile (here the gist
<https://gist.github.com/gardellajuanpablo/727d3b53e4e5a92e4068b272aa8b4fed#file-gwt28-usingjava6-xml-L1>
):


production


production





com.google.gwt
gwt-servlet
provided




${basedir}/src/env/production



org.apache.maven.plugins
maven-dependency-plugin
2.10


process-classes

unpack-dependencies


gwt-servlet
${project.build.directory}/classes






net.orfjackal.retrolambda
retrolambda-maven-plugin
2.3.0


process-classes

process-main
process-test




true
1.6





On Wed, 2 Nov 2016 at 10:53 Thomas Broyer <t.bro...@gmail.com> wrote:

>
>
> On Wednesday, November 2, 2016 at 2:38:38 PM UTC+1, Juan Pablo Gardella
> wrote:
>
> Hi all,
>
> At release notes is not mentioned that now it will support only java7.
>
>
> Good catch!
>
>
> I found tbroyer comment here:
> http://stackoverflow.com/questions/28879590/jdk-and-jre-minimal-versions-required-for-gwt-compiling-and-running
>
> Can be updated the release notes with that?
> http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0
>
> Let me know, I can create the pull request.
>
>
> Yes please, go ahead.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

GWT 2.8.0 is not compatible with java6

[Juan Pablo Gardella]

Hi all,

At release notes is not mentioned that now it will support only java7. I
found tbroyer comment here:
http://stackoverflow.com/questions/28879590/jdk-and-jre-minimal-versions-required-for-gwt-compiling-and-running

Can be updated the release notes with that?
http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0

Let me know, I can create the pull request.

Thanks,
Juan

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

Re: Issues calling RPC with GWT 2.8 RC1

[Juan Pablo Gardella]

Did you try 2.8 rc2? Which error are you seeing?

On Thu, 25 Aug 2016 at 07:16  wrote:

> Hi,
>
> From our application whenever we make RPC calls, we reach to our remote
> service and when we return any object successfully back, we get back in
> onFailure method of "AsyncCallback". The same code use to work with gwt 2.7
> and we are trying to migrate our application from 2.7 to 2.8 RC1. Does any
> one had similar issue with 2.8 RC1 ? Has something chnaged with the way RPC
> has to be made in 2.8 RC1 ? I'd appreciate any kind of help/suggestion.
>
> Thanks,
> Nishant Arya
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Package a GWT client project, no server code.

[Juan Pablo Gardella]

Maybe you can achieve that by using maven-assembly-plugin

El sáb., ago. 20, 2016 13:22, Mickael BARON 
escribió:

> Hi,
>
> With the GWT Maven plugin (
> https://gwt-maven-plugin.github.io/gwt-maven-plugin/), i can package my
> GWT application into a war file. But, if my GWT application contains only
> client layer (no server aspect), is there a solution to package to a
> classical web application (for example a zip file) ? In other words, no
> web.xml, no META-INF... only the generated GWT application files. I plan to
> use a Maven assembly to package my GWT application ?
>
> Any idea ?
>
> Mickael
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: 2.8.0 RC1 is here!

[Juan Pablo Gardella]

You could replace it with dagger2.

On Fri, 29 Jul 2016 at 06:51 Jens  wrote:

>
> the only blocking point for me now is GIN.
>>
>
> Why its blocking?
>
> -- 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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: FileUpload doesn't jumps in ChangeHandler

[Juan Pablo Gardella]

Check http://caniuse.com/#search=input and the notes related to fileupload.

On Wed, 20 Jul 2016 at 09:51 Daniel Kln  wrote:

> Hello together,
>
> i would like to know why after selecting a directory, the onChange method
> isn't triggered?
>
> Thank you very much for your help.
>
> Code:
>
> public class CenterPanel extends ScrollPanel {
>
> final FileUpload fileUpload = new FileUpload();
>
> public CenterPanel(final GoogleUploader gooUp) {
>
> fileUpload.getElement().setPropertyBoolean("webkitdirectory",
> true);
>
>
> Image upBack = new Image(Resources.INSTANCE.uploadBackground());
> this.getElement().setPropertyString("align", "left");
>
> upBack.addDoubleClickHandler(new DoubleClickHandler() {
>
> @Override
> public void onDoubleClick(DoubleClickEvent event) {
> // TODO Auto-generated method stub
>
>
> fileUpload.click();
> }
> });
>
> fileUpload.addChangeHandler(new ChangeHandler() {
>
> @Override
> public void onChange(ChangeEvent event) {
> // TODO Auto-generated method stub
>
> JavaScriptObject fileList = event.getNativeEvent().cast();
>
> gooUp.setFileList(getFiles(fileList));
> }
> });
>
> this.add(upBack);
> this.getElement().getStyle().setBackgroundColor("#DBDEE6");
> this.getElement().setAttribute("id", "idScrollPanel");
> this.setHeight("100%");
> this.setWidth("100%");
>
> }
>
> private native JsArray getFiles(JavaScriptObject e) /*-{
> var files = e.target.files;
> return files;
> }-*/;
> }
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Putnami Gradle plugin 0.4.0 for GWT

[Juan Pablo Gardella]

Thanks!!

On Fri, 8 Jul 2016 at 11:54 Fabien Dumay  wrote:

> Hi folks,
>
> The putnami gradle plugin 0.4.0 is released.
> If you love GTW and Gradle this plugin is made for you.
>
> - Making SDM super easy
> - Multi module support
> - Runs on jetty 9
>
> https://github.com/Putnami/putnami-gradle-plugin
>
> Enjoy.
>
> -- Fabien
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Any elegant approach to integrate Spring security with GWT RPC based application?

[Juan Pablo Gardella]

See
https://groups.google.com/forum/m/?fromgroups#!topic/google-web-toolkit/fkbowz5-5do
it's old but maybe ir is still useful for your needs

El sáb., jul. 2, 2016 7:52, Gilberto  escribió:

> Not the answer you would like to hear, but...
>
> In my humble opinion, the elegant solution would be not using GWT RPC at
> all. Go RESTful.
>
> For the annotation problem, I don't know if there's a way to escape...
> maybe you could try code generation (which usually also relies on
> annotations... so...).
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Closure compiler removal ?

[Juan Pablo Gardella]

Another question related to that. How can be integrated closure
optimization in the build after that?

On Fri, 10 Jun 2016 at 16:32 Hristo Stoyanov  wrote:

> According to this:
> https://gwt-review.googlesource.com/#/c/15110/
>
> The -XenableClosudeCompiler option will be removed from GWT 2.8. This
> impacts Cradle And Maven plugins. I also have 2 question:
> 1. Is specifying -optimte 9 good enough to be the only one left?
> 2. The reason for the removal states that it never worked with source
> maps, but source maps are only useful during development, when noone uses
> optimization?
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: JsInterop and Java collections?

[Juan Pablo Gardella]

Someone know what is the blocker on finishing elemental 2?

On Tue, 7 Jun 2016 at 14:03 Hristo Stoyanov  wrote:

> Here is another example
> 
> of project that could wait no longer for Elemental 2. As you can see,
> similar stuff, but incompatible. Let's hope Elemental 2 comes out soon
> enough to prevent "elemental hell" in GWT land :-)
>
>
> On Tuesday, June 7, 2016 at 2:02:03 AM UTC-7, Vassilis Virvilis wrote:
>
>> +1 for elemental 2.0
>>
>> One project that I know of is
>>
>> https://github.com/workingflows/gwt-jquery
>> that requires
>> https://github.com/workingflows/gwt-jscore
>> that re-implements Node for example
>> @JsType(isNative = true)
>> public class Node extends EventTarget {
>> public native void bind(String property, JsObject objects);
>> public native Element parentElement();
>> public native Node parentNode();
>> public native Node firstChild();
>> public native Node removeChild(Node child);
>> public native void appendChild(Object child);
>> }
>>
>> Its author Cristian Rinaldi explicitly states: "This project is an
>> abstraction of the key elements of HTML and JS functionality. This can be
>> replaced in the future by Elemental 2.0." in README.md
>>
>> jquery is a very basic js library. Lots and lots of js libraries depend
>> on it. I believe its adoption is a corner stone for jsinterop success
>> (although you can cut corners and create the wrappers only from the high
>> level js libraries your application actually needs).
>>
>> On the negative side I am somewhat worry of the danger to be confusing
>> for plain GWT users (like me). GWT lready has 2 element types (one
>> deprecated). A third one unavoidably will increase the confusion.
>>
>>
>> Vassilis
>>
> On Tue, Jun 7, 2016 at 3:03 AM, Hristo Stoyanov 
>> wrote:
>>
> Thanks Thomas,
>>> Yes, your are very close to what I am thinking! Note, that if such
>>> mapping cannot be "special-cased" with some jsinterop cleverness,  it could
>>> be refined by an additional @JsX annotation (or two).
>>>
>>> ... Other than that, releasing Elemental 2.0 is becoming an urgent
>>> matter, IMHO. I noticed at least 2 gwt frameworks that could not wait and
>>> started rolling out their custom jsinterop-enabled  basic DOM "stuff",
>>> which would otherwise belong to a proper GWT 2.8/Elemental 2 release. I
>>> also assume that Elemental 2 will include some of the  "jsinterop
>>> helper/utils" discussed in this forum.
>>>
>>>
>>> On Monday, June 6, 2016 at 3:58:53 PM UTC-7, Thomas Broyer wrote:



 On Monday, June 6, 2016 at 9:15:43 PM UTC+2, Hristo Stoyanov wrote:
>
> Kirrill,
> I did not suggest to *convert*, but *map*. That means that if/when a
> JSInter-oped class is exported into the JS Engine (let's say V8) , the JS
> developer will see plain old js arrays, so s/he can work with them as they
> have been for ages. When Java/JsInterop developers work with the same
> structure, they can chose to view it as java.util.ArrayList, java array or
> some other java.util.Collection, thus using familiar Java APIs. It is the
> same structure in the JS Engine memory, but viewed differently. But no
> conversion involved.
>

 Some of those might work, but not all.
 I.e. "seeing" a JS Array as a java.util.List might work, but not the
 reverse; at least not with any java.util.List, only the one implementing
 type(s) that directly map (@JsType(isNative=true)) to a JS Array. More
 precisely, that means using that specific JsType on setting (and on
 getting, though possibly JsInterop could special-case it; I think that's
 what you're asking for); specifically, a setter taking any java.util.List
 wouldn't work, as you could pass, say, a LinkedList, and GWT would be
 unable to simply "map" it to a JS Array: we're compiling to JS here,
 there's no boundary like with a plugin.
 Currently, you could use elemental.util.ArrayOf, and I believe there
 will be equivalents in due time (either GWT 2.8 proper, or Elemental 2).
 This is more or less what Jens and Vassilis were talking about already.

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

Re: GWT React preview release on Maven Central

[Juan Pablo Gardella]

Thanks for sharing!

On Fri, 13 May 2016 at 09:40 Paul Stockley  wrote:

> I have pushed preview versions of gwt-react, gwt-react-router and
> gwt-redux to Maven Central. Check out the documentation for details.
> https://github.com/GWTReact
>
> Soon I hope to have a Gradle build file to make it easy to try out the
> examples. I am just working around some issues with the Gradle gwt plugin
> and GWT 2.8
>
> My next priority is to finish the MobX integration and then work on
> stabilizing the interface towards a 1.0 release. Our company will start
> using gwt-react and gwt-mobx in a production application within the next 4
> months. I am sure this will flush out any issues relatively quickly.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: compilation error with 2.8.0-SNAPSHOT (guava problem)

[Juan Pablo Gardella]

20-SNAPSHOT

On Tue, 12 Apr 2016 at 14:48 Norbert Sándor 
wrote:

> Maybe someone can help which guava version is the "supported" for
> gwt-2.8.0-snapshot?
>
> Thanks,
> Norbi
>
>
> On Sunday, 10 April 2016 16:06:01 UTC+2, Norbert Sándor wrote:
>>
>> Hello,
>>
>> I use the latest gwt-2.8.0-snapshot + guava-20.0-snapshot.
>> When I perform GWT compilation in Eclipse (by directly calling the
>> Compiler from a launch config) everything works as expected.
>> But when I compile using gwt-maven-plugin, the following error is raised:
>>
>> [INFO][ERROR] Errors in
>> 'jar:file:/C:/Dev/m2-repo/com/google/guava/guava-gwt/20.0-SNAPSHOT/guava-gwt-20.0-SNAPSHOT.jar!/com/google/common/collect/Maps.java'
>> [INFO]   [ERROR] Line 2880: The method and(Predicate> super Map.Entry>, Predicate>) is
>> undefined for the type Predicates
>> [INFO]   [ERROR] Line 3134: The method and(Predicate> super Map.Entry>, Predicate>) is
>> undefined for the type Predicates
>> [INFO]Tracing compile failure path for type
>> 'com.google.common.collect.Maps'
>> [INFO]   [ERROR] Errors in
>> 'jar:file:/C:/Dev/m2-repo/com/google/guava/guava-gwt/20.0-SNAPSHOT/guava-gwt-20.0-SNAPSHOT.jar!/com/google/common/collect/Maps.java'
>> [INFO]  [ERROR] Line 2880: The method
>> and(Predicate>,
>> Predicate>) is undefined for the type
>> Predicates
>> [INFO]  [ERROR] Line 3134: The method
>> and(Predicate>,
>> Predicate>) is undefined for the type
>> Predicates
>> [INFO]   [ERROR] Errors in
>> 'jar:file:/C:/Dev/m2-repo/com/google/guava/guava-gwt/20.0-SNAPSHOT/guava-gwt-20.0-SNAPSHOT.jar!/com/google/common/collect/super/com/google/common/collect/ImmutableMap.java'
>> [INFO]  [ERROR] com.google.common.collect.ImmutableSetMultimap
>> cannot be resolved to a type
>> [INFO]   [ERROR] Errors in
>> 'jar:file:/C:/Dev/m2-repo/com/google/guava/guava-gwt/20.0-SNAPSHOT/guava-gwt-20.0-SNAPSHOT.jar!/com/google/common/collect/ForwardingMap.java'
>> [INFO]  [ERROR] com.google.common.collect.Maps.Values cannot be
>> resolved to a type
>> [INFO]   [ERROR] Errors in
>> 'jar:file:/C:/Dev/m2-repo/com/google/guava/guava-gwt/20.0-SNAPSHOT/guava-gwt-20.0-SNAPSHOT.jar!/com/google/common/collect/ImmutableSetMultimap.java'
>> [INFO]  [ERROR]
>> com.google.common.collect.ImmutableMultimap.Builder cannot be resolved to a
>> type
>> [INFO]   [ERROR] Errors in
>> 'jar:file:/C:/Dev/m2-repo/com/google/guava/guava-gwt/20.0-SNAPSHOT/guava-gwt-20.0-SNAPSHOT.jar!/com/google/common/collect/ImmutableMultimap.java'
>> [INFO]  [ERROR] com.google.common.collect.AbstractMultimap cannot
>> be resolved to a type
>> [INFO]   [ERROR] Errors in
>> 'jar:file:/C:/Dev/m2-repo/com/google/guava/guava-gwt/20.0-SNAPSHOT/guava-gwt-20.0-SNAPSHOT.jar!/com/google/common/collect/AbstractMultimap.java'
>> [INFO]  [ERROR] com.google.common.collect.Multimaps.Entries
>> cannot be resolved to a type
>>
>> Do you have any idea how can I fix it?
>>
>> Thanks.
>> BR,
>> Norbi
>>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GWT-2.8.0-SNAPSHOT and Gin

[Juan Pablo Gardella]

Thanks!

El vie, 1 de abril de 2016 18:31, Alexey Bykov  escribió:

> Ok I found an easy workaround. This commit
> 
> explains why JsException was created. So in order to fix this problem it is
> enough add following entry to gwt.xml:
>
>  value="com.google.gwt.core.client"/>
>
>
> Easy fix=)
>
> On Saturday, 2 April 2016 02:05:35 UTC+2, Alexey Bykov wrote:
>>
>> Seems that you right Thomas, GWT-2.8.0-SNAPSHOT emulates quite a few
>> classes from Java 8 compared to beta1 (whole java.util.function package!),
>> and one of them is a JsException which isn't present in Java 8.
>>
>> On Friday, 1 April 2016 14:07:12 UTC+2, Thomas Broyer wrote:
>>>
>>>
>>>
>>> On Friday, April 1, 2016 at 1:55:51 PM UTC+2, Jens wrote:

 Sounds like you are not the only one:
 https://groups.google.com/forum/#!topic/google-gin/ywh7d9s6GpA

>>>
>>> Looking quickly at the stacktrace, it could be a class from
>>> super-source: not found in the parent classloader so tentatively defined
>>> here from GWT's internal JDT-compiled classes.
>>> If that's the case, there are chances that it could be fixed by moving
>>> the class to another package (e.g. javaemul.internal).
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GWT React

[Juan Pablo Gardella]

Thanks for sharing!, worth to try it

On Thu, 24 Mar 2016 at 13:49 Paul Stockley  wrote:

> We currently have a large GWT application that we have been working on for
> the last 4 years. We use Uibinder and Widgets very
>
>  heavily, although we have our own Widget set and RPC mechanism. The
> application is being constantly expanded and realistically
>
> won’t be fully rewritten for 8-10 years. Given the news about J2CL not
> supporting widgets, I have been thinking about how we could
>
> migrate to a world without widgets on an incremental basis.
>
>
>
> In parallel, I have also being exploring writing native mobile apps. We
> tried the mobile web but it wasn’t great and we really needed
>
> hardware integration for NFC and total offline capabilities. Which brings
> us React. I found React Native and started researching
>
> and playing around. I have to say I am very impressed. In my mind it is a
> game changer. They are getting close to allowing one code
>
> base to support iOS, Android and the Web with only about 10-20% custom
> code for each platform.
>
>
>
> The more I played with React Native, the more I liked the React
> declarative model for defining UI’s. I started thinking that React
>
> would be ideal for incrementally embedding within an existing GWT
> application. Facebook designed it so they could incrementally
>
> role it out into their existing Web application. When GWT 2.8 beta came
> out, I wanted something to try the new JsInterop out on.
>
> React seemed like a good candidate. After a couple of weeks of
> experimenting, I have a working proof of concept for React. I
>
> have to say it was a real challenge and really pushed the capabilities of
> JsInterop. I had to do some javascript hacking to get it
>
> to work. My goal was to create an interface that was as close to
> JavaScript as possible. That way you could use the many React
>
> tutorials and apply them to writing GWT React code without some huge
> mental translation.
>
>
>
> I decided to try and port http://todomvc.com/examples/react/#/ to Java.
> The reason for this was so I could have a direct comparison
>
> between the Java and Javascript code. I have implemented enough of the
> React API to get this working. In addition, I also integrated
>
> a 3rd party React component called React Router (
> https://github.com/reactjs/react-router). This is pretty much the de
> facto standard
>
> for routing in the React world. This proved that I could consume React
> components written by other people. Overall I am pleased with
>
> how it turned out. I find the java version easier to follow, especially
> since the Prop types are explicit. It would be nice to support JSX
>
>  instead of the legacy createElement interface. However, it isn’t
> terrible. The Java version was 465 lines in total vs 419 for the original
>
> JavaScript code. If you take out the import statements which I don’t
> really count because the IDE creates them for you, the Java version
>
> was actually only 414 lines. You can take a look at the code here :
>
>
>
>
> https://drive.google.com/folderview?id=0Bxp8vLBG2ol3NjAtRmdjMDhlc0k=sharing
>
>
>
> At this point I am about 80% sure what I have created could become a
> viable production solution. The next steps I want to do are:
>
>
>
>1. Finish the API
>2. Test embedding Gwt React within an existing GWT Widget based
>application.
>3. Build an API for Redux (https://github.com/reactjs/redux) and React
>Redux (https://github.com/reactjs/react-redux) which is becoming the
>de facto standard for the MC in MVC. I will probably re-implement todomvc
>using this.
>
>
>
> If I don’t hit any roadblocks, I will either publish to Github or make the
> source publicly available. I haven’t made my mind up on which approach I
> will take.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: SuperDevMode

[Juan Pablo Gardella]

I think you are actually using an embedded jetty by using cfx.
On Mon, 21 Mar 2016 at 15:34 Jim Douglas <jdou...@basis.com> wrote:

> What about it?
>
>
> On Monday, March 21, 2016 at 2:29:30 PM UTC-7, Juan Pablo Gardella wrote:
>
>> What about /jetty-all-9.2.10.jar?
>>
>> On Mon, 21 Mar 2016 at 15:19 Jim Douglas <jdo...@basis.com> wrote:
>>
> Since DevMode dropped dead, I've just written it off and worked directly
>>> in JavaScript, adding debug logging as necessary to isolate problems.  It's
>>> not optimal, but it's workable.  I'm looking at SuperDevMode with GWT 2.8
>>> now, and I'm struggling.  The documentation (
>>> http://www.gwtproject.org/articles/superdevmode.html) suggests
>>> (possibly overly optimistically?) that it just works; is that theoretically
>>> true, or is it omitting crucial details?
>>>
>>> We do not use the builtin Jetty server; is SuperDevMode somehow bound to
>>> that older version of Jetty?  When I try to start it here, it dies
>>> immediately with this error:
>>>
>>> Launching:
>>> '/Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/jre/bin/java'
>>> '-Xmx1536m' '-Dbasis.BBjHome=/Users/jimdouglas/basis-dev/'
>>> '-Djava.util.logging.config.file=/Users/jimdouglas/workspace/BBj/logging.properties'
>>> '-Dfile.encoding=UTF-8' '-classpath'
>>> '/Users/jimdouglas/basis-dev/apps/aon/help/addonhelp.jar:/Users/jimdouglas/basis-dev/barista/sys/help/baristahelp.jar:/Users/jimdouglas/workspace/BBj/src:/Users/jimdouglas/workspace/BBj/.apt_generated:/Users/jimdouglas/workspace/ParserServiceAPI/src:/Users/jimdouglas/workspace/BBj/war/WEB-INF/classes:/Users/jimdouglas/workspace/BBj/jars/org.apache.jasper.glassfish-2.2.2.v201112011158.jar:/Users/jimdouglas/workspace/BBj/jars/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar:/Users/jimdouglas/workspace/BBj/jars/activation-1.1.jar:/Users/jimdouglas/workspace/BBj/jars/AppleJavaExtensions.jar:/Users/jimdouglas/workspace/BBj/jars/asm-all-5.0.3.jar:/Users/jimdouglas/workspace/BBj/jars/aws-java-sdk-1.10.18.jar:/Users/jimdouglas/workspace/BBj/jars/axis.jar:/Users/jimdouglas/workspace/BBj/jars/axis2-adb-1.6.2.jar:/Users/jimdouglas/workspace/BBj/jars/axis2-kernel-1.6.2.jar:/Users/jimdouglas/workspace/BBj/jars/bcel.jar:/Users/jimdouglas/workspace/BBj/jars/bcprov-jdk16-146.jar:/Users/jimdouglas/workspace/BBj/jars/charsetprovider.jar:/Users/jimdouglas/workspace/BBj/jars/comm.jar:/Users/jimdouglas/workspace/BBj/jars/commons-cli-1.2.jar:/Users/jimdouglas/workspace/BBj/jars/commons-fileupload-1.3.1.jar:/Users/jimdouglas/workspace/BBj/jars/commons-io-1.4.jar:/Users/jimdouglas/workspace/BBj/jars/config-1.3.0.jar:/Users/jimdouglas/workspace/BBj/jars/flexlm.jar:/Users/jimdouglas/workspace/BBj/jars/flexlmutil.jar:/Users/jimdouglas/workspace/BBj/jars/FontChooser-7.3.jar:/Users/jimdouglas/workspace/BBj/jars/gson-2.3.1.jar:/Users/jimdouglas/workspace/BBj/jars/guava-16.0.1.jar:/Users/jimdouglas/workspace/BBj/jars/hamcrest-core-1.3.jar:/Users/jimdouglas/workspace/BBj/jars/HelpAll.jar:/Users/jimdouglas/workspace/BBj/jars/InterFaxClient.jar:/Users/jimdouglas/workspace/BBj/jars/iText-2.1.7.jar:/Users/jimdouglas/workspace/BBj/jars/ihhelper-0.0.1.jar:/Users/jimdouglas/workspace/BBj/jars/jas.jar:/Users/jimdouglas/workspace/BBj/jars/jasperreports-javaflow-6.0.4.jar:/Users/jimdouglas/workspace/BBj/jars/jasmin.jar:/Users/jimdouglas/workspace/BBj/jars/java_cup.jar:/Users/jimdouglas/workspace/BBj/jars/jaxrpc-api.jar:/Users/jimdouglas/workspace/BBj/jars/jaxrpc-ri.jar:/Users/jimdouglas/workspace/BBj/jars/jcommon-1.0.23.jar:/Users/jimdouglas/workspace/BBj/jars/JDBCPooling-internal.jar:/Users/jimdouglas/workspace/BBj/jars/joda-time-2.8.2.jar:/Users/jimdouglas/workspace/BBj/jars/servlet-api-3.1.jar:/Users/jimdouglas/workspace/BBj/jars/jflex.jar:/Users/jimdouglas/workspace/BBj/jars/jfreechart-1.0.19.jar:/Users/jimdouglas/workspace/BBj/jars/junit-4.11.jar:/Users/jimdouglas/workspace/BBj/jars/lucene-analyzers-common-5.0.0.jar:/Users/jimdouglas/workspace/BBj/jars/lucene-core-5.0.0.jar:/Users/jimdouglas/workspace/BBj/jars/lucene-queryparser-5.0.0.jar:/Users/jimdouglas/workspace/BBj/jars/lucene-backward-codecs-5.0.0.jar:/Users/jimdouglas/workspace/BBj/jars/mail-1.4.jar:/Users/jimdouglas/workspace/BBj/jars/NetBeans.jar:/Users/jimdouglas/workspace/BBj/jars/outline.jar:/Users/jimdouglas/workspace/BBj/jars/PDFRenderer-0.9.1.jar:/Users/jimdouglas/workspace/BBj/jars/rfaxCOMM.jar:/Users/jimdouglas/workspace/BBj/jars/rfaxRXTX.jar:/Users/jimdouglas/workspace/BBj/jars/RXTXcomm.jar:/Users/jimdouglas/workspace/BBj/jars/skinlf.jar:/Users/jimdouglas/workspace/BBj/jars/ssce.jar:/Users/jimdouglas/workspace/BBj/jars/swingx-1.0.jar:/Users/jimdouglas/workspace/BBj/jars/TimingFramework.jar:/Users/jimdouglas/workspace/BBj/jars/unboundid-ldapsdk-se-2.3.6.jar:/Users/jimdougla

Re: SuperDevMode

[Juan Pablo Gardella]

What about /jetty-all-9.2.10.jar?

On Mon, 21 Mar 2016 at 15:19 Jim Douglas  wrote:

> Since DevMode dropped dead, I've just written it off and worked directly
> in JavaScript, adding debug logging as necessary to isolate problems.  It's
> not optimal, but it's workable.  I'm looking at SuperDevMode with GWT 2.8
> now, and I'm struggling.  The documentation (
> http://www.gwtproject.org/articles/superdevmode.html) suggests (possibly
> overly optimistically?) that it just works; is that theoretically true, or
> is it omitting crucial details?
>
> We do not use the builtin Jetty server; is SuperDevMode somehow bound to
> that older version of Jetty?  When I try to start it here, it dies
> immediately with this error:
>
> Launching:
> '/Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/jre/bin/java'
> '-Xmx1536m' '-Dbasis.BBjHome=/Users/jimdouglas/basis-dev/'
> '-Djava.util.logging.config.file=/Users/jimdouglas/workspace/BBj/logging.properties'
> '-Dfile.encoding=UTF-8' '-classpath'
> 

Re: GWT custom scrollIntoView() implementation

[Juan Pablo Gardella]

Hi Virviis,

Could you file a bug and the fix? It will be great to include in gwt 2.8.0

Thanks

On Tue, 26 Jan 2016 at 14:25 Vassilis Virvilis  wrote:

> Hi,
>
> I was using scrollIntoView() when I hit the bug.
>
> In pages of mine GWT.scrollIntoView() is working in all major browsers.
>
> In a foreign page GWTscrollIntoView() fails (does nothing) in chrome. It
> however works in IE and firefox.
>
> Looking at the implementation I found a custom implementation of
> scrollIntoView.
>
> I was expecting that GWT would call the native element.scrollIntoView().
>
> I changed my code to call the native scrollIntoView() via JSNI and it
> works in both pages in all browsers.
>
> So does anybody know why GWT 2.7 has a custom scrollIntoView()
> implementation?
>
>
> --
> Vassilis Virvilis
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

gwt 2.7.0 - superdevmode serialization is different than compiled serialization

[Juan Pablo Gardella]

Hi folks,

Do you know why guava multimap could be serialized with superdevmode? I
found a problem with a gwt compiled application but it didin't happen with
superdevmode. I serialized a multimap using gwt-rpc and it worked for
superdevmode, but no using the compiled application.

Any thought?

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

Re: Activities and Places - Enabling History to reflect an updated data item

[Juan Pablo Gardella]

I think you need to program it in the start() method in the activity.

On 5 January 2016 at 12:44, Paul Mazzuca  wrote:

> Let's say I have a view with a list of items. When I click on an item I go
> to a new Place and view with details about that item.  In this details
> view, I do some update to the item, then want to return back to the list
> view, but only using the back button on the browser.
>
> If the user clicks the back button on the browser, that would trigger a
> place change event (a History.back() call)  and would return me to the
> list, however, the item in the list would be the stale version of the item,
> rather than the new version I just updated.
>
> How can I pass the updated item to the list when only using the back
> button on the browser, and without reaching out to the server?
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Using MVP with GWT2.7

[Juan Pablo Gardella]

It's old, but check the comments at
http://wanderingcanadian.ca/2010/11/05/hello-mvp-with-gin/

On 5 January 2016 at 16:15, Richa  wrote:

> Thanks Troncoso.
> I get what you say, and agree that its not a very good approach.
> But my concern is, For a huge application having around 200 events . Will
> I have to write 200 Event handlers, 200 Event Classes and Event types ?
>
> On Tue, Jan 5, 2016 at 4:55 PM, N Troncoso 
> wrote:
>
>> You could technically do that, but you'd need some way to differentiate
>> between events; Maybe with an enum:
>>
>> public class MyEvent extends GwtEvent
>> {
>> public static enum EventTypes
>> {
>> THIS_EVENT,
>> THAT_EVENT;
>> };
>>
>> public interface Handler extends EventHandler
>> {
>> void onDispatch(MyEvent event);
>> }
>>
>> public static final GwtEvent.Type TYPE = new
>> GwtEvent.Type<>(); // NOSONAR
>>
>> private final EventTypes type;
>> public MyEvent(EventTypes type)
>> {
>> this.type = type;
>> }
>>
>> @Override
>> public GwtEvent.Type getAssociatedType()
>> {
>> return TYPE;
>> }
>>
>> public EventTypes getType()
>> {
>> return type;
>> }
>>
>> @Override
>> protected void dispatch(Handler handler)
>> {
>> handler.onDispatch(this);
>> }
>> }
>>
>> I don't think this is a very good approach, though, as you lose the
>> ability to pass specific parameters based on that particular kind of event.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "GWT Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/google-web-toolkit/l0aEL5fsAok/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GWT 2.8 Compiler Question for Streams

[Juan Pablo Gardella]

stream() method is not mentioned in
http://www.gwtproject.org/doc/latest/RefJreEmulation.html#Package_java_util.
Maybe this is the reason.

On 29 December 2015 at 12:22, Paul Mazzuca  wrote:

> Any reason why I would be receiving a compiler error in the code below?
>
>
> //compiles
>
> this.mybutton.addClickHandler(c -> *dosomething()*);
>
>
> //does not compile
> Arrays.asList("one", "two").stream();
>
>
> I am using the beta Maven release of GWT 2.8 with jdk 1.8.0_60  and am
> using super dev mode.
>
>
> This is either a compiler bug or a Generator has legitimately stopped
> creating these types.
> [INFO]  Compiling 1 permutation
> [INFO] Compiling permutation 0...
> [INFO] [ERROR] An internal compiler exception occurred
> [INFO] com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error
> during visit.
> [INFO] at
> com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:111)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:130)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:122)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
> [INFO] at
> com.google.gwt.dev.jjs.ast.JReturnStatement.traverse(JReturnStatement.java:40)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:146)
> [INFO] at
> com.google.gwt.dev.jjs.ast.JVisitor.acceptWithInsertRemove(JVisitor.java:168)
> [INFO] at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:92)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:127)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:139)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:135)
> [INFO] at
> com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:127)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:122)
> [INFO] at
> com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:730)
> [INFO] at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:722)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:146)
> [INFO] at
> com.google.gwt.dev.jjs.ast.JVisitor.acceptWithInsertRemoveImmutable(JVisitor.java:172)
> [INFO] at
> com.google.gwt.dev.jjs.ast.JClassType.traverse(JClassType.java:142)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:127)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:122)
> [INFO] at
> com.google.gwt.dev.jjs.ast.JProgram.visitModuleTypes(JProgram.java:1288)
> [INFO] at com.google.gwt.dev.jjs.ast.JProgram.traverse(JProgram.java:1253)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:127)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:122)
> [INFO] at
> com.google.gwt.dev.jjs.impl.ControlFlowRecorder.execImpl(ControlFlowRecorder.java:163)
> [INFO] at
> com.google.gwt.dev.jjs.impl.ControlFlowRecorder.exec(ControlFlowRecorder.java:46)
> [INFO] at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.maybeRecordReferencesAndControlFlow(JavaToJavaScriptCompiler.java:474)
> [INFO] at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:352)
> [INFO] at
> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:272)
> [INFO] at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:198)
> [INFO] at
> com.google.gwt.dev.ThreadedPermutationWorkerFactory$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFactory.java:50)
> [INFO] at
> com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(PermutationWorkerFactory.java:74)
> [INFO] at java.lang.Thread.run(Thread.java:745)
> [INFO] Caused by: java.lang.NullPointerException
> [INFO] at
> com.google.gwt.dev.jjs.ast.JMethod.getJsniSignature(JMethod.java:560)
> [INFO] at
> com.google.gwt.dev.jjs.impl.ControlFlowRecorder.computeName(ControlFlowRecorder.java:50)
> [INFO] at
> com.google.gwt.dev.jjs.impl.ControlFlowRecorder.processMethodCall(ControlFlowRecorder.java:195)
> [INFO] at
> com.google.gwt.dev.jjs.impl.ControlFlowRecorder.visit(ControlFlowRecorder.java:158)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.visit(JVisitor.java:683)
> [INFO] at
> com.google.gwt.dev.jjs.ast.JNewInstance.traverse(JNewInstance.java:73)
> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:127)
> [INFO] ... 32 more
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are 

Re: GWT 2.8 Compiler Question for Streams

[Juan Pablo Gardella]

I think it's not supported in GWT 2.8:
- https://groups.google.com/forum/#!topic/google-web-toolkit/SuLcOTeJkyo
- http://stackoverflow.com/questions/15693169/java-8-support-in-gwt

On 29 December 2015 at 12:30, Paul Mazzuca <paul.j.mazz...@gmail.com> wrote:

> That reference is for the "latest", which I am assuming is still for 2.7,
> not 2.8?
>
> On Tue, Dec 29, 2015 at 10:26 AM, Juan Pablo Gardella <
> gardellajuanpa...@gmail.com> wrote:
>
>> stream() method is not mentioned in
>> http://www.gwtproject.org/doc/latest/RefJreEmulation.html#Package_java_util.
>> Maybe this is the reason.
>>
>> On 29 December 2015 at 12:22, Paul Mazzuca <paul.j.mazz...@gmail.com>
>> wrote:
>>
>>> Any reason why I would be receiving a compiler error in the code below?
>>>
>>>
>>> //compiles
>>>
>>> this.mybutton.addClickHandler(c -> *dosomething()*);
>>>
>>>
>>> //does not compile
>>> Arrays.asList("one", "two").stream();
>>>
>>>
>>> I am using the beta Maven release of GWT 2.8 with jdk 1.8.0_60  and am
>>> using super dev mode.
>>>
>>>
>>> This is either a compiler bug or a Generator has legitimately stopped
>>> creating these types.
>>> [INFO]  Compiling 1 permutation
>>> [INFO] Compiling permutation 0...
>>> [INFO] [ERROR] An internal compiler exception occurred
>>> [INFO] com.google.gwt.dev.jjs.InternalCompilerException: Unexpected
>>> error during visit.
>>> [INFO] at
>>> com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:111)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:130)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:122)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:118)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.ast.JReturnStatement.traverse(JReturnStatement.java:40)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:146)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.ast.JVisitor.acceptWithInsertRemove(JVisitor.java:168)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:92)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:127)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:139)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:135)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:127)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:122)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:730)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:722)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:146)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.ast.JVisitor.acceptWithInsertRemoveImmutable(JVisitor.java:172)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.ast.JClassType.traverse(JClassType.java:142)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:127)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:122)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.ast.JProgram.visitModuleTypes(JProgram.java:1288)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.ast.JProgram.traverse(JProgram.java:1253)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:127)
>>> [INFO] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:122)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.impl.ControlFlowRecorder.execImpl(ControlFlowRecorder.java:163)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.impl.ControlFlowRecorder.exec(ControlFlowRecorder.java:46)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.maybeRecordReferencesAndControlFlow(JavaToJavaScriptCompiler.java:474)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:352)
>>> [INFO] at
>>> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:272)
>>> [INFO] at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:198)
>>> [INFO] at
>>> com.google.gwt.dev.ThreadedPermutationWorkerFactory$ThreadedPermutationWorker.compile(ThreadedPermutationWor

CellTable equivalent

[Juan Pablo Gardella]

Hi devs,

As GWT 3.0 will remove widgets, someone know if exists a CellTable
equivalence in JS libraries? CellTable and Datagrid are awesome components.

Juan

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

Re: [gwt-contrib] Re: GWT 2.8.0-beta1 available for testing

[Juan Pablo Gardella]

Hi contributors,

I've created a google doc  with full GWT 2.8.0
release notes. It's divided by features/components and links for each
commit. I didn't put reverted commits, and fixes over features like
JSInterop. Everyone can put comments. It could be added later at GWT
official documentation once gwt 2.8.0 is completed.

Juan

On 7 December 2015 at 11:15, István Horváth  wrote:

> ok, i have PR for this, i hope it fits Google's needs.
>
> 2015. december 7., hétfő 15:47:50 UTC+1 időpontban Julien Dramaix a
> következőt írta:
>>
>> Feel free to fill a patch for that :)
>>
>> On Mon, Dec 7, 2015 at 2:28 PM István Horváth  wrote:
>>
>>> it would nice to have if you update the release notes page with exact
>>> dates on all of the version on both the links and the linked details too.
>>>
>>> http://www.gwtproject.org/release-notes.html
>>>
>>>
>>> 2015. december 4., péntek 10:51:13 UTC+1 időpontban Daniel Kurka a
>>> következőt írta:

 Hi all,

 we just finished testing for GWT 2.8.0-beta1. You can either download
 it from goo.gl/62SeR5 or from maven central.

 Release notes can be found here
 
 .

 Please start testing and let us know about any issues you encounter by
 either discussion here or filing bugs on github
 .

 -Daniel

>>> --
>>> 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/06401611-3eeb-4647-9fca-69459939aa8d%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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/5ac770a2-db1c-4676-b167-8632289decae%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CA%2BkiFseLrH5LPYM%3DkmqBFNrjqJOuvq28ZC9vvpfiM6xcKxNAYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

GWT 2.8.0 release notes - not official

[Juan Pablo Gardella]

Hi contributors/users,

I've created a google doc  with full GWT 2.8.0
release notes. It's divided by features/components and links for each
commit. I didn't put reverted commits, and fixes over features like
JSInterop. Everyone can put comments. It could be added later at GWT
official documentation once gwt 2.8.0 is completed.

Juan

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

Re: [gwt-contrib] GWT 2.8.0-beta1 available for testing

[Juan Pablo Gardella]

It will be very useful to make gwt-servlet compatible with java 6

On 4 December 2015 at 17:41, Jens  wrote:

>
> Is it intentional/necessary that gwt-servlet.jar is compiled for Java 7
>> and not Java 6?
>>
>
> gwt-servlet.jar isn't really compiled, its just assembled. The build
> script compiles gwt-dev and gwt-user using Java 7 as minimum and then
> gwt-servlet.jar is created by pulling in a subset of already compiled
> classes of gwt-user and gwt-dev. That means gwt-servlet.jar also requires
> Java 7. So generally its intentional.
>
> Also as soon as we land Java 8 API emulations GWT will be compiled using
> Java 8 which would mean gwt-servlet.jar also requires Java 8. Its probably
> not possible to keep gwt-servlet.jar compatible to Java 7 because as soon
> as we add java.time emulation to GWT we probably also add GWT-RPC custom
> field serializers for Java 8 classes like LocalDate, etc.
>
> -- J.
>
> --
> 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/afbc2b40-5a48-4e6d-960e-e59d46a81936%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CA%2BkiFsfRoq70DtV%3DvMNc1PB4k6sOURtLJxeH5YzQ%3Du163VPdLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0 RC1

[Juan Pablo Gardella]

The https://github.com/gwtproject/gwt/issues/9074 was in master. Somebody
know how to check if it will be included in 2.8 release? the commit is
https://github.com/gwtproject/gwt/commit/dd215d81ce29db42b185ffa2f86f6af36076f3be


On 3 December 2015 at 11:06, Thomas Broyer  wrote:

> AFAICT, it's coming: http://www.gwtproject.org/release-notes.html
>
>
> On Thursday, December 3, 2015 at 5:15:19 PM UTC+1, Michael Joyner wrote:
>>
>> Would someone please post an RC that won't break overnight BEFORE y'all
>> start posting possible breaking changes?
>>
>>
>> On 12/03/2015 10:11 AM, Thomas Broyer wrote:
>>
>> FYI, we've merged back the change that splitted jsinterop annotations out
>> of gwt-user; it just failed to deploy for some reason (failed early this
>> time, so something has been deployed at all) but we might possibly have
>> broken the snapshots again (despite tests on two independent developer
>> machines). Watch out for the next snapshot update and keep us informed if
>> anything's broken.
>>
>> On Thursday, December 3, 2015 at 3:00:43 PM UTC+1, Evan Ruff wrote:
>>>
>>> I've been using the 2.8.0-SNAPSHOT artifact from the
>>> https://oss.sonatype.org/content/repositories/google-snapshots/ repo
>>> for a few weeks now. We had a minor hiccup the other day but now everything
>>> is back to running smoothly. Watch out for Guava incompatibility.
>>>
>>> E
>>>
>>> On Thursday, December 3, 2015 at 4:39:32 AM UTC-5, Norbert Sándor wrote:

 A month has passed... any news?

 On Thursday, 5 November 2015 19:49:05 UTC+1, steve Zara wrote:
>
> As 2.8.0 RC1 is out this week, would it be possible to say where this
> will be linked to on the GWT site?  I'm not a maven user, so a link to the
> zip would be helpful.
>
 --
>> You received this message because you are subscribed to the Google Groups
>> "GWT Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> Visit this group at http://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: SEO Google Crawlable experience ?

[Juan Pablo Gardella]

It will very useful if you write some article about that :)

On 11 November 2015 at 17:21, Ed  wrote:

> I implemented html5 pushState and works very well:
> In the backend I use apache http rewrite rules to dispatch all requests to
> the index.html.
> In the frontend added the  tag to the index.html to ensure the base
> path is correct as the url changes due to the pushState actions such that
> base path changes if the tag isn't used.
> In the frontend I use the native pushState and popState to replace the
> existing History mechanism.
> Have a look here at leuker.nl and see the url change while clicking
> around ...
> I am happy with the result. I just submitted the update sitemap to Google
> and let's see how many pages get indexed.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [gwt-contrib] GWT 2.8 Release

[Juan Pablo Gardella]

Great work! Thanks. Is there any release note to GWT 2.8?

On 23 October 2015 at 01:55, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> In the last few months, we had important progress on JsInterop and finally
> it looks like we will be able to start the release process for 2.8 in a few
> weeks. So if you believe a patch needs to be part of the RC release, this
> is a good time to engage.
>
> I know there will be questions about Java8 so here are some answers:
> Language features wise, we are feature complete for long time. However
> plenty of new APIs, most significantly streams, is not emulated. The
> release will only include the subset of the APIs that is contributed by the
> community so it is in the hands of open source contributors.
> We may also do a 2.8.x release with bug fixes that includes latest
> contributions to emulation.
>
> Let me know if you have any questions.
>
> Cheers.
>
> --
> 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/CAN%3DyUA3eb9YqQsxdZXHPtzo6uwyJnSDMcdTpfKj-B%2BRzpJ7pjw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CA%2BkiFscb-Kg8nvF4j0J%3DwA-Oba_GTb2fo7XpLDo_n4ibcEDktQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.