(ab)Using GWT Generators for linting?
Hi I am trying to write a linter for checking typical GWT-RPC errors. I have a rough implementation that I piggy-back onto one of our Generators. https://gist.github.com/rhmoller/7aebcfa928ebfd190784 I feel it is a bit of a hack. Is there a better way to hook into the process? I considered using a pluggable annotation processor but then I would have to do something to find out which classes are candidates for GWT compilation. Can I abort GWT compilation when I detect an error. I tried throwing UnableToCompleteException but that only stops the generator, while the rest of GWT compilation process continues. This also causes the error messages from the linter to drown in the compiler output. /Rene -- 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: (ab)Using GWT Generators for linting?
I feel it is a bit of a hack. Is there a better way to hook into the process? GWT already checks it (although error messages might not be perfect all the time). And in case something isn't checked correctly, it should be implemented into GWT itself. With SuperDevMode being the new default DevMode in GWT 2.7 typical GWT-RPC errors should show up quickly as a real (incremental) compile is done on each page reload. Maybe you should just try GWT 2.7 SNAPSHOT and see if you still need a linter. -- 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.
Putnami Web Toolkit 1.1, a productive and powerful GWT Framework
Hi All, Putnami Web Toolkit 1.1 is released. It's time to use it. Thanks to PWT, GWT has never been so easy and powerfull. With our new annotation based injection features, reduce even more your code amount. PWT provides a full bunch of awesome features. You will be able to: - Reduce your code amount up to 3x - Properly separate the ui templates from the app logic - Bind complex Form / Table / List with only 2 Java lines - Validate your forms with javax.validation (JSR 303) - Multiplex your RPC with a invisible command Pattern - MVP usage simplification - Slit and scale your webapp without even knowing your doing it - Theme your webapp and enjoy Twitter's bootstrap widgets - Securise your views and widgets - Track your guest with google analytics - Index your ajax contents with the bot-indexing pluggin - and much more... Come to discover all these awesome stuff on http://pwt.putnami.org Published under LGPLv3 PWT is totaly free of use As usual, all feedbacks are welcome. You like, that's wonderfull! We'll be delighted if you : - Follow us on Twitter https://twitter.com/PutnamiTeam - Star us on GitHub https://github.com/Putnami/putnami-pwt - Join the user group https://groups.google.com/forum/#!forum/putnami-web-toolkit - Talk, blog and tweet about PWT Have fun, and see you on http://pwt.putnami.org -- 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: (ab)Using GWT Generators for linting?
GWT already checks it (although error messages might not be perfect all the time). And in case something isn't checked correctly, it should be implemented into GWT itself. That was also my expectation, but we sometimes run into serialization errors at run time even though GWT compilation completed. Often it is caused by simple cases like a transfer class without default constructor or a serializable interface in our core without an implementation in our core modules. (we have optional modules that are not deployed on all systems). I would like to catch those at compile time and break the build. No one sees the warnings in that deeply indented output. I guess the correct approach then is to look into SerializableTypeOracleBuilder and friends and see if I can find out why they slip through. Looking forward to 2.7. I will try to find some time to evaluate the snapshot build. -- 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: (ab)Using GWT Generators for linting?
One patch is still not committed: https://gwt-review.googlesource.com/#/c/7500/ -- 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.
SDM incremental compiles and generators
I noticed that SDM incremental compiles are always running gwt generators. I'm using gin and all my controllers have a reference to the gin injector. After the SDM gets to the injector it goes on to regenerate all my presenters and most dependencies. My minimal refresh time right now is 13s, When the actual changes seem to take less than a second to refresh (when I make them on a class that don't reference the gin injector). I made my generators incremental, but this didn't make an improvement. Is there anything I can to avoid this? -- 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.
Vraptor 3.5.2 + RequestFactory Gwt
Boa tarde Amigos, Estou integrando Vraptor com o GWT e tenho algumas duvidas em relação a forma de fazer a ligação através do RequestFactory. No RequestFactory tem a interface ServiceLocator que serve para fazer a ligação entre com o serviço do lado java. Já trabalhei com EBJ3 do lado do java onde fazemos a implementação usando o InitialContext.doLookup( java:global/ejb/ + clazz.getSimpleName() ). Gostaria de saber como posso fazer essa mesma chamada usando o VRaptor. Alguém poderia me ajudar? -- 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: Vraptor 3.5.2 + RequestFactory Gwt
AFAICT, VRaptor uses CDI, and CDI isn't that different from Guice; which means you should be able to use https://github.com/tbroyer/gwt-maven-archetypes/tree/master/guice-rf-activities/src/main/resources/archetype-resources/__rootArtifactId__-server/src/main/java as an inspiration (replace Guice's Injector with CDI's BeanManager). (BTW, thanks Google for the Portuguese → English translation) On Tuesday, October 14, 2014 3:28:59 PM UTC+2, Thiago borges martins wrote: Boa tarde Amigos, Estou integrando Vraptor com o GWT e tenho algumas duvidas em relação a forma de fazer a ligação através do RequestFactory. No RequestFactory tem a interface ServiceLocator que serve para fazer a ligação entre com o serviço do lado java. Já trabalhei com EBJ3 do lado do java onde fazemos a implementação usando o InitialContext.doLookup( java:global/ejb/ + clazz.getSimpleName() ). Gostaria de saber como posso fazer essa mesma chamada usando o VRaptor. Alguém poderia me ajudar? -- 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.
DTD factory class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from DTDDVFactory after using GWT's XML parser
I have an application which uses xml parser library - XOM ( www.xom.nu ). The parser works without any issues until I do parsing on GWT side via com.google.gwt.xml.client.XMLParser. After the parsing is done on GWT client side, when I try to do another parsing with XOM, I get the following exception: org.apache.xerces.impl.dv.DVFactoryException: *DTD factory **class org.apache.xerces.impl.dv.dtd.DTDDVFactoryImpl does not extend from DTDDVFactory.* at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown Source) at org.apache.xerces.impl.dv.DTDDVFactory.getInstance(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.createDatatypeValidatorFactory (Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.init(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.init(Unknown Source) at nu.xom.XML1_0Parser.init(Unknown Source) at nu.xom.Builder.findParser(Unknown Source) at nu.xom.Builder.init(Unknown Source) at nu.xom.Builder.init(Unknown Source) at XMLParser.tryParse(XMLParser.java:42) I have googled this issue and found different suggestions ( including http://stackoverflow.com/questions/4730103/xerces-error-org-apache-xerces-impl-dv-dtd-dtddvfactoryimpl) , however none of them helped me. What I found is that gwt-dev.jar and XOM they both use Xerces, so when gwt-dev.jar uses Xerces, the DTD class somehow changes and afterwards XOM's Xerces instance does not recognize the DVFactoryException as it is from another package. I also tried to use the java.endorsed.dirs but it didn't help. Has anyone had similar issue? If so, please give me hint what is going on here. Thanks, Petros -- 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: SDM incremental compiles and generators
It seems Gin kills the productivity during development, but giving to us cleaner code. Maybe both advantages are not possible right now. On 14 October 2014 09:52, Gal Dolber g...@dolber.com wrote: I noticed that SDM incremental compiles are always running gwt generators. I'm using gin and all my controllers have a reference to the gin injector. After the SDM gets to the injector it goes on to regenerate all my presenters and most dependencies. My minimal refresh time right now is 13s, When the actual changes seem to take less than a second to refresh (when I make them on a class that don't reference the gin injector). I made my generators incremental, but this didn't make an improvement. Is there anything I can to avoid this? -- 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. -- 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: Internet Explorer 11 - compatibility mode
We ran into the same problem. We took a different approach particular to the function no longer being supported. The DOM.gwt.xml switches user.agents with ie10 or less from StyleInjectorImpl to StyleInjectorImplIE. In the gwt.xml file we check if the function exists return typeof $doc.createStyleSheet === 'function'; If that function does not exist and the user.agent is ie10 or less switch StyleInjectorImpl to IeCompatibilityStyleInjectorImpl. IeCompatibilityStyleInjectorImpl is a class we created that just extends StyleInjectorImpl. This was required so that the DOM.gwt.xml doesn't find and try to switch StyleInjectorImpl. -- 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: SDM incremental compiles and generators
As a developer probably not. There are commits in GWT to improve recompile times when generators run that produce lots of output, e.g. https://gwt.googlesource.com/gwt/+/11b1cdcf38cacbccfb64e55bcd3a949b61528436 In our app we don't have references to the Ginjector except for onModuleLoad(). Recompiles vary from 3-15 seconds depending on the changes we make. Maybe Google's Dagger fork performs better with GWT 2.7 SDM, but Dagger 2.0 hasn't been released yet. -- 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: Internet Explorer 11 - compatibility mode
This should be fixed in GWT 2.7, see https://gwt.googlesource.com/gwt/+/master/user/src/com/google/gwt/useragent/rebind/UserAgentPropertyGenerator.java -- 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: SDM incremental compiles and generators
That looks promising! On Tue, Oct 14, 2014 at 4:11 PM, Jens jens.nehlme...@gmail.com wrote: As a developer probably not. There are commits in GWT to improve recompile times when generators run that produce lots of output, e.g. https://gwt.googlesource.com/gwt/+/11b1cdcf38cacbccfb64e55bcd3a949b61528436 In our app we don't have references to the Ginjector except for onModuleLoad(). Recompiles vary from 3-15 seconds depending on the changes we make. Maybe Google's Dagger fork performs better with GWT 2.7 SDM, but Dagger 2.0 hasn't been released yet. -- 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: SDM incremental compiles and generators
Oh, its an old change On Tue, Oct 14, 2014 at 4:22 PM, Gal Dolber g...@dolber.com wrote: That looks promising! On Tue, Oct 14, 2014 at 4:11 PM, Jens jens.nehlme...@gmail.com wrote: As a developer probably not. There are commits in GWT to improve recompile times when generators run that produce lots of output, e.g. https://gwt.googlesource.com/gwt/+/11b1cdcf38cacbccfb64e55bcd3a949b61528436 In our app we don't have references to the Ginjector except for onModuleLoad(). Recompiles vary from 3-15 seconds depending on the changes we make. Maybe Google's Dagger fork performs better with GWT 2.7 SDM, but Dagger 2.0 hasn't been released yet. -- 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: [gwt-contrib] GssParserException
Thanks Daniel. I've updated tools folder and now I can compile without problem. n1. Il giorno lunedì 13 ottobre 2014 10:09:31 UTC+2, Daniel Kurka ha scritto: Did you update your svn tools dir? On Mon, Oct 13, 2014 at 8:51 AM, Stefano Pulze stefano...@gmail.com javascript: wrote: Hi, I've a problem with GssParserException when try compile from GWT trunk version. I've download latest GWT trunk versione from the web and start to compiling with ant buildonly but the compiler says https://lh4.googleusercontent.com/-gwxn7hoHFaM/VDt1p-VleII/A00/BdQcGpLECXc/s1600/11.PNG Have I wrong something? 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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/c8619542-f837-413a-bd3a-ff1879a20615%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/c8619542-f837-413a-bd3a-ff1879a20615%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Google Germany GmbH *Dienerstr. 12* *80331 München* Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Graham Law, Katherine Stephens -- 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/bc56dbf0-ff32-4aa3-8d4a-f49451cca9a9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
