Re: Strange error with streams
Hi foal, We had kind of similar problems when implemented Stream support but I cannot reproduce it now in a simple test like https://gist.github.com/nordligulv/9dfa0ca5ccfed3def097aefc59ea1e32 Can I ask you to create simple maven project with these classes to reproduce it? On Tuesday, November 1, 2016 at 1:14:27 PM UTC+2, foal wrote: > > Simplified widget is in attachment. Mehod createButtons contains the the > problem code. > > Let me know if you need something else. > > Stas > > On Tuesday, November 1, 2016 at 11:13:41 AM UTC+1, Jens wrote: >> >> Use -style PRETTY as SDM parameter so that the JS code is more readable. >> >> Looks like a GWT bug either in the compiler because of method references >> or inside the Stream emulation. If you can provide a minimal, reproducible >> example then open a bug report. >> >> -- 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.
Re: Super Devmode Error
Hi Marteijn, It's probably that you have stale dependencies in your classpath. The issue is resolved in these discussions: https://groups.google.com/forum/#!topic/google-web-toolkit/-c4RR6oLr2o https://groups.google.com/forum/#!topic/google-web-toolkit/ATR3ZWcVrEs On Wednesday, October 26, 2016 at 12:02:38 PM UTC+3, Marteijn Nouwens wrote: > > Does anybody got an idea why this is happening. Complies fine and such but > when running recompile it gives an error. The code server starts fine. > > Any hint are really apprciated. > > Marteijn > > Error > > [INFO] Compile of permutations succeeded > [INFO] Compilation succeeded -- 44,004s > [INFO] Linking into > C:\Users\Nouwens\AppData\Local\Temp\gwt-codeserver-2011215494628222743.tmp\eu.future.earth.crm > .EmployeeGui\compile-2\war\employeegui; Writing extras to > C:\Users\Nouwens\AppData\Local\Temp\gwt-codeserver-20112154946 > 28222743.tmp\eu.future.earth.crm.EmployeeGui\compile-2\extras\employeegui > [INFO] [WARN] Can't write source map > 6620753AA4B9C5EDD1145CE4947CAB4D_sourceMap0.json > [INFO] java.lang.NullPointerException > [INFO] at > com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:101) > [INFO] at > com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:88) > [INFO] at > com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:78) > [INFO] at > com.google.gwt.thirdparty.debugging.sourcemap.SourceMapGeneratorV3.mergeMapSection(SourceMapGeneratorV3.java: > 311) > [INFO] at > com.google.gwt.core.linker.SymbolMapsLinker.link(SymbolMapsLinker.java:316) > [INFO] at > com.google.gwt.core.ext.linker.impl.StandardLinkerContext.invokeLinkForOnePermutation(StandardLinkerContext.j > ava:384) > [INFO] at com.google.gwt.dev.Link.finishPermutation(Link.java:483) > [INFO] at com.google.gwt.dev.Link.doSimulatedShardingLink(Link.java:445) > [INFO] at com.google.gwt.dev.Link.link(Link.java:178) > [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:244) > [INFO] at > com.google.gwt.dev.codeserver.Recompiler.doCompile(Recompiler.java:362) > [INFO] at > com.google.gwt.dev.codeserver.Recompiler.compile(Recompiler.java:175) > [INFO] at > com.google.gwt.dev.codeserver.Recompiler.recompile(Recompiler.java:134) > [INFO] at com.google.gwt.dev.codeserver.Outbox.recompile(Outbox.java:135) > [INFO] at > com.google.gwt.dev.codeserver.JobRunner.recompile(JobRunner.java:113) > [INFO] at > com.google.gwt.dev.codeserver.JobRunner.access$000(JobRunner.java:37) > [INFO] at com.google.gwt.dev.codeserver.JobRunner$2.run(JobRunner.java:90) > [INFO] at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [INFO] at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [INFO] at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [INFO] at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [INFO] at java.lang.Thread.run(Thread.java:745) > [INFO] Invoking Linker Export CompilationResult symbol maps > [INFO] [ERROR] Failed to link > [INFO] java.lang.NullPointerException > [INFO] at java.util.TreeMap.put(TreeMap.java:563) > [INFO] at java.util.TreeSet.add(TreeSet.java:255) > [INFO] at > com.google.gwt.thirdparty.guava.common.collect.ForwardingCollection.add(ForwardingCollection.java:84) > [INFO] at > com.google.gwt.core.ext.linker.TypeIndexedSet.add(TypeIndexedSet.java:101) > [INFO] at > com.google.gwt.core.ext.linker.ArtifactSet.add(ArtifactSet.java:42) > [INFO] at > com.google.gwt.core.linker.SymbolMapsLinker.link(SymbolMapsLinker.java:330) > [INFO] at > com.google.gwt.core.ext.linker.impl.StandardLinkerContext.invokeLinkForOnePermutation(StandardLinkerContext.j > ava:384) > [INFO] at com.google.gwt.dev.Link.finishPermutation(Link.java:483) > [INFO] at com.google.gwt.dev.Link.doSimulatedShardingLink(Link.java:445) > [INFO] at com.google.gwt.dev.Link.link(Link.java:178) > [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:244) > [INFO] at > com.google.gwt.dev.codeserver.Recompiler.doCompile(Recompiler.java:362) > [INFO] at > com.google.gwt.dev.codeserver.Recompiler.compile(Recompiler.java:175) > [INFO] at > com.google.gwt.dev.codeserver.Recompiler.recompile(Recompiler.java:134) > [INFO] at com.google.gwt.dev.codeserver.Outbox.recompile(Outbox.java:135) > [INFO] at > com.google.gwt.dev.codeserver.JobRunner.recompile(JobRunner.java:113) > [INFO] at > com.google.gwt.dev.codeserver.JobRunner.access$000(JobRunner.java:37) > [INFO] at com.google.gwt.dev.codeserver.JobRunner$2.run(JobRunner.java:90) > [INFO] at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [INFO] at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [INFO] at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142
Re: Emulating CompletableFuture with Promise
In this case I wanted 'new Promise', not 'Promise.resolve'. Thanks for spotting that out! I've updated my branch. On Tuesday, September 6, 2016 at 10:09:28 PM UTC+3, Ian Preston wrote: > > For another hint, I think you don't want the "new" before > "Promise.resolve" on line 88 of impl/JsPromise :-) > What the best way for me to report bugs to you? A PR? > -- You received this message because you are subscribed to the Google Groups "GWT 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: Emulating CompletableFuture with Promise
Sounds good. Thanks! On Tuesday, September 6, 2016 at 10:09:28 PM UTC+3, Ian Preston wrote: > > For another hint, I think you don't want the "new" before > "Promise.resolve" on line 88 of impl/JsPromise :-) > What the best way for me to report bugs to you? A PR? > -- You received this message because you are subscribed to the Google Groups "GWT 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: Emulating CompletableFuture with Promise
No reason for that. I had to implement the code from scratch and didnt pay
attention to the signatures.
Thanks for the hint!
On Tuesday, September 6, 2016 at 1:48:09 AM UTC+3, Ian Preston wrote:
>
> Thanks, Andrei. That looks great! Is there a reason you've changed the
> signatures on some of the CompletableFuture methods?
>
> E.g. in the JRE,
> public CompletableFuture thenApply(Function
> fn)
>
> has become
>
> public CompletionStage thenApply(Function
> fn)
>
>
> On Monday, 5 September 2016 09:47:10 UTC+1, Andrei Korzhevskii wrote:
>>
>> I guess you need to super-source this class so the gwt compiler could use
>> it.
>>
>> You can take a look at my initial CompletableFuture implementation here:
>>
>> https://github.com/nordligulv/gwt/tree/completable-future
>>
>> https://github.com/nordligulv/gwt/commit/ea70c5358bac3c939cb0c1628a58ccc462cd7423
>>
>> Feel free to use it but note that I haven't tested it properly yet.
>>
>>
>>
>> On Monday, September 5, 2016 at 3:28:27 AM UTC+3, Ian Preston wrote:
>>>
>>> I'm trying to emulate CompletableFuture by backing directly onto
>>> Promise, but when compiling it gives this error:
>>> "No source code is available for type
>>> java.util.concurrent.CompletableFuture"
>>> (it finds other JRE classes I've replaced fine)
>>>
>>> My source I'm including is below. Am I doing anything illegal?
>>>
>>> package java.util.concurrent;
>>>
>>> import com.google.gwt.user.client.*;
>>> import jsinterop.annotations.*;
>>>
>>> import java.util.function.*;
>>>
>>> @JsType(isNative=true, name = "Promise", namespace = JsPackage.GLOBAL)
>>> public class CompletableFuture implements CompletionStage {
>>>
>>> @JsMethod(name = "then")
>>> public native CompletableFuture thenApply(Function>> T,? extends U> fn);
>>>
>>> @JsMethod(name = "then")
>>> public native CompletableFuture thenAccept(Consumer
>>> action);
>>>
>>> @JsMethod(name = "then")
>>> public native CompletableFuture thenCompose(Function>> T, ? extends CompletionStage> fn);
>>>
>>> @JsMethod(name = "reject")
>>> public native boolean completeExceptionally(Throwable ex);
>>>
>>> @JsMethod(name = "resolve")
>>> public native boolean complete(T value);
>>>
>>> @JsMethod(name = "resolve")
>>> public static native CompletableFuture completedFuture(U
>>> value);
>>>
>>> @JsOverlay
>>> public T get() throws InterruptedException, ExecutionException {
>>> Window.alert("Calling synchronous get() on CompletableFuture is
>>> not possible in Javascript!");
>>> throw new IllegalStateException("Unimplemented!");
>>> }
>>> }
>>>
>>
--
You received this message because you are subscribed to the Google Groups "GWT
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: Emulating CompletableFuture with Promise
I guess you need to super-source this class so the gwt compiler could use
it.
You can take a look at my initial CompletableFuture implementation here:
https://github.com/nordligulv/gwt/tree/completable-future
https://github.com/nordligulv/gwt/commit/ea70c5358bac3c939cb0c1628a58ccc462cd7423
Feel free to use it but note that I haven't tested it properly yet.
On Monday, September 5, 2016 at 3:28:27 AM UTC+3, Ian Preston wrote:
>
> I'm trying to emulate CompletableFuture by backing directly onto Promise,
> but when compiling it gives this error:
> "No source code is available for type
> java.util.concurrent.CompletableFuture"
> (it finds other JRE classes I've replaced fine)
>
> My source I'm including is below. Am I doing anything illegal?
>
> package java.util.concurrent;
>
> import com.google.gwt.user.client.*;
> import jsinterop.annotations.*;
>
> import java.util.function.*;
>
> @JsType(isNative=true, name = "Promise", namespace = JsPackage.GLOBAL)
> public class CompletableFuture implements CompletionStage {
>
> @JsMethod(name = "then")
> public native CompletableFuture thenApply(Function extends U> fn);
>
> @JsMethod(name = "then")
> public native CompletableFuture thenAccept(Consumer
> action);
>
> @JsMethod(name = "then")
> public native CompletableFuture thenCompose(Function ? extends CompletionStage> fn);
>
> @JsMethod(name = "reject")
> public native boolean completeExceptionally(Throwable ex);
>
> @JsMethod(name = "resolve")
> public native boolean complete(T value);
>
> @JsMethod(name = "resolve")
> public static native CompletableFuture completedFuture(U value);
>
> @JsOverlay
> public T get() throws InterruptedException, ExecutionException {
> Window.alert("Calling synchronous get() on CompletableFuture is
> not possible in Javascript!");
> throw new IllegalStateException("Unimplemented!");
> }
> }
>
--
You received this message because you are subscribed to the Google Groups "GWT
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: NPE with 2.8.0 rc2, SDM, Errai
I dont think it's a gwt issue. I guess the issue will be resolved when errai will use gwt 2.8 final instead of gwt 2.8 beta On Friday, August 19, 2016 at 6:24:10 PM UTC+3, Alberto Mancini wrote: > > Yes, adding the dependency actually solves the problem, thanks. > Actually i cannot remove errai profile in the real project. > > In your opinion, is it an issue in gwt or errai dependencies ? > > Thanks again, >Alberto. > > > On Fri, Aug 19, 2016 at 3:49 PM Andrei Korzhevskii > wrote: > >> Yes, that's true. Some dependency hell is going on there. >> Commenting out the errai profile does not help but it helps if you just >> add gson 2.6.2 to your project as a dependency >> >> >> com.google.code.gson >> gson >> 2.6.2 >> >> >> >> >> On Friday, August 19, 2016 at 4:13:12 PM UTC+3, Seamus McMorrow wrote: >>> >>> I had a quick look at that sample project. >>> The errai profile which is activated by default at the bottom of your >>> pom.xml has a dependencyManagement section BOM import. >>> That is conflicting the versions for gson and some others, xerces. >>> >>> If you comment out the whole profile bit >>> >>> On Friday, 19 August 2016 13:42:27 UTC+1, Andrei Korzhevskii wrote: >>>> >>>> Ok, I've tracked down the problem. >>>> The problem is that gwt-dev somehow relies on gson 1.7.2 but should >>>> rely on 2.6.2. I dont know what the problem is. I hope Jens or Thomas can >>>> help with that. >>>> The problem was that gson 1.7.2 incorrectly parsed provided source map >>>> string and returned empty JsonObject which resulted in NPE. >>>> >>>> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ sourcemap --- >>>> [INFO] com.testcase:sourcemap:war:1.0-SNAPSHOT >>>> [INFO] +- com.google.gwt:gwt-user:jar:2.8.0-rc2:provided >>>> [INFO] | +- com.google.jsinterop:jsinterop-annotations:jar:1.0.0:provided >>>> [INFO] | +- >>>> com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0:provided >>>> [INFO] | +- javax.validation:validation-api:jar:1.0.0.GA:provided >>>> [INFO] | +- javax.validation:validation-api:jar:sources:1.0.0.GA:provided >>>> [INFO] | +- javax.servlet:javax.servlet-api:jar:3.1.0:provided >>>> [INFO] | \- org.w3c.css:sac:jar:1.3:provided >>>> [INFO] \- com.google.gwt:gwt-dev:jar:2.8.0-rc2:provided >>>> [INFO]+- com.google.code.gson:gson:jar:1.7.2:provided (version managed >>>> from 2.6.2) >>>> [INFO]+- org.ow2.asm:asm:jar:5.0.3:provided >>>> [INFO]+- org.ow2.asm:asm-util:jar:5.0.3:provided >>>> [INFO]| \- org.ow2.asm:asm-tree:jar:5.0.3:provided >>>> [INFO]| \- (org.ow2.asm:asm:jar:5.0.3:provided - omitted for >>>> duplicate) >>>> [INFO]+- org.ow2.asm:asm-commons:jar:5.0.3:provided >>>> [INFO]| \- (org.ow2.asm:asm-tree:jar:5.0.3:provided - omitted for >>>> duplicate) >>>> [INFO]+- colt:colt:jar:1.2.0:provided >>>> [INFO]+- ant:ant:jar:1.6.5:provided >>>> [INFO]+- commons-collections:commons-collections:jar:3.2.2:provided >>>> [INFO]+- commons-io:commons-io:jar:2.4:provided >>>> [INFO]+- com.ibm.icu:icu4j:jar:50.1.1:provided >>>> [INFO]+- tapestry:tapestry:jar:4.0.2:provided >>>> [INFO]+- net.sourceforge.htmlunit:htmlunit:jar:2.19:provided >>>> [INFO]| +- xalan:xalan:jar:2.7.1:provided (version managed from 2.7.2) >>>> [INFO]| | \- xalan:serializer:jar:2.7.1:provided >>>> [INFO]| | \- xml-apis:xml-apis:jar:1.4.01:provided (version >>>> managed from 1.3.04) >>>> [INFO]| +- >>>> (commons-collections:commons-collections:jar:3.2.2:provided - version >>>> managed from 3.2.1; omitted for duplicate) >>>> [INFO]| +- org.apache.commons:commons-lang3:jar:3.1:provided (version >>>> managed from 3.4) >>>> [INFO]| +- org.apache.httpcomponents:httpclient:jar:4.5:provided >>>> (version managed from 4.5.1) >>>> [INFO]| | +- org.apache.httpcomponents:httpcore:jar:4.4.1:provided >>>> [INFO]| | \- (commons-codec:commons-codec:jar:1.10:provided - >>>> version managed from 1.9; omitted for duplicate) >>>> [INFO]| +- org.apache.httpcomponents:httpmime:jar:4.5.1:provided >>>> [INFO]| | \- (org.apache.httpcomponents
Re: NPE with 2.8.0 rc2, SDM, Errai
Yes, that's true. Some dependency hell is going on there. Commenting out the errai profile does not help but it helps if you just add gson 2.6.2 to your project as a dependency com.google.code.gson gson 2.6.2 On Friday, August 19, 2016 at 4:13:12 PM UTC+3, Seamus McMorrow wrote: > > I had a quick look at that sample project. > The errai profile which is activated by default at the bottom of your > pom.xml has a dependencyManagement section BOM import. > That is conflicting the versions for gson and some others, xerces. > > If you comment out the whole profile bit > > On Friday, 19 August 2016 13:42:27 UTC+1, Andrei Korzhevskii wrote: >> >> Ok, I've tracked down the problem. >> The problem is that gwt-dev somehow relies on gson 1.7.2 but should rely >> on 2.6.2. I dont know what the problem is. I hope Jens or Thomas can help >> with that. >> The problem was that gson 1.7.2 incorrectly parsed provided source map >> string and returned empty JsonObject which resulted in NPE. >> >> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ sourcemap --- >> [INFO] com.testcase:sourcemap:war:1.0-SNAPSHOT >> [INFO] +- com.google.gwt:gwt-user:jar:2.8.0-rc2:provided >> [INFO] | +- com.google.jsinterop:jsinterop-annotations:jar:1.0.0:provided >> [INFO] | +- >> com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0:provided >> [INFO] | +- javax.validation:validation-api:jar:1.0.0.GA:provided >> [INFO] | +- javax.validation:validation-api:jar:sources:1.0.0.GA:provided >> [INFO] | +- javax.servlet:javax.servlet-api:jar:3.1.0:provided >> [INFO] | \- org.w3c.css:sac:jar:1.3:provided >> [INFO] \- com.google.gwt:gwt-dev:jar:2.8.0-rc2:provided >> [INFO]+- com.google.code.gson:gson:jar:1.7.2:provided (version managed >> from 2.6.2) >> [INFO]+- org.ow2.asm:asm:jar:5.0.3:provided >> [INFO]+- org.ow2.asm:asm-util:jar:5.0.3:provided >> [INFO]| \- org.ow2.asm:asm-tree:jar:5.0.3:provided >> [INFO]| \- (org.ow2.asm:asm:jar:5.0.3:provided - omitted for >> duplicate) >> [INFO]+- org.ow2.asm:asm-commons:jar:5.0.3:provided >> [INFO]| \- (org.ow2.asm:asm-tree:jar:5.0.3:provided - omitted for >> duplicate) >> [INFO]+- colt:colt:jar:1.2.0:provided >> [INFO]+- ant:ant:jar:1.6.5:provided >> [INFO]+- commons-collections:commons-collections:jar:3.2.2:provided >> [INFO]+- commons-io:commons-io:jar:2.4:provided >> [INFO]+- com.ibm.icu:icu4j:jar:50.1.1:provided >> [INFO]+- tapestry:tapestry:jar:4.0.2:provided >> [INFO]+- net.sourceforge.htmlunit:htmlunit:jar:2.19:provided >> [INFO]| +- xalan:xalan:jar:2.7.1:provided (version managed from 2.7.2) >> [INFO]| | \- xalan:serializer:jar:2.7.1:provided >> [INFO]| | \- xml-apis:xml-apis:jar:1.4.01:provided (version managed >> from 1.3.04) >> [INFO]| +- (commons-collections:commons-collections:jar:3.2.2:provided >> - version managed from 3.2.1; omitted for duplicate) >> [INFO]| +- org.apache.commons:commons-lang3:jar:3.1:provided (version >> managed from 3.4) >> [INFO]| +- org.apache.httpcomponents:httpclient:jar:4.5:provided >> (version managed from 4.5.1) >> [INFO]| | +- org.apache.httpcomponents:httpcore:jar:4.4.1:provided >> [INFO]| | \- (commons-codec:commons-codec:jar:1.10:provided - version >> managed from 1.9; omitted for duplicate) >> [INFO]| +- org.apache.httpcomponents:httpmime:jar:4.5.1:provided >> [INFO]| | \- (org.apache.httpcomponents:httpclient:jar:4.5:provided - >> version managed from 4.5.1; omitted for duplicate) >> [INFO]| +- commons-codec:commons-codec:jar:1.10:provided >> [INFO]| +- net.sourceforge.htmlunit:htmlunit-core-js:jar:2.17:provided >> [INFO]| +- xerces:xercesImpl:jar:2.11.0.SP4:provided (version managed >> from 2.11.0) >> [INFO]| +- net.sourceforge.nekohtml:nekohtml:jar:1.9.22:provided >> [INFO]| +- net.sourceforge.cssparser:cssparser:jar:0.9.18:provided >> [INFO]| | \- (org.w3c.css:sac:jar:1.3:provided - omitted for duplicate) >> [INFO]| +- (commons-io:commons-io:jar:2.4:provided - omitted for >> duplicate) >> [INFO]| +- commons-logging:commons-logging:jar:1.1.1:provided (version >> managed from 1.2) >> [INFO]| \- >> org.eclipse.jetty.websocket:websocket-client:jar:9.2.13.v20150730:provided >> [INFO]| +- >> (org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:provided - version >> managed from 9.2.13.v20150730; omitted for duplicate) >> [INFO]| +- (org.eclipse.jetty:jet
Re: NPE with 2.8.0 rc2, SDM, Errai
Ok, I've tracked down the problem. The problem is that gwt-dev somehow relies on gson 1.7.2 but should rely on 2.6.2. I dont know what the problem is. I hope Jens or Thomas can help with that. The problem was that gson 1.7.2 incorrectly parsed provided source map string and returned empty JsonObject which resulted in NPE. [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ sourcemap --- [INFO] com.testcase:sourcemap:war:1.0-SNAPSHOT [INFO] +- com.google.gwt:gwt-user:jar:2.8.0-rc2:provided [INFO] | +- com.google.jsinterop:jsinterop-annotations:jar:1.0.0:provided [INFO] | +- com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0:provided [INFO] | +- javax.validation:validation-api:jar:1.0.0.GA:provided [INFO] | +- javax.validation:validation-api:jar:sources:1.0.0.GA:provided [INFO] | +- javax.servlet:javax.servlet-api:jar:3.1.0:provided [INFO] | \- org.w3c.css:sac:jar:1.3:provided [INFO] \- com.google.gwt:gwt-dev:jar:2.8.0-rc2:provided [INFO]+- com.google.code.gson:gson:jar:1.7.2:provided (version managed from 2.6.2) [INFO]+- org.ow2.asm:asm:jar:5.0.3:provided [INFO]+- org.ow2.asm:asm-util:jar:5.0.3:provided [INFO]| \- org.ow2.asm:asm-tree:jar:5.0.3:provided [INFO]| \- (org.ow2.asm:asm:jar:5.0.3:provided - omitted for duplicate) [INFO]+- org.ow2.asm:asm-commons:jar:5.0.3:provided [INFO]| \- (org.ow2.asm:asm-tree:jar:5.0.3:provided - omitted for duplicate) [INFO]+- colt:colt:jar:1.2.0:provided [INFO]+- ant:ant:jar:1.6.5:provided [INFO]+- commons-collections:commons-collections:jar:3.2.2:provided [INFO]+- commons-io:commons-io:jar:2.4:provided [INFO]+- com.ibm.icu:icu4j:jar:50.1.1:provided [INFO]+- tapestry:tapestry:jar:4.0.2:provided [INFO]+- net.sourceforge.htmlunit:htmlunit:jar:2.19:provided [INFO]| +- xalan:xalan:jar:2.7.1:provided (version managed from 2.7.2) [INFO]| | \- xalan:serializer:jar:2.7.1:provided [INFO]| | \- xml-apis:xml-apis:jar:1.4.01:provided (version managed from 1.3.04) [INFO]| +- (commons-collections:commons-collections:jar:3.2.2:provided - version managed from 3.2.1; omitted for duplicate) [INFO]| +- org.apache.commons:commons-lang3:jar:3.1:provided (version managed from 3.4) [INFO]| +- org.apache.httpcomponents:httpclient:jar:4.5:provided (version managed from 4.5.1) [INFO]| | +- org.apache.httpcomponents:httpcore:jar:4.4.1:provided [INFO]| | \- (commons-codec:commons-codec:jar:1.10:provided - version managed from 1.9; omitted for duplicate) [INFO]| +- org.apache.httpcomponents:httpmime:jar:4.5.1:provided [INFO]| | \- (org.apache.httpcomponents:httpclient:jar:4.5:provided - version managed from 4.5.1; omitted for duplicate) [INFO]| +- commons-codec:commons-codec:jar:1.10:provided [INFO]| +- net.sourceforge.htmlunit:htmlunit-core-js:jar:2.17:provided [INFO]| +- xerces:xercesImpl:jar:2.11.0.SP4:provided (version managed from 2.11.0) [INFO]| +- net.sourceforge.nekohtml:nekohtml:jar:1.9.22:provided [INFO]| +- net.sourceforge.cssparser:cssparser:jar:0.9.18:provided [INFO]| | \- (org.w3c.css:sac:jar:1.3:provided - omitted for duplicate) [INFO]| +- (commons-io:commons-io:jar:2.4:provided - omitted for duplicate) [INFO]| +- commons-logging:commons-logging:jar:1.1.1:provided (version managed from 1.2) [INFO]| \- org.eclipse.jetty.websocket:websocket-client:jar:9.2.13.v20150730:provided [INFO]| +- (org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:provided - version managed from 9.2.13.v20150730; omitted for duplicate) [INFO]| +- (org.eclipse.jetty:jetty-io:jar:9.2.14.v20151106:provided - version managed from 9.2.13.v20150730; omitted for duplicate) [INFO]| \- org.eclipse.jetty.websocket:websocket-common:jar:9.2.13.v20150730:provided [INFO]|+- org.eclipse.jetty.websocket:websocket-api:jar:9.2.13.v20150730:provided [INFO]|+- (org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:provided - version managed from 9.2.13.v20150730; omitted for duplicate) [INFO]|\- (org.eclipse.jetty:jetty-io:jar:9.2.14.v20151106:provided - version managed from 9.2.13.v20150730; omitted for duplicate) [INFO]+- org.eclipse.jetty:jetty-webapp:jar:9.2.14.v20151106:provided [INFO]| +- org.eclipse.jetty:jetty-xml:jar:9.2.14.v20151106:provided [INFO]| | \- (org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:provided - version managed from 9.2.13.v20150730; omitted for duplicate) [INFO]| \- org.eclipse.jetty:jetty-servlet:jar:9.2.14.v20151106:provided [INFO]| \- org.eclipse.jetty:jetty-security:jar:9.2.14.v20151106:provided [INFO]|\- (org.eclipse.jetty:jetty-server:jar:9.2.14.v20151106:provided - omitted for duplicate) [INFO]+- org.eclipse.jetty:jetty-servlets:jar:9.2.14.v20151106:provided [INFO]| +- org.eclipse.jetty:jetty-continuation:jar:9.2.14.v20151106:provided [INFO]| +- org.eclipse.jetty:jetty-http:ja
Re: NPE with 2.8.0 rc2, SDM, Errai
It's hard to see what the problem actually is. I see you've created a test
project, can you share it? That would help to reproduce and track the error.
On Friday, August 19, 2016 at 1:06:56 PM UTC+3, Alberto Mancini wrote:
>
> Hello,
> we have still the same problem with SourceMaps.
> A teammate tracked down the problem and we found that the error appears if we
> depend on gwt-dev (rc1 or rc2) and errai.
>
> ---
> Job com.testcase.sourcemap.App_1_0
> [INFO] Linking into
> /var/folders/n8/8w8npfys46x90q0y9lqdxb0hgn/T/gwt-codeserver-4222675233479416644.tmp/com.testcase.sourcemap.App/compile-2/war/app;
>
> Writing extras to
> /var/folders/n8/8w8npfys46x90q0y9lqdxb0hgn/T/gwt-codeserver-4222675233479416644.tmp/com.testcase.sourcemap.App/compile-2/extras/app
> [INFO] [WARN] Can't write source map
> D84F40D38A264502877474A1394B6135_sourceMap0.json
> [INFO] java.lang.NullPointerException
> [INFO] at
> com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:101)
>
>
>
> Am I missing something trivial ?
> Should i file a bug on gwt-2.8.0-rc2 or errai beta2?
>
> Follows the sample pom.
>
> Thanks,
>Alberto.
>
>
>
>
> 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/xsd/maven-4.0.0.xsd";>
> 4.0.0
>
> com.testcase
> sourcemap
> 1.0-SNAPSHOT
> war
>
>
> 4.0.0.Beta2
> 2.8.0-rc2
>
>
>
>
> jboss
> JBoss Public Repo
>
> https://repository.jboss.org/nexus/content/groups/public
>
>
>
>
>
>
>
>
> com.google.gwt
> gwt-user
> ${gwt.version}
> provided
>
>
>
> com.google.gwt
> gwt-dev
> ${gwt.version}
> provided
>
>
>
>
>
>
> ${project.artifactId}
>
>
> src/main/java
>
>
>
>
>
> maven-compiler-plugin
> 3.5.1
>
> 1.8
> 1.8
>
>
>
> maven-clean-plugin
> 2.4.1
>
>
>
> ${basedir}
>
> src/gen/
> src/main/webapp/app/
>
> src/main/webapp/WEB-INF/deploy/
>
> src/main/webapp/WEB-INF/lib/
>
> src/main/webapp/WEB-INF/classes/**/*.*
>
> src/main/webapp/WEB-INF/classes/**/*
>
> src/main/webapp/WEB-INF/classes
> **/gwt-unitCache/**
> .errai/
>
>
>
>
>
>
> maven-war-plugin
> 2.6
>
>
> org.codehaus.mojo
> gwt-maven-plugin
> 2.8.0-rc1
>
>
>
> compile
>
>
>
>
> 0.0.0.0
> WARN
> true
> false
> src/gen/java
> src/gen/java
>
> ${project.basedir}/src/main/webapp
>
> ${project.basedir}/src/main/webapp
> /
> -Xmx2048m
> -XX:CompileThreshold=700
> true
>
>
>
> com.google.gwt
> gwt-user
> ${gwt.version}
>
>
> com.google.gwt
> gwt-dev
> ${gwt.version}
> compile
>
>
>
>
>
>
>
>
> errai
>
> true
>
>
>
>
> org.jboss.errai.bom
> errai-bom
> ${errai.version}
> pom
> import
>
>
>
>
>
>
>
Re: Problem with 2.8.0 rc1 SDM
Reading the stacktrace, I think the problem is in https://github.com/gwtproject/gwt/blob/master/dev/core/src/com/google/gwt/core/linker/SymbolMapsLinker.java#L282, looks like disk cache returns null there. Did you try to remove folder /var/folders/63/qxvnlkdn7yq2n689wbryx_ vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp and run compile again? On Friday, August 12, 2016 at 12:04:44 AM UTC+3, Alberto Mancini wrote: > > Hello, > in the attempt of porting an internal project from beta1 to rc1 we faced > an issue i do not understand how to debug. > > The project uses errai but my feeling is that the problem is not related > to it because similar projects with errai work without problems. > > Essentially SDM fails during the first compilation and the problem seems > in the generation of the source maps. > > The relevant error log follows. > > [INFO] GET /recompile/it.e.u.Application > [INFO]Job it.e.u.Application_1_0 > [INFO] starting job: it.e.u.Application_1_0 > [INFO] binding: user.agent=safari > [INFO] Compiling module it.e.u.Application > ... > > [INFO] Unification traversed 54946 fields and methods and 5256 > types. 5210 are considered part of the current module and 5210 had all of > their fields and methods traversed. > [INFO] Compiling 1 permutation > [INFO] Compiling permutation 0... > [INFO] Linking per-type JS with 5190 new/changed types. > [INFO] Source Maps Enabled > [INFO] Compile of permutations succeeded > [INFO] Compilation succeeded -- 35.850s > [INFO] Linking into > /var/folders/63/qxvnlkdn7yq2n689wbryx_vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp/it.e.u.Application/compile-2/war/it.e.u.Application; > Writing extras to > /var/folders/63/qxvnlkdn7yq2n689wbryx_vwrfzqfp/T/gwt-codeserver-2706361954965741673.tmp/it.e.u.Application/compile-2/extras/it.e.u.Application*[INFO] > [WARN] Can't write source map > CCA06A04193EDF5B35BDE836DF1FABBE_sourceMap0.json > [INFO] java.lang.NullPointerException* > [INFO]at > com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:101) > [INFO]at > com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:88) > [INFO]at > com.google.gwt.thirdparty.debugging.sourcemap.SourceMapConsumerV3.parse(SourceMapConsumerV3.java:78) > [INFO]at > com.google.gwt.thirdparty.debugging.sourcemap.SourceMapGeneratorV3.mergeMapSection(SourceMapGeneratorV3.java:311) > [INFO]at > com.google.gwt.core.linker.SymbolMapsLinker.link(SymbolMapsLinker.java:316) > [INFO]at > com.google.gwt.core.ext.linker.impl.StandardLinkerContext.invokeLinkForOnePermutation(StandardLinkerContext.java:384) > [INFO]at com.google.gwt.dev.Link.finishPermutation(Link.java:483) > [INFO]at > com.google.gwt.dev.Link.doSimulatedShardingLink(Link.java:445) > [INFO]at com.google.gwt.dev.Link.link(Link.java:178) > [INFO]at com.google.gwt.dev.Compiler.compile(Compiler.java:244) > [INFO]at > com.google.gwt.dev.codeserver.Recompiler.doCompile(Recompiler.java:362) > [INFO]at > com.google.gwt.dev.codeserver.Recompiler.compile(Recompiler.java:175) > [INFO]at > com.google.gwt.dev.codeserver.Recompiler.recompile(Recompiler.java:134) > [INFO]at > com.google.gwt.dev.codeserver.Outbox.recompile(Outbox.java:135) > [INFO]at > com.google.gwt.dev.codeserver.JobRunner.recompile(JobRunner.java:113) > [INFO]at > com.google.gwt.dev.codeserver.JobRunner.access$000(JobRunner.java:37) > [INFO]at > com.google.gwt.dev.codeserver.JobRunner$2.run(JobRunner.java:90) > [INFO]at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [INFO]at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [INFO]at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [INFO]at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [INFO]at java.lang.Thread.run(Thread.java:745) > [INFO] Invoking Linker Export CompilationResult symbol maps > [INFO] [ERROR] Failed to link > [INFO] java.lang.NullPointerException > [INFO]at java.util.TreeMap.put(TreeMap.java:563) > [INFO]at java.util.TreeSet.add(TreeSet.java:255) > [INFO]at > com.google.gwt.thirdparty.guava.common.collect.ForwardingCollection.add(ForwardingCollection.java:84) > [INFO]at > com.google.gwt.core.ext.linker.TypeIndexedSet.add(TypeIndexedSet.java:101) > [INFO]at > com.google.gwt.core.ext.linker.ArtifactSet.add(ArtifactSet.java:42) > [INFO]at > com.google.gwt.core.linker.SymbolMapsLinker.link(SymbolMapsLinker.java:330) > [INFO]at > com.google.gwt.core.ext.linker.impl.StandardLinkerContext.invokeLinkForOnePermutation(StandardLinkerContext.java:38
Re: AtomicReference
That was just a suggestion. Guava is involved in the way that it already provides gwt emulation for java.util.concurrent.* classes, e.g. it has emulation of AtomicBoolean, AtomicInteger and AtomicLong. It will be easier to merge your PR to Guava because they have more frequent release cycles than GWT has and since GWT 2.8 is about to hit rc1, there is a chance that your PR might get stalled. But again, that's just my suggestion. On Friday, June 17, 2016 at 1:23:59 PM UTC+3, Jaroslav Záruba wrote: > > I don't use Guava in this very project. > I am completely clueless about what you are suggesting. What I wish to add > to GWT is AtomicReference class (as simple as possible) and one or two > *.gwt.xml files. How would Guava be involved in that? > > Dne pátek 17. června 2016 11:43:27 UTC+2 Andrei Korzhevskii napsal(a): >> >> If you use Guava in your project, I'd send this PR to Guava since they >> have much frequent releases than GWT does and they accept PRs quite fast. >> They currently have atomic references for primitive values but not >> AtomicReference. >> >> >> On Friday, June 17, 2016 at 12:32:49 PM UTC+3, Jens wrote: >>> >>> I can't speak for an official maintainer but I would be fine with it to >>> increase code compatibility. Also the emulation code is pretty straight >>> forward. Its likely that GWT will contain a bit more java.util.concurrent.* >>> emulation in the future as long as it makes sense (e.g. CompletableFuture + >>> what Guava currently provides) >>> >>> But you can not do Github pull requests. You must sign a CLA and then >>> push your patch to Gerrit, GWT's code review tool. >>> >>> http://www.gwtproject.org/makinggwtbetter.html >>> https://gwt-review.googlesource.com >>> >>> -- 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.
Re: AtomicReference
If you use Guava in your project, I'd send this PR to Guava since they have much frequent releases than GWT does and they accept PRs quite fast. They currently have atomic references for primitive values but not AtomicReference. On Friday, June 17, 2016 at 12:32:49 PM UTC+3, Jens wrote: > > I can't speak for an official maintainer but I would be fine with it to > increase code compatibility. Also the emulation code is pretty straight > forward. Its likely that GWT will contain a bit more java.util.concurrent.* > emulation in the future as long as it makes sense (e.g. CompletableFuture + > what Guava currently provides) > > But you can not do Github pull requests. You must sign a CLA and then push > your patch to Gerrit, GWT's code review tool. > > http://www.gwtproject.org/makinggwtbetter.html > https://gwt-review.googlesource.com > > -- 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.
Re: Output ECMAScript 5 strict mode?
I used that linker to package gwt app as a chrome app/extension On Thursday, April 7, 2016 at 11:39:08 AM UTC+3, Alain wrote: > > Not sure what that will bring though .. > > On 7 April 2016 at 10:19, Andrei Korzhevskii > wrote: > >> No, no one showed any interest on this change. >> >> >> On Thursday, April 7, 2016 at 3:54:30 AM UTC+3, Michael Zhou wrote: >>> >>> Thanks. Do you plan to pick up that change? >>> >>> On Wednesday, April 6, 2016 at 5:38:37 PM UTC-4, Andrei Korzhevskii >>> wrote: >>>> >>>> Back in the days as I remember, I overrid linker for that so it wraps >>>> gwt code in aanonymous function call and inserts "use strict;" into it >>>> Something like that: https://gwt-review.googlesource.com/#/c/7710 >>>> >>>> On Thursday, April 7, 2016 at 12:25:33 AM UTC+3, Michael Zhou wrote: >>>>> >>>>> Bump. Anyone? >>>>> >>>>> On Sunday, March 27, 2016 at 4:01:05 PM UTC-4, Michael Zhou wrote: >>>>>> >>>>>> Is there a way to force GWT to output JS that is in ECMAScript 5 >>>>>> strict mode (ie. with the "use strict;" directive)? >>>>>> >>>>> -- >> You received this message because you are subscribed to the Google Groups >> "GWT 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. >> > > > > -- > > Alain Ekambi > > Co-Founder > > Ahomé Innovation Technologies > > http://www.ahome-it.com/ <http://ahome-it.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 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: Output ECMAScript 5 strict mode?
No, no one showed any interest on this change. On Thursday, April 7, 2016 at 3:54:30 AM UTC+3, Michael Zhou wrote: > > Thanks. Do you plan to pick up that change? > > On Wednesday, April 6, 2016 at 5:38:37 PM UTC-4, Andrei Korzhevskii wrote: >> >> Back in the days as I remember, I overrid linker for that so it wraps gwt >> code in aanonymous function call and inserts "use strict;" into it >> Something like that: https://gwt-review.googlesource.com/#/c/7710 >> >> On Thursday, April 7, 2016 at 12:25:33 AM UTC+3, Michael Zhou wrote: >>> >>> Bump. Anyone? >>> >>> On Sunday, March 27, 2016 at 4:01:05 PM UTC-4, Michael Zhou wrote: >>>> >>>> Is there a way to force GWT to output JS that is in ECMAScript 5 strict >>>> mode (ie. with the "use strict;" directive)? >>>> >>> -- You received this message because you are subscribed to the Google Groups "GWT 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: Output ECMAScript 5 strict mode?
Back in the days as I remember, I overrid linker for that so it wraps gwt code in aanonymous function call and inserts "use strict;" into it Something like that: https://gwt-review.googlesource.com/#/c/7710 On Thursday, April 7, 2016 at 12:25:33 AM UTC+3, Michael Zhou wrote: > > Bump. Anyone? > > On Sunday, March 27, 2016 at 4:01:05 PM UTC-4, Michael Zhou wrote: >> >> Is there a way to force GWT to output JS that is in ECMAScript 5 strict >> mode (ie. with the "use strict;" directive)? >> > -- You received this message because you are subscribed to the Google Groups "GWT 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: Is it possible for onModuleLoad to be called before DOMContentLoad?
Override CrossSiteIframeLinker's getJsWaitForBodyLoaded() method to return waitForBodyLoadedNull.js On Friday, December 12, 2014 11:20:17 PM UTC+3, pgi...@gmail.com wrote: > > The use case is when a GWT module is only exporting javascript functions. > > On a complex page, I have noticed a several second delay in the triggering > of onModuleLoad from when the selection script is actually downloaded. My > understanding > is that this seems to be a consequence of waiting for DOMContentLoad to > trigger. > > However, since this particular module is not going to be interacting with > the page at all, I would rather not pay the price of waiting if possible. > > Is there a way that onModuleLoad can be triggered earlier? > > If there are other things I should be considering in order to make this > use case performant, I would be interested in hearing about those as well. > > Thanks, > Pete Gieser > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Logging properties and classes
Thanks for response! Is it the only error you experience in gwt 2.7.0-snapshot? Would you mind posting an issue to https://code.google.com/p/google-web-toolkit/issues/list ? On Tuesday, September 30, 2014 2:11:18 PM UTC+4, Luca wrote: > > Sure, updated snapshots and "mvn install": > > [INFO] --- gwt-maven-plugin:2.7.0-SNAPSHOT:compile (default) @ --- > [INFO] auto discovered modules > [INFO] Loading inherited module 'x' > [INFO]Loading inherited module 'org.jboss.errai.common.ErraiCommon' > [INFO] Loading inherited module 'org.jboss.errai.common.Logging' > [INFO] [ERROR] Line 7: Property 'gwt.logging.popupHandler' not > found > > As you can see the property is not defined, I think that 2.7 should be > retro-compatible. > > > Il giorno martedì 30 settembre 2014 11:38:26 UTC+2, Andrei Korzhevskii ha > scritto: >> >> I don't think that removing FirebugLogHandler and NullLoggingPopup should >> be a problem for anyone, hardly anyone used that. >> Can you post exact error output here? >> >> >> On Tuesday, September 30, 2014 1:28:12 PM UTC+4, Luca wrote: >>> >>> Well, not really a bit... >>> >>> Being a 2.x I would expect not to have API compatibility broken, and >>> also if is not really a problem for my own code (some hours of work), I use >>> some external framework that I don't control. >>> >>> I think I cannot upgrade. >>> >>> Il giorno martedì 30 settembre 2014 11:18:30 UTC+2, Jens ha scritto: >>>> >>>> GWT 2.7 cleaned up logging a bit so you or any library that does more >>>> than just inheriting Logging.gwt.xml would need to check its configuration >>>> and maybe update it a bit when upgrading to 2.7. >>>> >>>> In general FirebugLogHandler and NullLoggingPopup classes have been >>>> removed and the corresponding GWT properties as well. >>>> >>>> -- J. >>>> >>> -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Logging properties and classes
I don't think that removing FirebugLogHandler and NullLoggingPopup should be a problem for anyone, hardly anyone used that. Can you post exact error output here? On Tuesday, September 30, 2014 1:28:12 PM UTC+4, Luca wrote: > > Well, not really a bit... > > Being a 2.x I would expect not to have API compatibility broken, and also > if is not really a problem for my own code (some hours of work), I use some > external framework that I don't control. > > I think I cannot upgrade. > > Il giorno martedì 30 settembre 2014 11:18:30 UTC+2, Jens ha scritto: >> >> GWT 2.7 cleaned up logging a bit so you or any library that does more >> than just inheriting Logging.gwt.xml would need to check its configuration >> and maybe update it a bit when upgrading to 2.7. >> >> In general FirebugLogHandler and NullLoggingPopup classes have been >> removed and the corresponding GWT properties as well. >> >> -- J. >> > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: JSNI function not called in Chrome
Just wrap your entire function with $entry, no function call.
public native void setCallDrillReport(ReportPanel rep)/*-{
$wnd.callReport = $entry(function (url) {
rep.@packageToMyClass.Classname::triggerDrillReport(Ljava/lang/String;)
(url);
});
}-*/;
On Friday, August 8, 2014 2:39:05 PM UTC+4, Rainer Sprünken wrote:
>
> Hi,
>
> I have developed a gwt application which uses jsni-function to trigger
> some Birt-Reports.
>
> JSNI function is definied as follows:
>
> public native void setCallDrillReport(ReportPanel rep)/*-{
> $wnd.callReport = function (url) {
> $entry(rep.@packageToMyClass.Classname::triggerDrillReport(Ljava/lang/String;)
>
> (url));
> };
>
> }-*/;
>
> The javascript call from Birt Report looks as follows:
>
> title="Report">title
>
> The call to the jsni method works well in all tested browsers but Google
> Chrome. Does anybody know where the problem could be?
>
> Thanks and regards Rainer
>
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
