Re: Main Advantages of using GWT against other technology like [jsp,spring,javascript...]
Of course, the requirements of your particular application are the main gating factor for any choice and we don't know what the applicaiton is. But generally speaking, GWT is great for single-page applications; applications that run in the browser but act like desktop applications. Rather than loading page after page and keeping data in a database-backed session, your applicaition runs on a single page and keeps most of it's model in the client until it needs to persist it. The results is a more fluid user experience. JSP/Struts are great for creating traditional web pages with dynamic content. The user's session data (model) is kept in the server's database and when a page is requested, that model is used to render user-specific content into the page before it is returned to the browser. The advantage of this model is the central control the server provides. If your application is heavily content oriented, then serving it as a set of pages makes sense. If you are running a lot of business logic (beyond things like form validation) on the client, then you will want to use a language and tooling for that logic that supports good software engineering practices. The two things ares not mutually exclusive; you may use JSPs to write that basic DOM and a JSON model into the page and use logic in GWT to run the page. However, I would look to make a binary choice at first; I am delivering pages or am I writing a application; If you are delivering pages, traditional web technology works well. If you are writing an application, something like GWT will help you create a modern, browser delivered application. Ed On Friday, September 5, 2014 7:53:24 PM UTC-7, abdullah wrote: Hi, I am newbie to GWT and started developing my application using GWT.I would like to know what is the main advantages for going to GWT since we have lot of technology like JSP,Struts,..Can anyone give me suggestion on 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.
Re: SuperDevMode
Carlos, You've gotten to the point of launching the SuperDevMode codeserver. So http://localhost:9876/ is the code server. At that point, you don't need to have the SuperDevMode page open in the browser. Now you need to load the page the GWT app is hosted within.. I can often just go to my GWT project's war file and double-click the html file to load it into chrome, then choose the Dev Mode On bookmark to compile and run. If your page needs to talk to a server, then you'll want to launch from the server address (like the hosted Jetty in the video). In either case, once you have the SuperDevMode code server running, you then want to load your GWT host page then do the Dev Mode On compile. Ed On Sunday, January 19, 2014 3:16:32 PM UTC-8, Carlos Aguayo wrote: Hi, I don't seem to be able to get SuperDevMode to work. I'm following instructions from Brian's slides: https://docs.google.com/presentation/d/1DTWZ_06dQsTPhinIwzHSdoPMndRr92wpZoZWicK97YQ/edit?forcehl=1hl=en#slide=id.g25a114ce1_2056 I can get to normal devmode with ant devmode. But when I do ant superdevmode, things seem to compile and start up fine, I then go to http://localhost:9876/ using Chrome (I tried both 32 and canary), I see the welcome screen to drag the Dev mode on/off buttons, I drag them to the toolbar, the welcome page says that the hello project is available, I click on that link and then I click on the dev mode on bookmark and I get the Can't find any GWT Modules on this page.. What step am I missing or what am I doing wrong? Thanks! Carlos -- 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/groups/opt_out.
Re: GWTTestCase and CORS
Thank you Thomas. It looks like htmlunit 2.11 is the first version with CORS support. It should also have the GWT patches so I'll try your suggestion with that. I'll also take a look at phantomjs. Thanks again. Ed On Friday, June 28, 2013 1:12:18 AM UTC-7, Thomas Broyer wrote: On Friday, June 28, 2013 2:22:36 AM UTC+2, emurmur wrote: I'm writing a test case that involves a cross-origin call and htmlunit chokes on it. The code works in real browsers. Recent versions of htmlunit seem to support CORS (based on commit comments). How do I find what version of htmlunit is bundled with GWT and is there a way to upgrade it? Thanks. All the dependencies can be found in http://google-web-toolkit.googlecode.com/svn/tools/ (see http://www.gwtproject.org/makinggwtbetter.html#compiling), and as you can see in https://gwt.googlesource.com/gwt/+/master/dev/build.xml, GWT currently depends on HtmlUnit 2.9 (and as you can see in http://google-web-toolkit.googlecode.com/svn/tools/lib/htmlunit/htmlunit-2.9/ it's actually a patched version). Apparently, we could update to 2.10 with no breakage (and 2.10 includes all patches applied to the 2.9 for GWT), at least GWT compiles against 2.10 but I haven't heavily tested it (yet). I haven't tried with more recent versions. I think you can try it out by putting HtmlUnit 2.10 (and its dependencies) before gwt-dev.jar in your classpath (i.e. without rebuilding gwt-dev). You could also try using PhantomJS instead of HtmlUnit: https://github.com/neothemachine/gwt-phantomjs-junit-runstyle -- 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/groups/opt_out.
Re: GWTTestCase and CORS
I added htmlunit 2.12 to the run configuration's classpath, but my test still fails on an origin error. Jun 28, 2013 1:57:03 PM com.gargoylesoftware.htmlunit.javascript.StrictErrorReporter runtimeError SEVERE: runtimeError: message=[Access to restricted URI denied] sourceName=[injected script] line=[85] lineSource=[null] lineOffset=[0] So now I'm wondering if htmlunit is configured to emulate a non-CORS browser. I'll look more into that; If there are any htmlunit gurus out there that know exactly how to do that, it would be great. Thanks. Ed On Friday, June 28, 2013 12:45:15 PM UTC-7, emurmur wrote: Thank you Thomas. It looks like htmlunit 2.11 is the first version with CORS support. It should also have the GWT patches so I'll try your suggestion with that. I'll also take a look at phantomjs. Thanks again. Ed On Friday, June 28, 2013 1:12:18 AM UTC-7, Thomas Broyer wrote: On Friday, June 28, 2013 2:22:36 AM UTC+2, emurmur wrote: I'm writing a test case that involves a cross-origin call and htmlunit chokes on it. The code works in real browsers. Recent versions of htmlunit seem to support CORS (based on commit comments). How do I find what version of htmlunit is bundled with GWT and is there a way to upgrade it? Thanks. All the dependencies can be found in http://google-web-toolkit.googlecode.com/svn/tools/ (see http://www.gwtproject.org/makinggwtbetter.html#compiling), and as you can see in https://gwt.googlesource.com/gwt/+/master/dev/build.xml, GWT currently depends on HtmlUnit 2.9 (and as you can see in http://google-web-toolkit.googlecode.com/svn/tools/lib/htmlunit/htmlunit-2.9/ it's actually a patched version). Apparently, we could update to 2.10 with no breakage (and 2.10 includes all patches applied to the 2.9 for GWT), at least GWT compiles against 2.10 but I haven't heavily tested it (yet). I haven't tried with more recent versions. I think you can try it out by putting HtmlUnit 2.10 (and its dependencies) before gwt-dev.jar in your classpath (i.e. without rebuilding gwt-dev). You could also try using PhantomJS instead of HtmlUnit: https://github.com/neothemachine/gwt-phantomjs-junit-runstyle -- 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/groups/opt_out.
Re: GWTTestCase and CORS
It appears that older BrowserVersion identifiers have been removed from 2.11 and above and this breaks the GWTTestCase configuration code. I think it will need a patch to make this work. Ed On Friday, June 28, 2013 2:23:27 PM UTC-7, emurmur wrote: I added htmlunit 2.12 to the run configuration's classpath, but my test still fails on an origin error. Jun 28, 2013 1:57:03 PM com.gargoylesoftware.htmlunit.javascript.StrictErrorReporter runtimeError SEVERE: runtimeError: message=[Access to restricted URI denied] sourceName=[injected script] line=[85] lineSource=[null] lineOffset=[0] So now I'm wondering if htmlunit is configured to emulate a non-CORS browser. I'll look more into that; If there are any htmlunit gurus out there that know exactly how to do that, it would be great. Thanks. Ed On Friday, June 28, 2013 12:45:15 PM UTC-7, emurmur wrote: Thank you Thomas. It looks like htmlunit 2.11 is the first version with CORS support. It should also have the GWT patches so I'll try your suggestion with that. I'll also take a look at phantomjs. Thanks again. Ed On Friday, June 28, 2013 1:12:18 AM UTC-7, Thomas Broyer wrote: On Friday, June 28, 2013 2:22:36 AM UTC+2, emurmur wrote: I'm writing a test case that involves a cross-origin call and htmlunit chokes on it. The code works in real browsers. Recent versions of htmlunit seem to support CORS (based on commit comments). How do I find what version of htmlunit is bundled with GWT and is there a way to upgrade it? Thanks. All the dependencies can be found in http://google-web-toolkit.googlecode.com/svn/tools/ (see http://www.gwtproject.org/makinggwtbetter.html#compiling), and as you can see in https://gwt.googlesource.com/gwt/+/master/dev/build.xml, GWT currently depends on HtmlUnit 2.9 (and as you can see in http://google-web-toolkit.googlecode.com/svn/tools/lib/htmlunit/htmlunit-2.9/ it's actually a patched version). Apparently, we could update to 2.10 with no breakage (and 2.10 includes all patches applied to the 2.9 for GWT), at least GWT compiles against 2.10 but I haven't heavily tested it (yet). I haven't tried with more recent versions. I think you can try it out by putting HtmlUnit 2.10 (and its dependencies) before gwt-dev.jar in your classpath (i.e. without rebuilding gwt-dev). You could also try using PhantomJS instead of HtmlUnit: https://github.com/neothemachine/gwt-phantomjs-junit-runstyle -- 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/groups/opt_out.
GWTTestCase and CORS
I'm writing a test case that involves a cross-origin call and htmlunit chokes on it. The code works in real browsers. Recent versions of htmlunit seem to support CORS (based on commit comments). How do I find what version of htmlunit is bundled with GWT and is there a way to upgrade it? Thanks. Ed -- 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/groups/opt_out.
Re: asm.js
My understanding is that asm.js is all or nothing. It is designed as a target for languages that manage their own memory (that is generally not garbage collected, but you could implement garbage collection in such a system). Firefox looks at the JavaScript and decides if it is asm.js, then switches to another JavaScript interpreter that is optimized for asm.js. If this interpreter detects anything outside of the asm.js subset, it kicks all execution back to the standard interpreter. This means you can't pick part of a gwt compile to target asm.js; it would be all on none. Ed On Thursday, May 23, 2013 12:52:00 AM UTC-7, RyanZA wrote: Have a quick read through this article if you don't know what asm.js is: http://arstechnica.com/information-technology/2013/05/native-level-performance-on-the-web-a-brief-examination-of-asm-js/ With firefox already supporting it, GWT should have the firefox compile target target asm.js for, at least, things like ArrayList. I didn't see anything about it in the recent I/O talk - has anybody looked at how difficult it would be to support in the GWT compiler ? Ryan -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Offline debugging my gwt app
Yves, I would try SuperDev mode and debug using Chrome Dev Tools and the source maps produced by the super dev mode code server. You don't need any special changes to your project, you just need to create a way to launch the super dev mode code server. This is documented at gwtproject.org.herehttp://www.gwtproject.org/articles/superdevmode.html. Here http://lumpofcode.blogspot.com/2012/11/configuring-gwt-codeserver-and.html?view=mosaicis a blog post I wrote with detailed instructions. Ed On Monday, May 20, 2013 11:46:08 AM UTC-7, yves wrote: Hello All, I need to debug my gwt app. The problem is that I need to debug it OFFLINE. After a tour on the net, I didn't found an answer. Thus here is the scenario. My GWT version is 2.4.0 Debugging the code is ok. Running in production offline is ok, using a cache manifest. But I can't do both : debugging offline. To avoid any config difference, I use exactly the same tomcat server deployment to run in production or in debug mode (thus with the debug option -noserver). The cache manifest is built in runtime by a dedicated service whose response depends on the current permutation. When online, the manifest is always requested in debug and in production mode (confirmed by tracing). (a subsidiary question is : why in production the manifest is called twice and in debug it is called once ?). Then I stopped tomcat. = In production offline the gwt app is running correctly. = In debug offline, nothing is displayed : the browser has loaded the app html file from its cache (confirmed by displaying the page source code), but the browser remains empty, the gwt app is not running. It seems that when offline, the google dev plugin doesn't communicate correctly with the IDE as it even doesn't realize when the development mode is stopped in the IDE (the black overlay with the message Plugin failed to connect to Development Mode server at localhost:9997 is no displayed). May be the plugin is not started when offline ? In order to help me test my app when offline, does anybody knows why the app is not running in debug offline mode and how to make it run ? Thanks a lot ! Yves -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: GWT - So terribly slow that makes development hard ... very hard ... extremely hard ...
Ani, here is what I see for compile times when I use super dev mode. Release build (full GWT compile, 6 permutations); 3 minutes. Starting the super dev mode code server (which does an initial compile): 60 seconds. Compile using DevMode On bookmarklet in browser; 10 seconds. So, in the morning I start the code sever (60 seconds) and leave it running all day. From then on, when I change code in Eclipse, I switch to Chrome, run the bookmarklet (10 seconds) to compile it, then debug the Java using source map in Chrome Dev Tools. The bookmarklet compiles a single permutation with reduced number of optimizations, so it is very fast. Overall it's a nice workflow. It's a lot like a JavaScript workflow, except you get a great IDE, tooling and type checking. One thing to know about my project is that I'm doing low level browser coding using GWT. I've written my own framework. I don't use GWT widgets. I don't use UIBinder, which uses a GWT Generator (I believe). My understanding is that generators are very slow when used with Super Dev Mode because they run each time the bookmarklet compile is done. I hope that helps. Ed On Fri, Apr 19, 2013 at 7:54 PM, emurmur wrote: We are using GWT and it is performing very very well. We use SuperDev mode. We have no generators of any kind (I'm told generators can slow down SuperDev mode compiles considerably). Our code/compile/debug cycle is very fast. Doing a release build is pretty slow, but that does not happen very often. We are very productive with it (and so we are happy). Ed On Thursday, April 18, 2013 10:22:15 AM UTC-7, Ani wrote: Now that we have been using GWT for a while ... what do you think? Was it the right choice or thinking of migrating to other framework? -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem use GWT 2.5.0 Super Dev Mode
Here is a blog post I wrote on getting the code server running with the
Elemental library. You might find stuff in it that is useful.
http://lumpofcode.blogspot.com/2012/11/configuring-gwt-codeserver-and.html
On Wednesday, February 27, 2013 1:09:59 AM UTC-8, Dominic Warzok wrote:
Hey I try to use Super Dev Mode in my web app.
But I always get the message
Can't find any GWT Modules on this page. code serverhttp://127.0.0.1:9876/
I follow these Steps to get Super Dev Mode running in eclipse:
1. *add* add-linker name=xsiframe /
set-configuration-property name=devModeRedirectEnabled value=true /
* to my webapp.xml*
2. *build a new Java configuration* Run as Java App
3. *Start up code server* Output:
A lot of compiling packages and this:
* Source Maps Enabled*
* Compile of permutations succeeded*
*Linking into
C:\Users\warzok\AppData\Local\Temp\gwt-codeserver-2196663031883485286.tmp\com.SchumannGmbH.cam.web.Web_CAM\compile-1\war\web_cam;
Writing extras to
C:\Users\warzok\AppData\Local\Temp\gwt-codeserver-2196663031883485286.tmp\com.SchumannGmbH.cam.web.Web_CAM\compile-1\extras\web_cam
*
* Link succeeded*
* Compilation succeeded -- 50,274s*
*Compile completed in 50873 ms*
*SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder.*
*SLF4J: Defaulting to no-operation (NOP) logger implementation*
*SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
further details.*
*
*
*The code server is ready.*
*Next, visit: http://localhost:9876/*
4. *Run normal dev mode* with these programm arguments:
*-war ${workspace_loc:Web-CAM/war} -remoteUI
${gwt_remote_ui_server_port}:${unique_id} -startupUrl Web_CAM.html
-logLevel INFO -codeServerPort 4321 -port
com.SchumannGmbH.cam.web.Web_CAM*
* *
Maybe here is the error ?!
5. *Go to* http://localhost/myWebApp.html
6. *Click Dev Mode On*
If I set up a Testproject this will work but not with my bigger webapp,
Any sugesstions
Thanks in advance .
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: GWT still viable for new projects?
I agree with what James wrote. There is a whole class of alt-js languages that compile to javascript. GWT if by far the most mature and usable. You can use the mature widget library for Enterprise kinds of stuff, our use low level browser api's and Elemental to write 'to the metal' browser code. It optimizes the heck out of the resulting code. It integrates with other Javascriipt libraries (like phonegap). The new codeserver and support for source maps makes the workflow really great. It's a pleasure to use and that is important. Ed On Friday, February 22, 2013 3:50:34 PM UTC-8, Joe Attardi wrote: With recent things like the development of Dart and the moving of GWT to a steering committee, I'm a little uncertain about GWT's future. To those of you more experienced with it - does it still make sense to use for new projects? -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Go from one module to another module
You can set values in localstorage in one page and they can be read in another, provided they are in the same domain. Localstorage is not secure, so do not write sensitive data into localstorage. On Friday, February 8, 2013 3:50:39 AM UTC-8, Visruth CV wrote: Hai, I have many gwt modules in my project. Each module has an entry point, html and css page. I want to go from one module from another module and I should also be able to pass values with it. Consider, the first module contains a login page and the second contains account page. After authentication, how can I go to the second module (with passing some details like user Id user name etc to the second module). Can anybody help me please...Thanks in advance. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: Super dev mode - sourcemap not working anymore
Thomas suggested that it might be in a few weeks. https://groups.google.com/d/msg/google-web-toolkit/OliX8alcMqs/ljeW_XNcY-8J Ed On Tuesday, January 22, 2013 2:34:13 PM UTC-8, Lyden Nee wrote: Ballpark idea of when 2.5.1 will be released? On Thursday, January 17, 2013 9:07:47 AM UTC-5, Thomas Broyer wrote: On Thursday, January 17, 2013 3:01:43 PM UTC+1, Martones wrote: Hi guys ! My source maps doesn't seem to appear once I compile in SDM - Chrome. Did chrome do some update that changed something ? Yes. It worked fine yesterday but now I cant see the sources in the Chrome debug panel anymore. Any ideas ? Fixed in trunk, will be in the soon-to-be-released GWT 2.5.1. https://code.google.com/p/google-web-toolkit/source/detail?r=11408 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/omwLIv601iwJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Super dev mode - sourcemap not working anymore
At Thomas' suggestion I got the latest source code for GWT trunk and built that, then used the sdk that was produced. That fixed the problem for me. Ed On Thursday, January 17, 2013 6:19:24 AM UTC-8, Martones wrote: Alright thanks alot Thomas ! Good luck Le jeudi 17 janvier 2013 15:07:47 UTC+1, Thomas Broyer a écrit : On Thursday, January 17, 2013 3:01:43 PM UTC+1, Martones wrote: Hi guys ! My source maps doesn't seem to appear once I compile in SDM - Chrome. Did chrome do some update that changed something ? Yes. It worked fine yesterday but now I cant see the sources in the Chrome debug panel anymore. Any ideas ? Fixed in trunk, will be in the soon-to-be-released GWT 2.5.1. https://code.google.com/p/google-web-toolkit/source/detail?r=11408 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/9kTqLQfMnrEJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Building GWT 2.5 From Source
I got this same error the first time I tried the build. This issue is that I checked out the source using Tortoise SVN. It was using version 1.6 SVN database. My command line svn tools (which I installed for this purpose) were using 1.7 database format, so the call to svn info failed. You can verify this by going into the trunk folder and running the command from the command prompt. The fix was to uninstall the command line svn tools and install and older version (1.6.20) so it would use the same database format as Tortoise. Ed On Tuesday, January 15, 2013 12:48:03 AM UTC-8, shahid...@docobo.co.uk wrote: Platform: *Windows 7, ANT 1.8.2, Subversion 1.7.8* I checked out the latest source with Tortoise SVN and am trying to build after putting a fix for Issue 2467 but I am getting the following error. I have had to install Subversion 1.7.8 to get the command line svn working because previously I was getting an SVN command error when building: BUILD FAILED C:\Projects\GWT\build.xml:114: The following error occurred while executing this line: C:\Projects\GWT\build.xml:27: The following error occurred while executing this line: C:\Projects\GWT\build.xml:56: The following error occurred while executing this line: C:\Projects\GWT\dev\build.xml:203: The following error occurred while executing this line: C:\Projects\GWT\common.ant.xml:293: Non-zero status code result (1) running comm and: svn info --xml Total time: 10 seconds -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/0OTxhK8DUWMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: SuperDev Mode Java files are not sent to the browser
I built trunk (you guys make this easy, thanks). I used the sdk that I built from trunk (gwt0.0.0.0) and switched my project to this new sdk. That worked (after I fixed the path to gwt-codeserver.jar in my run configuration to point to the new codeserver). Thanks for your help. Ed On Monday, January 14, 2013 6:23:24 PM UTC-8, Thomas Broyer wrote: We'll release 2.5.1 in the coming weeks, and it will have the fix. If you really need it, then either patch your GWT 2.5.0 or build GWT from trunk (we'll cut 2.5.1 from trunk) On Tuesday, January 15, 2013 3:14:06 AM UTC+1, emurmur wrote: Well, I'm not sure how to rollback to Chrome 23. I tried updating my GWT plugin and SDK to latest (SDK 2.5.0 from 12/12/12 I think), but no dice. Now I'm really stuck. I depend on code server and chrome dev tools. Code server was supposed to be the way to avoid issues with browser upgrades. Does anyone from the GWT team have a suggestion? Is anyone out there successfully using Chrome 24/25 and Code Server and Source Maps? Thanks for your help. Ed On Monday, January 14, 2013 5:23:02 PM UTC-8, emurmur wrote: That makes sense. I just uninstalled Chrome 25 and installed latest Chrome (24) and still have the issue. I probably need to back up to 23, which is what I had this morning when everything worked. Thanks for finding that. Ed On Monday, January 14, 2013 5:16:13 PM UTC-8, Paul Stockley wrote: I think the issue could be related to this: https://gwt-review.googlesource.com/#/c/1300/1 On Monday, January 14, 2013 7:46:26 PM UTC-5, emurmur wrote: Unfortunately, I'm just now experiencing the same thing. It started happening immediately after I update to Chrome 25. It's not clear yet that Chrome 25 is the issue. Here is what I did; 1) I was in Chrome 23, happily using code server for compiling and source maps and chrome dev tools for debuggging. 2) I wanted to try the new speech features in Chrome 25, so installed the beta, the restarted chrome (while eclipse and code server were running). 3) I opened up the html file again. I made some changed to my source and compiled it in chrome using the code server bookmark. It compiled correctly, but only javascript source was available. The compiler output shows the source maps are enabled. I checked the chrome dev tools setting and they indicate source maps are still enabled in chrome. 4) I then did a bunch of stuff in various combinations,refreshing the page, clearing the cache, restarting chrome, restarting code server, doing full GWT compile then starting code servers, etc. Still no source maps. So, I'm not sure if it was the upgrading of the browser, or restarting the browser while code server was running. I'll continue to work on this and let you know what I find. If you figure this out, please reply and let me know what you found. Thanks much. Ed On Sunday, January 13, 2013 1:06:24 AM UTC-8, ustakraharez wrote: Dear All, I have a strange problem with SuperDev mode. Sometimes it sends the java files to the browser, sometimes (and sadly more times :-)) it don't. - SuperDev mode run configuration set, and working. - Superdev mode url working - Bookmarks are working, and when I hit Dev Mode On, compiling working (console logged in Eclipse) - But here, nothing happens. When I follow the modulename url from the browser, I can see the compiled source files, but when I open Chrome Web tools, on Sources (and Profiling) tabs only the cache.js can be seen. Source Maps enabled in Chrome of course. I also aware, that if source maps working properly, the *[WARN] : Source maps sent for module : moduleName* can be seen in Eclipse logs. I only don't understand, what is the reason why it is sometimes working and more times not. Thanks a lot for your help! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/xUVW3o9TMj8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: SuperDev Mode Java files are not sent to the browser
Unfortunately, I'm just now experiencing the same thing. It started happening immediately after I update to Chrome 25. It's not clear yet that Chrome 25 is the issue. Here is what I did; 1) I was in Chrome 23, happily using code server for compiling and source maps and chrome dev tools for debuggging. 2) I wanted to try the new speech features in Chrome 25, so installed the beta, the restarted chrome (while eclipse and code server were running). 3) I opened up the html file again. I made some changed to my source and compiled it in chrome using the code server bookmark. It compiled correctly, but only javascript source was available. The compiler output shows the source maps are enabled. I checked the chrome dev tools setting and they indicate source maps are still enabled in chrome. 4) I then did a bunch of stuff in various combinations,refreshing the page, clearing the cache, restarting chrome, restarting code server, doing full GWT compile then starting code servers, etc. Still no source maps. So, I'm not sure if it was the upgrading of the browser, or restarting the browser while code server was running. I'll continue to work on this and let you know what I find. If you figure this out, please reply and let me know what you found. Thanks much. Ed On Sunday, January 13, 2013 1:06:24 AM UTC-8, ustakraharez wrote: Dear All, I have a strange problem with SuperDev mode. Sometimes it sends the java files to the browser, sometimes (and sadly more times :-)) it don't. - SuperDev mode run configuration set, and working. - Superdev mode url working - Bookmarks are working, and when I hit Dev Mode On, compiling working (console logged in Eclipse) - But here, nothing happens. When I follow the modulename url from the browser, I can see the compiled source files, but when I open Chrome Web tools, on Sources (and Profiling) tabs only the cache.js can be seen. Source Maps enabled in Chrome of course. I also aware, that if source maps working properly, the *[WARN] : Source maps sent for module : moduleName* can be seen in Eclipse logs. I only don't understand, what is the reason why it is sometimes working and more times not. Thanks a lot for your help! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/SkUDxNvgPU4J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: SuperDev Mode Java files are not sent to the browser
That makes sense. I just uninstalled Chrome 25 and installed latest Chrome (24) and still have the issue. I probably need to back up to 23, which is what I had this morning when everything worked. Thanks for finding that. Ed On Monday, January 14, 2013 5:16:13 PM UTC-8, Paul Stockley wrote: I think the issue could be related to this: https://gwt-review.googlesource.com/#/c/1300/1 On Monday, January 14, 2013 7:46:26 PM UTC-5, emurmur wrote: Unfortunately, I'm just now experiencing the same thing. It started happening immediately after I update to Chrome 25. It's not clear yet that Chrome 25 is the issue. Here is what I did; 1) I was in Chrome 23, happily using code server for compiling and source maps and chrome dev tools for debuggging. 2) I wanted to try the new speech features in Chrome 25, so installed the beta, the restarted chrome (while eclipse and code server were running). 3) I opened up the html file again. I made some changed to my source and compiled it in chrome using the code server bookmark. It compiled correctly, but only javascript source was available. The compiler output shows the source maps are enabled. I checked the chrome dev tools setting and they indicate source maps are still enabled in chrome. 4) I then did a bunch of stuff in various combinations,refreshing the page, clearing the cache, restarting chrome, restarting code server, doing full GWT compile then starting code servers, etc. Still no source maps. So, I'm not sure if it was the upgrading of the browser, or restarting the browser while code server was running. I'll continue to work on this and let you know what I find. If you figure this out, please reply and let me know what you found. Thanks much. Ed On Sunday, January 13, 2013 1:06:24 AM UTC-8, ustakraharez wrote: Dear All, I have a strange problem with SuperDev mode. Sometimes it sends the java files to the browser, sometimes (and sadly more times :-)) it don't. - SuperDev mode run configuration set, and working. - Superdev mode url working - Bookmarks are working, and when I hit Dev Mode On, compiling working (console logged in Eclipse) - But here, nothing happens. When I follow the modulename url from the browser, I can see the compiled source files, but when I open Chrome Web tools, on Sources (and Profiling) tabs only the cache.js can be seen. Source Maps enabled in Chrome of course. I also aware, that if source maps working properly, the *[WARN] : Source maps sent for module : moduleName* can be seen in Eclipse logs. I only don't understand, what is the reason why it is sometimes working and more times not. Thanks a lot for your help! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/il6xSyKpqBQJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: SuperDev Mode Java files are not sent to the browser
Well, I'm not sure how to rollback to Chrome 23. I tried updating my GWT plugin and SDK to latest (SDK 2.5.0 from 12/12/12 I think), but no dice. Now I'm really stuck. I depend on code server and chrome dev tools. Code server was supposed to be the way to avoid issues with browser upgrades. Does anyone from the GWT team have a suggestion? Is anyone out there successfully using Chrome 24/25 and Code Server and Source Maps? Thanks for your help. Ed On Monday, January 14, 2013 5:23:02 PM UTC-8, emurmur wrote: That makes sense. I just uninstalled Chrome 25 and installed latest Chrome (24) and still have the issue. I probably need to back up to 23, which is what I had this morning when everything worked. Thanks for finding that. Ed On Monday, January 14, 2013 5:16:13 PM UTC-8, Paul Stockley wrote: I think the issue could be related to this: https://gwt-review.googlesource.com/#/c/1300/1 On Monday, January 14, 2013 7:46:26 PM UTC-5, emurmur wrote: Unfortunately, I'm just now experiencing the same thing. It started happening immediately after I update to Chrome 25. It's not clear yet that Chrome 25 is the issue. Here is what I did; 1) I was in Chrome 23, happily using code server for compiling and source maps and chrome dev tools for debuggging. 2) I wanted to try the new speech features in Chrome 25, so installed the beta, the restarted chrome (while eclipse and code server were running). 3) I opened up the html file again. I made some changed to my source and compiled it in chrome using the code server bookmark. It compiled correctly, but only javascript source was available. The compiler output shows the source maps are enabled. I checked the chrome dev tools setting and they indicate source maps are still enabled in chrome. 4) I then did a bunch of stuff in various combinations,refreshing the page, clearing the cache, restarting chrome, restarting code server, doing full GWT compile then starting code servers, etc. Still no source maps. So, I'm not sure if it was the upgrading of the browser, or restarting the browser while code server was running. I'll continue to work on this and let you know what I find. If you figure this out, please reply and let me know what you found. Thanks much. Ed On Sunday, January 13, 2013 1:06:24 AM UTC-8, ustakraharez wrote: Dear All, I have a strange problem with SuperDev mode. Sometimes it sends the java files to the browser, sometimes (and sadly more times :-)) it don't. - SuperDev mode run configuration set, and working. - Superdev mode url working - Bookmarks are working, and when I hit Dev Mode On, compiling working (console logged in Eclipse) - But here, nothing happens. When I follow the modulename url from the browser, I can see the compiled source files, but when I open Chrome Web tools, on Sources (and Profiling) tabs only the cache.js can be seen. Source Maps enabled in Chrome of course. I also aware, that if source maps working properly, the *[WARN] : Source maps sent for module : moduleName* can be seen in Eclipse logs. I only don't understand, what is the reason why it is sometimes working and more times not. Thanks a lot for your help! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/-h3Z_oXSSe8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: SuperDev Mode Java files are not sent to the browser
Looks like it is fixed in SDK 2.5.1, which is not yet released; http://code.google.com/p/google-web-toolkit/issues/detail?id=7725q=sourcemapscolspec=ID%20Type%20Status%20Owner%20Milestone%20Summary%20Stars There is no 2.5.1RC available yet. Does anyone know when that may appear? Anyone have a process for rolling back to Chrome 23? Ed On Monday, January 14, 2013 6:14:06 PM UTC-8, emurmur wrote: Well, I'm not sure how to rollback to Chrome 23. I tried updating my GWT plugin and SDK to latest (SDK 2.5.0 from 12/12/12 I think), but no dice. Now I'm really stuck. I depend on code server and chrome dev tools. Code server was supposed to be the way to avoid issues with browser upgrades. Does anyone from the GWT team have a suggestion? Is anyone out there successfully using Chrome 24/25 and Code Server and Source Maps? Thanks for your help. Ed On Monday, January 14, 2013 5:23:02 PM UTC-8, emurmur wrote: That makes sense. I just uninstalled Chrome 25 and installed latest Chrome (24) and still have the issue. I probably need to back up to 23, which is what I had this morning when everything worked. Thanks for finding that. Ed On Monday, January 14, 2013 5:16:13 PM UTC-8, Paul Stockley wrote: I think the issue could be related to this: https://gwt-review.googlesource.com/#/c/1300/1 On Monday, January 14, 2013 7:46:26 PM UTC-5, emurmur wrote: Unfortunately, I'm just now experiencing the same thing. It started happening immediately after I update to Chrome 25. It's not clear yet that Chrome 25 is the issue. Here is what I did; 1) I was in Chrome 23, happily using code server for compiling and source maps and chrome dev tools for debuggging. 2) I wanted to try the new speech features in Chrome 25, so installed the beta, the restarted chrome (while eclipse and code server were running). 3) I opened up the html file again. I made some changed to my source and compiled it in chrome using the code server bookmark. It compiled correctly, but only javascript source was available. The compiler output shows the source maps are enabled. I checked the chrome dev tools setting and they indicate source maps are still enabled in chrome. 4) I then did a bunch of stuff in various combinations,refreshing the page, clearing the cache, restarting chrome, restarting code server, doing full GWT compile then starting code servers, etc. Still no source maps. So, I'm not sure if it was the upgrading of the browser, or restarting the browser while code server was running. I'll continue to work on this and let you know what I find. If you figure this out, please reply and let me know what you found. Thanks much. Ed On Sunday, January 13, 2013 1:06:24 AM UTC-8, ustakraharez wrote: Dear All, I have a strange problem with SuperDev mode. Sometimes it sends the java files to the browser, sometimes (and sadly more times :-)) it don't. - SuperDev mode run configuration set, and working. - Superdev mode url working - Bookmarks are working, and when I hit Dev Mode On, compiling working (console logged in Eclipse) - But here, nothing happens. When I follow the modulename url from the browser, I can see the compiled source files, but when I open Chrome Web tools, on Sources (and Profiling) tabs only the cache.js can be seen. Source Maps enabled in Chrome of course. I also aware, that if source maps working properly, the *[WARN] : Source maps sent for module : moduleName* can be seen in Eclipse logs. I only don't understand, what is the reason why it is sometimes working and more times not. Thanks a lot for your help! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/fSjEBbNSUDcJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: SuperDev Mode Java files are not sent to the browser
I think we posted on top of each other. Thanks for the timetable on 2.5.1. I have not been building from source, so that is a big time-suck for me to setup and then patch. I'll try to rollback to Chrome 23 first. Thanks again. Ed On Monday, January 14, 2013 6:23:24 PM UTC-8, Thomas Broyer wrote: We'll release 2.5.1 in the coming weeks, and it will have the fix. If you really need it, then either patch your GWT 2.5.0 or build GWT from trunk (we'll cut 2.5.1 from trunk) On Tuesday, January 15, 2013 3:14:06 AM UTC+1, emurmur wrote: Well, I'm not sure how to rollback to Chrome 23. I tried updating my GWT plugin and SDK to latest (SDK 2.5.0 from 12/12/12 I think), but no dice. Now I'm really stuck. I depend on code server and chrome dev tools. Code server was supposed to be the way to avoid issues with browser upgrades. Does anyone from the GWT team have a suggestion? Is anyone out there successfully using Chrome 24/25 and Code Server and Source Maps? Thanks for your help. Ed On Monday, January 14, 2013 5:23:02 PM UTC-8, emurmur wrote: That makes sense. I just uninstalled Chrome 25 and installed latest Chrome (24) and still have the issue. I probably need to back up to 23, which is what I had this morning when everything worked. Thanks for finding that. Ed On Monday, January 14, 2013 5:16:13 PM UTC-8, Paul Stockley wrote: I think the issue could be related to this: https://gwt-review.googlesource.com/#/c/1300/1 On Monday, January 14, 2013 7:46:26 PM UTC-5, emurmur wrote: Unfortunately, I'm just now experiencing the same thing. It started happening immediately after I update to Chrome 25. It's not clear yet that Chrome 25 is the issue. Here is what I did; 1) I was in Chrome 23, happily using code server for compiling and source maps and chrome dev tools for debuggging. 2) I wanted to try the new speech features in Chrome 25, so installed the beta, the restarted chrome (while eclipse and code server were running). 3) I opened up the html file again. I made some changed to my source and compiled it in chrome using the code server bookmark. It compiled correctly, but only javascript source was available. The compiler output shows the source maps are enabled. I checked the chrome dev tools setting and they indicate source maps are still enabled in chrome. 4) I then did a bunch of stuff in various combinations,refreshing the page, clearing the cache, restarting chrome, restarting code server, doing full GWT compile then starting code servers, etc. Still no source maps. So, I'm not sure if it was the upgrading of the browser, or restarting the browser while code server was running. I'll continue to work on this and let you know what I find. If you figure this out, please reply and let me know what you found. Thanks much. Ed On Sunday, January 13, 2013 1:06:24 AM UTC-8, ustakraharez wrote: Dear All, I have a strange problem with SuperDev mode. Sometimes it sends the java files to the browser, sometimes (and sadly more times :-)) it don't. - SuperDev mode run configuration set, and working. - Superdev mode url working - Bookmarks are working, and when I hit Dev Mode On, compiling working (console logged in Eclipse) - But here, nothing happens. When I follow the modulename url from the browser, I can see the compiled source files, but when I open Chrome Web tools, on Sources (and Profiling) tabs only the cache.js can be seen. Source Maps enabled in Chrome of course. I also aware, that if source maps working properly, the *[WARN] : Source maps sent for module : moduleName* can be seen in Eclipse logs. I only don't understand, what is the reason why it is sometimes working and more times not. Thanks a lot for your help! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/2J5YdGJeZvsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: DOM manipulation - setting the height and top in onMouseDown has flakey results
I don't know exactly what your code looks like, but generally, you can listen for the mousedown on the target div, but the mousemove and mouseup you may want to listen on the body element or some enclosing parent div, because you are constantly moving the mouse out of the div. Also, make sure to stopPropagation() preventDefault() on the mousedown event so it does not turn into a click, which can also cause problems. On Friday, January 4, 2013 10:54:28 AM UTC-8, jken...@connectwise.com wrote: We are trying to resize a DOM Div element on the mouse down event by setting the element top and height attribute. This seems to randomly set one or the other or sometimes both. The result is as the user drags the mouse the div keeps flicking and changing size. We tried setting one of the elements in schedule deferred but no luck. We also have a mouse move event that just changes the height and it works fine. Any ideas? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/sGxAvluHobsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Urgent help on Debugging in GWT
I use SuperDevMode and debug directly in the browser using source maps. It is a very productive workflow. See this; https://developers.google.com/web-toolkit/articles/superdevmode And here is a blog post with more details for setting up a Run configuration for the code server: http://lumpofcode.blogspot.com/2012/11/configuring-gwt-codeserver-and.html Ed On Monday, December 10, 2012 10:35:35 PM UTC-8, MB wrote: Hello, Please let me know how can we debug a GWT application. Thanks and regards, Moushmi -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/4E3xbtLI2MEJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT canvas app testing on the Lumia 920/IE 10 mobile
My understanding is that IE10 does not implement TouchEvent. Instead it implements a new event called a PointerEvent that unifies mouse, touch and stylus input. However, if you only care about a single touch point then use mouse events. they work on windows touch devices. On Friday, November 23, 2012 5:54:48 AM UTC-8, Litmus wrote: Just curious, any one else give this a go yet? Ran into touch event issues right off the block, so it looks like its going to take a little fine tuning.. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/kHDc51CxVGkJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: SuperDevMode not so super
I am really enjoying SuperDevMode. My desire is to program to the browser, not to a high-level GWT api. I've build an MVP framework on top of lower level browser api's, so no UI Binder, no request factory, no GWT widgets. Compiles are fast. Debugging in Chrome works well. There are some things to get used-to, and I generally prefer the IDE debugger's ui, but debugging the actual code in the actual execution environment at full speed is a big benefit. I can make changes to html or css and simply reload the page and I'm debugging again in 2 seconds. If I step a little too far in the code, I can reload and I'm debugging again in 2 seconds. If I change a line of Java code, I need to recompile, but that takes about 5 seconds in my app. So SuperDevMode and source maps are ideal for me. If feel like I'm getting the productivity of a Javascript work flow and the structure and code-reliability of Java. Ed On Wednesday, November 14, 2012 11:35:59 AM UTC-8, Clint Gilbert wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/14/2012 09:47 AM, Andrew Mackenzie wrote: IMHO, SuperDev is not the fix for this, and GWT is exploring a path (Source maps, browser debug, etc) that breaks one of the best and distinguishing points of GWT. Agreed. The inability to debug using an IDE makes super dev mode a non-starter for me. SDM solves a problem for the browser plugin maintainers, which I completely understand, but it creates problems for users like me. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCj8lEACgkQ5IyIbnMUeTvFtwCfcMOnIYxXwTsiZu87tDuT1yrJ pL0AoKi8fJKLYPaOohoR3PzZdRaEWWUO =bIqT -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/30Xavun1iLYJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: FastButton? Handling touch events for mobile?
I took a quick look at the code you linked to in stackoverflow. I think the code as written has a few problems. (NOTE: I'm looking at code I wrote using the Elemental library as reference, so some of the calls might be different in the user library). a) The code is not filtering touches aimed at the button; it calls TouchEvent.getTouches(). You want to call TouchEvent.getTargetTouches() on touchstart and touchmove to get the the touches just for your button. You want to call TouchEvent.getChangedTouches() on touchend to get the end touch. b) The code does not take into account multitouch. On touchstart, you can check that a single touch is available and bail out if there is more than one. Also, on touchstart, stash away the id of touch, then use this in touchmove and touchend to find your touch id in the array that is returned (in case the user has touched another finger later on). You can also simplify and check for multiple touches on touchmove and touchend and bail again there. c) I believe you need to call stopPropagation on touchstart, since you are handling the event. I don't see where they call event.preventDefault on the touchstart event You can see that this happens in the click handlers, but not the touchstart. There is also a simpler way. If you don't care about dragging starting on a button, then you can simply call your click logic in the touchstart event (and make sure you call event.preventDefault, TouchEvent.getTargetTouches() and check for single touch) and ignore touchmove and touchend. All the touchmove and touchend stuff is to handle the case of allowing dragging to start on the button. Ed On Monday, November 5, 2012 5:29:53 AM UTC-8, markww wrote: Hi, I've got some buttons on a page which will primarily be used from mobile devices. The click handlers fire only after a 300ms delay (intentional on mobile devices as detailed here [ https://developers.google.com/mobile/articles/fast_buttons]). Looks like someone has tried to implement the above for GWT: http://stackoverflow.com/questions/9596807/converting-gwt-click-events-to-touch-events but I'm getting strange behavior from that FastButton implementation. Is there something baked into GWT 2.5 that does this for us? Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/GTcqhsN8YpAJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: FastButton? Handling touch events for mobile?
Anyplace I wrote event.preventDefault I really meant event.stopPropagation. Ed On Monday, November 5, 2012 10:57:44 AM UTC-8, emurmur wrote: I took a quick look at the code you linked to in stackoverflow. I think the code as written has a few problems. (NOTE: I'm looking at code I wrote using the Elemental library as reference, so some of the calls might be different in the user library). a) The code is not filtering touches aimed at the button; it calls TouchEvent.getTouches(). You want to call TouchEvent.getTargetTouches() on touchstart and touchmove to get the the touches just for your button. You want to call TouchEvent.getChangedTouches() on touchend to get the end touch. b) The code does not take into account multitouch. On touchstart, you can check that a single touch is available and bail out if there is more than one. Also, on touchstart, stash away the id of touch, then use this in touchmove and touchend to find your touch id in the array that is returned (in case the user has touched another finger later on). You can also simplify and check for multiple touches on touchmove and touchend and bail again there. c) I believe you need to call stopPropagation on touchstart, since you are handling the event. I don't see where they call event.preventDefault on the touchstart event You can see that this happens in the click handlers, but not the touchstart. There is also a simpler way. If you don't care about dragging starting on a button, then you can simply call your click logic in the touchstart event (and make sure you call event.preventDefault, TouchEvent.getTargetTouches() and check for single touch) and ignore touchmove and touchend. All the touchmove and touchend stuff is to handle the case of allowing dragging to start on the button. Ed On Monday, November 5, 2012 5:29:53 AM UTC-8, markww wrote: Hi, I've got some buttons on a page which will primarily be used from mobile devices. The click handlers fire only after a 300ms delay (intentional on mobile devices as detailed here [ https://developers.google.com/mobile/articles/fast_buttons]). Looks like someone has tried to implement the above for GWT: http://stackoverflow.com/questions/9596807/converting-gwt-click-events-to-touch-events but I'm getting strange behavior from that FastButton implementation. Is there something baked into GWT 2.5 that does this for us? Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/m6WSLcwPpQkJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT module may need to be (re)compiled message when using SuperDevMode
Make sure that you do a full release compile (using GWT compile from the Google menu) once before running the code server the first time. Of course, the source code server MUST be running for the bookmarklets to work at all. On Saturday, September 8, 2012 9:02:48 PM UTC-7, Paul Stockley wrote: Every time I click the compile button from the 'Dev Mode On' bookmarklet, I get the 'GWT module '..' may need to be (re)compiled' alert. It works fine after that but it's kind of annoying. Anyone have an idea why this happens? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/tv1TxSl1qR0J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Elemental - webkit only?
I'm using Elemental and writing some code that needs requestAnimationFrame. Elemental has Window.webkitRequestAnimationFrame(), which only works on webkit browsers (but not on earlier ones, like the Android 2.3 or 3.1 browsers). It does not work on Firefox or IE. There is a common shim used in Javascript to handle this (which works in all my test cases). So, that brings up the question, how and when will these other modern browsers get Elemental support? Is the plan to create a hybrid IDL and generator that targets common features, using shims where necessary? Or will the compiler generate separate code for multiple IDLs and targets (in which case, it will still need to generate common names based on the 'standard' IDL)? Anything you can tell me will be helpful. Thanks. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/pMd3Q3_TEgcJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How to configure Super Dev Mode in Eclipse ?
In the Run Configuration dialog, make sure you have selected Java
Application from the list on the left. Choosing Web Application get's
all those automatic arguments and so it will not work. You are really
creating a configuration to run the code server, which is a regular Java
application, not a web application.
Ed
On Wednesday, July 18, 2012 4:31:40 PM UTC-7, regnoult axel wrote:
Hello,
I am unsuccessfully configurating Super Dev Mode in Eclipse ( Eclipse
Java EE IDE for Web Developers, Version: *Indigo *Service Release 2 )
To be simple, I am just finding the easiest way (maybe it is easier
without eclipse ?) to use/configure Super Dev Mode...I know the
documentation explain things, but I am more likely looking for a kind of
tutorial for newbies.
First, I go to *Run Configuration* and then I have various
questions/problems :
#1 - Should I create the new configuration for a *Web Application* or a *Java
Application* ? (because in the following link, it is doing a Java
Configuration :
http://blog.daniel-kurka.de/2012/07/mgwt-super-dev-mode.html) ?
#2 - I am asuming that I should use a configuration for a web application
(like I had with the Normal Dev Mode). So then I do not why Eclipse is
always adding the following (even if I remove them and save the config) :
*-remoteUI* ${gwt_remote_ui_server_port}:${unique_id} -logLevel INFO *
-codeServerPort* 9997 -server
com.google.appengine.tools.development.gwt.AppEngineLauncher *-war *
C:\MS\workDir
Is it a bug ?
#3 - Configuring the JRE, I do not know if I should use the *JDK6* or *JDK7
?* If I use JDK6 Eclipse says (I have the same problem with normal dev
mode. ) :
JRE not compatible with workspace .class file compatibility: 1.7
Which JDK should I use ?
#4 - Is there any mandatory argument to add (such as -workDir or
[module]...) ? Because I put this application argument line :
*
*
*-src* C:\MS\src\com* -workDir* C:\MS\workDir *-port* auto *
com.mananaseguro.MananaSeguro*
I had many times the following error : Working directory does not exist:
com.mananaseguro.MananaSeguro
Thanks a lot for your help.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/S8j3wk-RTTwJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Elemental in GWT 2.5 is what?
Elemental is a GWT api that exposes the raw browser api's defined in the browser IDLs. So, Elemental is a 'to the metal' way of programming the browser using Java (assembly programmers please forgive the usage). It allows me to program the browser in a type- safe language using direct browser api's with basically zero overhead. Prior to Elemental, I've been using GQuery to do something similar, but Elemental improves on this in that new API's are implemented sooner and with full fidelity. For me, this means that I can read any article showing how to use a new HTML5 api and implement it in type-safe Java. I can more fully benefit from the experience of the huge community of Javascript programmers that are constantly experimenting with these new apis. I will still use UIBinder and other GWT api's for widget-heavy UIs. However, much of my work is now on mobile and tablets and does not involve IE8 or prior, so Elemental offers a lighter-weight way to handle these platforms. It's true that there is very little formal documentation or examples on Elemental right now. I hope that changes. I would expect that the community will start to use it and that will result in a lot more discussion and examples. I have a little tutorial that explains how to get Elemental, CodeServer and Source Maps working within Eclipse, I'll post that soon. Ed On Jul 9, 3:34 pm, mp31415 mp_...@yahoo.com wrote: I'm trying to make some sense from that Elemental feature. But I'm definitely missing something. On 2.5 main page there is a link to a brief article about Elemental which really does not add much. GWT team is notoriously bad on documentation side and it's not getting any better. Just please don't tell me to shut up and use something else. It's impossible to see the big picture without some background information, like what was missing before, what real purpose of the feature is. It's very nice that we can now call some latest API but what about the more trivial stuff that say UiBinder was in charge so far? Or maybe it is not about UI but more about better hiding JSO types? Or something totally different at all? It's not any better with all other features in fact, but right now my gripe is about Elemental. I looked at the Collide project code. They reference elemental.* packages all over the place and elemental classes carry copyright statement from 2010. So is it new or just recently opened by Google? I mean we get some random pieces of information from GWT team which I have a hard time stitching together. And I didn't download yet 2.5 RC, as I prefer to understand things first, before diving into some low-level details. Thanks. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Call for action: Time to rethink a road-map and more frequent updates for GWT.
I've decided to go with GWT as well. It's mature and solid. It integrates really well javascript and there are many important related projects (like PhoneGap integration). Ray's comments regarding ongoing efforts have been very helpful. I'm particularly anxious to try out Elemental. I've been using GQuery (thanks Ray) to do more low- level stuff with GWT and it works well, but it would be nice to get even closer to the 'metal' and still retain the great tooling and type safety. On May 2, 8:49 am, thumky mdun...@gmail.com wrote: After evaluating many different technologies, i'm starting an ambitious project with GWT for our company. Even knowing what i know about the uncertainty of its future, i'm still choosing it. Because nothing really comes close in terms of high performing enterprise web app development. I'd hope that Google's lack of support/communication is temporary. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Mobile App Widgets
I did a little research a while back. Here are my notes; m-gwt http://code.google.com/p/mgwt/ Set of mobile widgets and transitions for GWT. The widgets are quite good and work on desktop, tablet and phones. My Android 3.1 tablet has trouble with the history, but that is a small problem. The library is well integrated with standard GWT. It uses CSS3 transitions and animations for efficiency. It uses separate CSS files for each browser profile, so it is easy to use the correct sizes and transitions based on browser type. Integrates with gwt-phonegap to create installable applications. The associated blog is also very informative. There is a demo site to show how mGWT performs in mobile and desktop browsers. It is a single site that uses different CSS to display itself for these different form factors. mGWT performs more smoothly than GWT Mobile, but it does not have as many widgets and features. It works well on an Android phone, Android tablet (that is impressive) and desktop webkit browsers. It does not work at all on IE9 (so, more work would need to be done to create a browser profile for IE). The history management works well in both the desktop and mobile browsers, which is a big advantage over GWT Mobile. GWT Designer was recently updated to support mGWT, so it is well integrated with Google’s tooling. GWTMobile http://code.google.com/p/gwtmobile/ GWTMobile is a framework that includes mobile UI widgets, a persistence api and a phone-gap wrapper. The Android store has two demo apps that can be installed. The apps run using GWT-PhoneGap and perform pretty well on an Android phone. I would say most of the transitions are not that good. The mGWT transitions work much better. There is a separate browser demo for desktop and mobile. In both cases, the views are formatted for a phone (the desktop site runs in a picture of a phone). The mobile demo works well on an Android phone and feels almost identical to the demo app, except the history management is broken. I keep hitting the back button and leaves the demo site, which is very aggravating. Again, the transitions are better on mGWT, but GWT Mobile has more user interface widgets. The demo site does not run on IE. CAVEAT: I have not used either of these libraries. I looked at their demos on desktop and mobile browsers. I also downloaded the mobile apps (both based on PhoneGap). Ed On Apr 30, 11:01 am, AgitoM karel.m...@gmail.com wrote: Well the app runs fine on iPhone Safari, Google Chrome, and the Android Default Browser. However the app does not work on Firefox and Opera installations on the Android platform, so that could be a problem. So still hope someone can make a suggestion. On Apr 30, 10:53 pm, Alfredo Quiroga-Villamil laww...@gmail.com wrote: Mobile web libraries are based on webkit. Firefox is not. Mobile devices use webkit. To test the app you can try to use a webkit based browser such as chrome or safari. So if you are happy with that library I recommend you continue using it and test it as previously mentioned. Regards, Alfredo On Apr 30, 2012 10:35 AM, AgitoM karel.m...@gmail.com wrote: Does anyone know a decent library that contains GWT Widgets for the development of Mobile Apps in GWT? Over the past few days I've been experimenting with gwt-mobile-gui. Though this library is great, it doesn't appear to be working on all browsers. (or at least I can't get it to work on Firefox). So basically I am looking into other Libraries. Does anyone have any suggestions? Reason I am looking for a mobile widget library is because I am developing a mobile app. I developed a framework for a mobile app myself, and it works fine, but it looks too ugly. If no other library is available, does anyone know any tutorial of guide to how to develop nice looking GUI in GWT? Hope anyone can offer some advice. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Developers.google.com
I can't find any link to GWT at all, not even from the open source page. I have to say, this developer site is prettier than code.google.com, but it's not nearly as useful. On Apr 23, 6:55 am, Patrice De Saint Steban patou.de.saint.ste...@gmail.com wrote: Hello, There a new developers website for all APIs for Google :http://developers.google.com, and the documentation website of GWT has migrated on the new website :http://developers.google.com/web-toolkit/ But there are no links for GWT on the first page of the news developers page, you must know the URL or click on the page Open Source :http://code.google.com/intl/fr/opensource/ It is an oversight? Patrice -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Call for action: Time to rethink a road-map and more frequent updates for GWT.
I'm one of the fence sitters. I have been using Flex/Flash, which has been fantastic, but has no future on the mobile web. I think there are only two mature tools that would allow me to create similarly rich applications; GWT and Closure Tools. Google has decided that Javascript won't cut it for their own future products, even though they are heavily invested in Closure Tools. I agree completely. It is important to understand that they have also decided NOT to move everything to GWT. This makes some sense, given that the owner of Java is suing them. I think this is in no way a reflection on GWT as a tool and technology. So Google has decided to move forward with a third initiative designed, in part, to replace GWT and Closure Tools at Google. So, I look at that and I am worried about long-term support for GWT. I think that is a reasonable concern. This concern is mitigated by the fact that GWT is a fully open-source project. Flex/Flash on mobile browsers _was_ fully supported and look how that turned out. So, corporate support is no guarantee; open source is actually a safer bet. However, I would feel a lot better if I had an official roadmap for GWT. That being said, Ray's comments on what is coming are heartening. The biggest worry I have for GWT, if Google stops directly supporting it, is the debug environment. The plugin seems to need a lot of maintenance because the browsers are moving so fast. The upcoming support for source-maps mitigates this; I would feel better if I did not have to rely on a plugin. I've been working with Dart quite a bit and it is really promising. However, integration with other Javascript environments is problematic. For instance, Dart integration with PhoneGap does not exist and appears to be very challenging (some have tried and decided to pass on it). This is a non-starter for me. I want to use the mobile web, but I also want the flexibility of providing an app if my customers want one. For now, Dart can't do that. This may also be a problem when trying to integrate a Dart app into Windows 8 Metro. GWT is far superior in this regard; it has a nice architecture for integrating with Javascript and many useful implementations, including a couple for PhoneGap. I'm hoping Javascript integration will be addressed in the future, but Dart is still in alpha and the team is working on core features at least until the language gets to 1.0. Also, because Dart is so young, the tooling cannot compare to Java tooling. This will improve, but Java has many years head start. The Dart team is amazing and I am sure they are creating something very important; I just wish they were 2 more years along. My window for fence sitting is closing fast. I will have to make a decision. GWT and Dart are the only real contenders. As of now, I think GWT is the best choice, but I would sleep better at night if I had a roadmap under my pillow. On Apr 13, 7:34 am, Blake McBride blake1...@gmail.com wrote: I strongly disagree with this. First of all browser technology and HTML are in constant flux. If GWT is not updated, it will very soon become out-of-date (bugs in new browsers) and unusable (reliably usable over a broad base of browsers and platforms). Secondly, building apps with GWT is a full time job. Having to understand and maintain GWT makes two full time jobs. Building GWT apps could easily be a multi-million dollar effort - and so could maintaining GWT. This is a huge, huge risk! Another issue I've seen this many times before. When Windows became popular, many developer tools appeared. Many were quite good. IMO, the worst development environment by far was Microsoft's MFC. Virtually all of the other tools either sold out or got dropped. Management often chose MFC over other tool because they were non-technical and the old IBM adage applied to Microsoft no one ever lost their job by selecting Microsoft ruled. In the end, the industry largely settled on the absolute lowest common denominator. Innovation in that area, for all practical purposes, is dead. Now we have ASP, JSP, and other popular mashups out there. I am utterly shocked how poor they are (although to their credit, they are trying to solve practical problems given an environment that was clearly not meant to support what they are attempting!). These environments are among the worst I've ever seen. It's one kludgy work around after another with three totally different environments attempting to interact. GWT goes a very long way to solve this very significant problem. However, GWT is a total waste of time if you risk your entire company on it and it gets dropped. In terms of financial risk, very unfortunately, tool popularity and support beats functionality, elegance, and productivity every time. A statement of commitment from Google would make a huge difference to me. Blake McBride On Thu, Apr 12, 2012 at 7:52 AM, Frank frank.wyna...@gmail.com wrote:
Re: Restlet
I've been using Restlet starting at 1.x and now at 2.0 in my appengine project, which has been in production for about 6 months. Much of my UI is written using Adobe Flex. I recently attempted to use GWT for part of the UI and had some problems, but there is a work-around and both the GWT and the Restlet team have accepted bugs in their issue trackers. The problem only happens in the development server. GWT writes a system property that overwrites the default xml TransformerFactory. This causes an exception in Restlet if you use an XML Representation. There is a simple workaround. See issue 4267 at, http://code.google.com/p/google-web-toolkit/issues/detail?id=4267. Please go to that issue and star it so it gets some attention. If you use JSON or another format, you should not have any issues at all, this is an XML problem only. As for Restlet, I think it is an excellent package. Very comprehensive. Manning Publications has an early review version of a book by the authors called Restlet in Action. Version 2.0 is at the release candidate phase and it is very stable. Other than the GWT bug in the development mode (which is a GWT bug, not a Restlet bug), I have had no issues. On Jul 22, 8:11 am, michael mich...@michaelvogt.eu wrote: Hello. Right now I am setting up a new project, that uses GWT at the client side. This time I have to use rest for the server communication. Shouldn't be any problem doing that with GWT. But I looked around and found restlet, offered fromhttp://www.restlet.org. Does someone have experience with this in a large GWT-project? I wonder which advantages it offers compared to using the RequestBuilder? Is version 2.0 of it stable enough to be used? Thanks, Michael -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: XSL Transformation, AccessControlException, NoClassDefFoundError and SyntheticRepository
This seems very similar to issue 4267. The issue is the GWT is setting a system property, overriding the default transformer factory. This causes the appengine server to get the wrong transformer factory. The exception you are getting is not exactly the same as the bug, but the circumstances are very similary. A workaround is, in your servlet, set the system property yourself to the java default. This should fix the server (although it might cause an issue in the GWT client, if you are using XML). Note that this is only an issue in the development server and not in production. Here is the issue: http://code.google.com/p/google-web-toolkit/issues/detail?id=4267 Please go and check this issue so it get's some attention. Here is the line of code to set the property on the server to work around the GWT bug: // // When using GWT with appengine, we must override the // default TransformerFactory because GWT writes an invalid // default that causes an exception when trying to // render a XML Representation. This works around the bug. // System.setProperty(javax.xml.transform.TransformerFactory, com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl); On Jul 21, 5:42 am, Jan jan.morl...@googlemail.com wrote: Hi, I would like to use an xsl transformation inside an HttpServlet. The code is essentially the following: File xslfile = new File(test.xsl); TransformerFactory factory = TransformerFactory.newInstance(); factory.setAttribute( debug, true ); Transformer transformer = factory.newTransformer(new StreamSource( xslfile ) ); I already made sure that the xsl file is valid and I defined it as resource-file inside appengine-web.xml If I now call the servlet the first time, the following error occurs: java.lang.ExceptionInInitializerError at com.sun.org.apache.bcel.internal.classfile.JavaClass.init(JavaClass.java: 109) at com.sun.org.apache.bcel.internal.classfile.JavaClass.init(JavaClass.java: 228) at com.sun.org.apache.bcel.internal.generic.ClassGen.getJavaClass(ClassGen.jav a: 174) at com.sun.org.apache.xalan.internal.xsltc.compiler.Stylesheet.translate(Style sheet.java: 735) at com.sun.org.apache.xalan.internal.xsltc.compiler.XSLTC.compile(XSLTC.java: 354) at com.sun.org.apache.xalan.internal.xsltc.compiler.XSLTC.compile(XSLTC.java: 429) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemp lates(TransformerFactoryImpl.java: 795) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTran sformer(TransformerFactoryImpl.java: 617) at com.axag.invoiceedit.server.MY SERVLET.doGet(MY SERVLET:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 511) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1166) at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFi lter.java: 51) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(Trans actionCleanupFilter.java: 43) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1157) at com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFile Filter.java: 122) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: 216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: 182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java: 765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 418) at com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEn gineWebAppContext.java: 70) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at com.google.appengine.tools.development.JettyContainerService $ApiProxyHandler.handle(JettyContainerService.java:349) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java: 542) at org.mortbay.jetty.HttpConnection $RequestHandler.headerComplete(HttpConnection.java:923) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547) at
Re: GWT 2.0.4 caused Class Not Found, TransformerFactoryImpl
Thank you Shyam, I verified that this eliminates the server-side exception when using GWT, Appengine and Restlet together when using XML at the transport. However, I'm still a little worried. The reason the exception is thrown is because GWT itself writes this system property to something that it needs (see issue 4267) while running in the development server. By overwriting this value, we may be re-creating the issue that GWT intended to address by setting the property. So, we still need a real fix to issue 4267. Please go and star the issue at: http://code.google.com/p/google-web-toolkit/issues/detail?id=4267 Thank you again Shyam. On Jul 16, 7:34 am, Shyam Visamsetty shyamsunder...@gmail.com wrote: You should use this for creating XML transformations on App Engine. System.setProperty(javax.xml.transform.TransformerFactory, com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl); You definitely cant use this on the client side. Thanks, Shyam Visamsetty On Jul 16, 12:20 am, Jan jan.morl...@googlemail.com wrote: No, it is definitely the server side where I'm trying this reflection. Anyway, thank's -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.0.4 caused Class Not Found, TransformerFactoryImpl
Here is example restlet code that shows the fix in a restlet
application:
/**
* Creates a root Restlet that will receive all incoming calls.
*/
@Override
public synchronized Restlet createInboundRoot()
{
//
// When using GWT with appengine, we must override the
// default TransformerFactory because GWT writes an invalid
// default that causes an exception when trying to
// render a XML Representation. This masks the bug.
//
System.setProperty(javax.xml.transform.TransformerFactory,
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl);
// Create a router Restlet that defines routes.
Router router = new Router(getContext());
//
// Defines a route for the resource list of customer
// the route is used to get the list of customers or
// to create a new customer.
//
router.attach(/service, ServiceResource.class);
return router;
}
On Jul 16, 9:13 am, emurmur emur...@conceptuamath.com wrote:
Thank you Shyam, I verified that this eliminates the server-side
exception when using GWT, Appengine and Restlet together when using
XML at the transport. However, I'm still a little worried. The
reason the exception is thrown is because GWT itself writes this
system property to something that it needs (see issue 4267) while
running in the development server. By overwriting this value, we may
be re-creating the issue that GWT intended to address by setting the
property. So, we still need a real fix to issue 4267. Please go and
star the issue
at:http://code.google.com/p/google-web-toolkit/issues/detail?id=4267
Thank you again Shyam.
On Jul 16, 7:34 am, Shyam Visamsetty shyamsunder...@gmail.com wrote:
You should use this for creating XML transformations on App Engine.
System.setProperty(javax.xml.transform.TransformerFactory,
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl);
You definitely cant use this on the client side.
Thanks,
Shyam Visamsetty
On Jul 16, 12:20 am, Jan jan.morl...@googlemail.com wrote:
No, it is definitely the server side where I'm trying this reflection.
Anyway, thank's
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT roadmap: easier use of REST?
GWT has a bug that prevents it from being use with Restlet. The Restlet framework has direct support for both Appengine, as a service provider, and GWT as a client. However, a bug added to GWT since 1.7 makes it impossible to use GWT with a restlet server if you want to use XML representations. It may may work fine with JSON. Here is the reference to the issue tracker; http://code.google.com/p/google-web-toolkit/issues/detail?id=4267. If you want GWT to be fully compatible with Restlet (which is an excellent package), please go and star this issue. Ed On Jul 9, 2:39 am, marius.andreiana marius.andrei...@gmail.com wrote: Hi, A lot of web APIs use REST nowadays. GWT seems really well suited to build mashups/UIs on top of REST web services. However, it's not that easy to work with REST from GWT (see alsohttp://groups.google.com/group/google-web-toolkit/browse_thread/threa... ) There are two projects tackling this: * Restlethttp://blog.noelios.com/2008/07/25/restlet-ported-to-gwt/ * SmartGWT'shttp://www.smartclient.com/smartgwt/javadoc/com/smartgwt/client/docs/... (it provides DataSources, then makes it easy to have REST DataSources, both read/write) Are there any plans to improve out-of-the-box GWT to work with REST, so no additional libraries are needed? Is there a wish list to submit this request? Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.0.4 caused Class Not Found, TransformerFactoryImpl
There is an issue in the tracker for this bug, http://code.google.com/p/google-web-toolkit/issues/detail?id=4267. Please go and stat that issue and leave a comment, so it get's some attention. There is also an issue in the Restlet issue tracker that contains a small example that shows the bug at, http://restlet.tigris.org/issues/show_bug.cgi?id=1149. On Jul 8, 9:06 pm, davewilliamson dave.p.william...@googlemail.com wrote: Interestingly, I have 'just' come across the same problem in the middle of development! Using Elipse's neat trick of setting SDK versions, I have found that this problem exists since V2.0, whereas the older SDK 1.7.1 works fine = a very poor but quick work around, that is FAR from ideal!!! Come on Google, give us a fix! Cheers Dave On Jul 8, 8:51 pm, emurmur emur...@conceptuamath.com wrote: I've traced through theRestlet2.0rc4 code for both the success case (no GWT) and the failure case (gwt-dev.jar in on classpath). The issue is how DomRepresentation.createTransformer() creates the necessary javax.xml.transform.TransformerFactory instance. In the success case, we end up in FractoryFinder.findJarService() at the line 255, is = ss.getResourceAsStream(cl, serviceId); and the result is null. Therefore, the code returns and uses the fallback class (com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl), which works. In the failure case (when gwt-dev.jar in on the classpath), line 255 DOES return a class, the code that immediately follows is then able to read the factoryClassName from the class, which ends up being, org.apache.xalan.processor.TransformerFactoryImpl. Later, the attempt to instantiate this class fails with a ClassNotFoundException. So it seems that the gwt-dev.jar file contains some configuration that tricksRestletinto attempting to instantiate the wrong TransformerFactory implementation. How would I go about makingRestletignore this Jar. Note that this is only an issue in the development environment, because gwt-dev.jar is not copied to the production server. However, it's still a show stopper bug for me, because I can't debug my client application with my rest services. Does anyone on the GWT team know that this may be about? Any help would be welcome. I will pass it on to theRestletteam. Thanks. On Jul 7, 10:01 am, emurmur emur...@conceptuamath.com wrote: I have an Java App Engine project using SDK 1.3.5 and the latest RestletGAE 2.0rc4 to implement some restful services. Everything worked well (this has been in production for 6 months) until I added GWT 2.0.4 to the project. As soon as I check use GWT on in the control panel in Eclipse (without even adding a module) my services start to fail in the development server with the following class not found exception: Couldn'twritetheXMLrepresentation:Provider org.apache.xalan.processor.TransformerFactoryImpl not found This exception happens on the way out of myRestlet, after a GET of a lists of entities, as it tries to turn my DomRepresentation into the response payload. I've found that if I remove the gwt-dev.jar, the exception does not happen. Of course, I can't use the development server if I do that. Again, this all works fine without GWT. Here is the relevant parts of the trace: SEVERE: An exception occured writing the response entity java.io.IOException:Couldn'twritetheXMLrepresentation:Provider org.apache.xalan.processor.TransformerFactoryImpl not found at org.restlet.ext.xml.DomRepresentation.write(DomRepresentation.java: 287) at org.restlet.representation.WriterRepresentation.write(WriterRepresentation. java: 104) at org.restlet.engine.http.ServerCall.writeResponseBody(ServerCall.java: 502) at org.restlet.engine.http.ServerCall.sendResponse(ServerCall.java: 439) at org.restlet.ext.servlet.internal.ServletCall.sendResponse(ServletCall.java: 451) at org.restlet.engine.http.adapter.ServerAdapter.commit(ServerAdapter.java: 198) at org.restlet.engine.http.HttpServerHelper.handle(HttpServerHelper.java: 151) at org.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:1037) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.jav a:1166) at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFi lter. java:51) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.jav a:1157) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(Trans actio nCleanupFilter.java:43
Re: GWT 2.0.4 caused Class Not Found, TransformerFactoryImpl
I've traced through the Restlet 2.0rc4 code for both the success case (no GWT) and the failure case (gwt-dev.jar in on classpath). The issue is how DomRepresentation.createTransformer() creates the necessary javax.xml.transform.TransformerFactory instance. In the success case, we end up in FractoryFinder.findJarService() at the line 255, is = ss.getResourceAsStream(cl, serviceId); and the result is null. Therefore, the code returns and uses the fallback class (com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl), which works. In the failure case (when gwt-dev.jar in on the classpath), line 255 DOES return a class, the code that immediately follows is then able to read the factoryClassName from the class, which ends up being, org.apache.xalan.processor.TransformerFactoryImpl. Later, the attempt to instantiate this class fails with a ClassNotFoundException. So it seems that the gwt-dev.jar file contains some configuration that tricks Restlet into attempting to instantiate the wrong TransformerFactory implementation. How would I go about making Restlet ignore this Jar. Note that this is only an issue in the development environment, because gwt-dev.jar is not copied to the production server. However, it's still a show stopper bug for me, because I can't debug my client application with my rest services. Does anyone on the GWT team know that this may be about? Any help would be welcome. I will pass it on to the Restlet team. Thanks. On Jul 7, 10:01 am, emurmur emur...@conceptuamath.com wrote: I have an Java App Engine project using SDK 1.3.5 and the latest Restlet GAE 2.0rc4 to implement some restful services. Everything worked well (this has been in production for 6 months) until I added GWT 2.0.4 to the project. As soon as I check use GWT on in the control panel in Eclipse (without even adding a module) my services start to fail in the development server with the following class not found exception: Couldn't write the XML representation: Provider org.apache.xalan.processor.TransformerFactoryImpl not found This exception happens on the way out of my Restlet, after a GET of a lists of entities, as it tries to turn my DomRepresentation into the response payload. I've found that if I remove the gwt-dev.jar, the exception does not happen. Of course, I can't use the development server if I do that. Again, this all works fine without GWT. Here is the relevant parts of the trace: SEVERE: An exception occured writing the response entity java.io.IOException: Couldn't write the XML representation: Provider org.apache.xalan.processor.TransformerFactoryImpl not found at org.restlet.ext.xml.DomRepresentation.write(DomRepresentation.java: 287) at org.restlet.representation.WriterRepresentation.write(WriterRepresentation. java: 104) at org.restlet.engine.http.ServerCall.writeResponseBody(ServerCall.java: 502) at org.restlet.engine.http.ServerCall.sendResponse(ServerCall.java: 439) at org.restlet.ext.servlet.internal.ServletCall.sendResponse(ServletCall.java: 451) at org.restlet.engine.http.adapter.ServerAdapter.commit(ServerAdapter.java: 198) at org.restlet.engine.http.HttpServerHelper.handle(HttpServerHelper.java: 151) at org.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:1037) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.jav a:1166) at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFi lter. java:51) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.jav a:1157) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(Trans actio nCleanupFilter.java:43) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.jav a:1157) at com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFile Filte r.java:122) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.jav a:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: 216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: 182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java: 765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 418) at com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEn gineW ebAppContext.java:70) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152
GWT 2.0.4 caused Class Not Found, TransformerFactoryImpl
I have an Java App Engine project using SDK 1.3.5 and the latest Restlet GAE 2.0rc4 to implement some restful services. Everything worked well (this has been in production for 6 months) until I added GWT 2.0.4 to the project. As soon as I check use GWT on in the control panel in Eclipse (without even adding a module) my services start to fail in the development server with the following class not found exception: Couldn't write the XML representation: Provider org.apache.xalan.processor.TransformerFactoryImpl not found This exception happens on the way out of my Restlet, after a GET of a lists of entities, as it tries to turn my DomRepresentation into the response payload. I've found that if I remove the gwt-dev.jar, the exception does not happen. Of course, I can't use the development server if I do that. Again, this all works fine without GWT. Here is the relevant parts of the trace: SEVERE: An exception occured writing the response entity java.io.IOException: Couldn't write the XML representation: Provider org.apache.xalan.processor.TransformerFactoryImpl not found at org.restlet.ext.xml.DomRepresentation.write(DomRepresentation.java: 287) at org.restlet.representation.WriterRepresentation.write(WriterRepresentation.java: 104) at org.restlet.engine.http.ServerCall.writeResponseBody(ServerCall.java: 502) at org.restlet.engine.http.ServerCall.sendResponse(ServerCall.java: 439) at org.restlet.ext.servlet.internal.ServletCall.sendResponse(ServletCall.java: 451) at org.restlet.engine.http.adapter.ServerAdapter.commit(ServerAdapter.java: 198) at org.restlet.engine.http.HttpServerHelper.handle(HttpServerHelper.java: 151) at org.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:1037) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.jav a:1166) at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter. java:51) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.jav a:1157) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(Transactio nCleanupFilter.java:43) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.jav a:1157) at com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilte r.java:122) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.jav a:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java: 388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java: 216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java: 182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java: 765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 418) at com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineW ebAppContext.java:70) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at com.google.appengine.tools.development.JettyContainerService $ApiProxyHandler.han dle(JettyContainerService.java:349) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java: 152) at org.mortbay.jetty.Server.handle(Server.java:326) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
