Re: Is there a Chrome extension/api which allows for 'read/write *.txt/*.js file' ?
This question is so confusing I can only respond with an equally confusing answer: Have you tried V http://www.vim.org/im? Ok, a more serious answer would be: Can you tell us what you're trying to accomplish? Why would you try to edit a txt or js file in a browser? :-) Ryan On Sunday, January 20, 2013 10:16:12 AM UTC-6, vmars316 wrote: Email updates to me -- 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/-/rbQSrzUR8GYJ. 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: The Future of GWT Report 2012 Published
I just wanted to thank you for taking the time to make this so consumable. I found it very interesting to read. If getting my (spam-me-as-much-as-you-want) email was the cost, I'd pay that again happily. Whoever put this together did a very, very good job. If this had been a big table of numbers I wouldn't have learned as much. Thanks again, Ryan On Tuesday, December 4, 2012 5:19:05 AM UTC-6, Joonas Lehtinen wrote: *The GWT community have been having many questions about the Future of GWT. Questions like: Where is GWT going? How is GWT used today? What are the challenges they are facing? What is the competition? Should I build my next project with GWT? When joining the GWT steering committee and deciding to include a full copy of GWT into Vaadin 7 we had the same questions. In the end we stepped forward and asked the GWT community. Now after 2 months of asking and receiving responses to the dozens of questions we had from over over 1300 GWT users, we compiled all of this together and are proud to present you with some answers in for of 30 page long report. We would like to thank everyone who participated: You - the very active GWT community who answered, GWT steering committee members and other GWT experts who helped create the questions and analyze the answers, Vaadin team and David Booth who coordinated the effort. Enough talking, download your personal copy of The Future of GWT Report at: * * https://vaadin.com/gwt/report-2012 * -- 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/-/HX43ol9dILIJ. 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: Roadmap GWT?
Thanks Thomas, that's a start. I was hoping for something more than that, but I guess I'll be patient. When is the next SC meeting / decision point? On Friday, November 9, 2012 4:01:32 AM UTC-6, Thomas Broyer wrote: On Friday, November 9, 2012 2:56:00 AM UTC+1, Joseph Lust wrote: Are the calls/meetings still regular? I had thought they were going to be Hangouts and recorded, but there is little mention of anything on the forum. There hasn't been any other meeting. Several SC members were touring the world for conferences recently (mGWT, Vaadin and Errai). I must confess we've exchanged a bit by mail off-list, but no decision were made, except for welcoming JetBrains as a new SC member. I promise you we'll come back in the open soon, now that GWT 2.5.0 has been released, Gerrit is being setup, and I'm working hard to move to Maven and modularize. -- 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/-/XfFCGZ9H6q8J. 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: Roadmap GWT?
To be a little more blunt than Christian - I would like to see some results from the Steering committee. I don't care about timelines as much as I care about direction. What direction are you taking GWT for vNext? Ryan On Monday, November 5, 2012 4:07:28 AM UTC-6, ChrLipp wrote: We are starting a new project and GWT is a possible candidate for the implementation. So I would also be interested to see a road map. Road maps generate trust (if you see a plan for the next year ahead and if you can watch the team reaching the planned milestones in time). I know the steering committee group, but there is no message since mid of August. Sincerely, Christian Am Samstag, 3. November 2012 17:01:07 UTC+1 schrieb Joseph Lust: Stay tuned to the Steering Committeehttps://groups.google.com/forum/#!forum/gwt-steeringif you want to know where they are steering towards. Sincerely, Joseph -- 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/-/EPCzhpHoLFEJ. 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 2.5 GA is Here!
Is there a roadmap for GWT? I'd really like to create switch statements for Strings. It would make our Place locator, which I suspect a lot of projects have who hadn't seen that awesome GWT Architecture video at the start of their project, so much cleaner. Ryan On Thursday, November 1, 2012 6:41:41 AM UTC-5, Dean S. Jones wrote: Can you outline the incompatibilities between GWT proper and using Elemental? Ran into some issues with ArrayList, etc... bombing out if used in both. Also, and updates on Java7 server side support in GAE? -- 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/-/m-ONyNKp478J. 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: Future of GWT survey
Crap. I also forgot about that. I want to go back. On Wednesday, September 19, 2012 10:50:05 AM UTC-5, Dave Laycock wrote: I wish I could change my responses. I forgot about the single biggest improvement I would like to see on the long term roadmap: support for Java 8 language features On Wednesday, 19 September 2012 07:23:24 UTC-6, Joonas Lehtinen wrote: What is your opinion on the future of GWT? How should GWT develop? What technologies should it better support? ... We all would like to get answers to these questions, right? To do so, we created survey with help of Ray Cromwell, Artur Signell, Mike Brock, David Chandler, Daniel Kurka and Bhaskar Janakiraman. If you want to help finding the best direction for GWT, please fill the survey at: http://bit.ly/GWT2012 (it will take just 10 minutes) When the results are collected, the will share the information with you. - Joonas @ Vaadin -- 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/-/z7Tfib2LX44J. 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 Compilation Time Performance Improvement
Niraj, you didn't mention the -localWorkers flag. On a quad-core machine that reduced our compile time to about 1/3 of what it was (our 300s compile time became 100s). Ryan On Tuesday, September 4, 2012 1:10:19 AM UTC-5, Niraj Salot wrote: Hi Members, We are using GWT Version 2.4 in our current project. On server side, we are using Spring Custom JDBC framework. We are using Maven as our Build Tool. The application is getting deployed on JBOSS 7 Server. Currently we have everything in one single Eclipse Project. Means one Application.gwt.xml file and one ApplicationContext.xml for spring. We have around 2000 Java files out of which around 1500 are for GWT related source files. The project is still growing with more source files. We are fine with timings of Java to Javac [class file] Compilation time. But when It comes to Java to JavaScript , It is a issue. We have used all hacks mentioned in the GWT Forum. Like. 1. Compiling for only one Local 2. Compiling for only one Browser But still the compilation is taking 4-6 minutes.. OR even 7 minutes some times. With this question, I would like to know the options available to improve the same. We are thinking to Split the Project like this WAY: - Module 1 (JAR Build) - Module 2 (JAR Build) - Module Main (WAR Build). This would contain Application.gwt.xml file which would inherit Module 1 Module 2. Now Question comes: *1) Will this help us in Improving the compilation time?* *2) IF we change only Module 2 and then compile Module Main, will GWT still compile Module 1 as it is inherited by Module Main?* Please share your views on above scenario. We have even tried out GWT 2.5 option but no help in performance improvements. Thanks, Niraj Salot. -- 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/-/6wcp0gRAmb4J. 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: Single images of corner.png/circles.png, etc
There's no way (that I know of) to change an image's color in GWT. That kind of thing is child's play in Adobe Photoshop / Gimp. If you want a really nice site design, you're almost certainly going to need to create these images yourself. Also, CSS3 supports doing most of that kind of stuff without needing any images anymore. If you're not planning on supporting IE 8 (which Google will drop support for once IE 10 comes out in a month or 2), then that's the way to go. Ryan On Wednesday, September 5, 2012 7:38:13 AM UTC-5, Musicman75 wrote: Hello, I need to generate a new theme for gwt. Therefore I need the single images of the combined corner.png, circles.png, etc. Is there a possibility to get these images as single images (not wrapped together)? Is there an other way to build an own theme and using images instead of the default images for the border? I don't want to design these images from scratch, just use the original images and change the color. Thanks for 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/-/O1f0V9AR2WsJ. 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: com.google.gwt.junit.client.TimeoutException: The browser did not contact the server within 60000ms.
For the next poor soul - this started happening to me as soon as I moved
from Java 6 (where my GWTTestCases worked fine) to Java 7.
I know, I know, don't use GWTTestCases. We learned that the hard way. We
have a couple of legacy ones that we never converted into Selenium tests.
Well, I guess this will force us to convert them now.
Ryan
On Monday, November 2, 2009 7:20:03 AM UTC-6, Dominik Steiner wrote:
I haven't tried the UiBinder yet, but if i remember right I read
somewhere that it is now prefered to use HtmlUnit tests instead of
using the GWTTestCase.
HTH
Dominik
On Oct 31, 9:49 am, Tiago Fernandez tiago...@gmail.com wrote:
Hello,
I have a fully working webapp built with GWT-2.0.0-ms2's UiBinder.
Recently I decided to get it covered by unit tests using GWTTestCase,
but after coding a simple test case:
public class MyTest extends GWTTestCase {
@Override public String getModuleName() {
return foo.bar.MyApp;
}
public void testAnythingYouWant() {
assertTrue(true);
}
I stumbled on this:
com.google.gwt.junit.client.TimeoutException: The browser did not
contact the server within 6ms.
- 1 client(s) haven't responded back to JUnitShell since the start of
the test.
Actual time elapsed: 60.009 seconds.
at com.google.gwt.junit.JUnitShell.notDone(JUnitShell.java:800)
at
com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:989)
at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:436)
at
com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:
386)
at
com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:269)
at com.intellij.junit3.JUnit3IdeaTestRunner.doRun
(JUnit3IdeaTestRunner.java:108)
at com.intellij.rt.execution.junit.JUnitStarter.main
(JUnitStarter.java:60)
Process finished with exit code 255
The same test works fine when targeting a module NOT UiBinder-based.
Any hint? I am using IDEA on a Mac, with the following VM arguments:
-XstartOnFirstThread -Xmx512M
Thanks in advance,
Tiago Fernandez
--
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/-/x-CWA6q8v3QJ.
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: DART vs. GWT
Google is an incubator. They throw a lot of darts at the wall to see what sticks (pun intended). When you have 10 irons in the fire, one or 2 of them are bound to glow hot. There's no reason to believe that Dart will win over GWT in the next 2-3 years if you're building something of modest complexity. My company (onlyinsight.com) is a start-up. We use wordpress for our main site (so basically PHP) which is super-simple (5-10 pages). For our first big real product, with half a million lines of code, we're using GWT (and wouldn't consider Ruby/PHP). Ruby/Rails/PHP to me is like a chainsaw - it's super-easy to cut down trees with, but it's just as easy to cut your arm off. You don't want a million lines of a scripting language. Ryan On Sunday, August 26, 2012 6:42:07 PM UTC-5, b0b wrote: On Wednesday, 22 August 2012 17:57:42 UTC+2, deepak chauhan wrote: One question is disturbing me from a long time. Why Google invented DART, when GWT is already there? To have one more project to can in a few months/years, instead of puting all resources behind GWT. -- 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/-/7ZK-h8gH6OQJ. 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 and automated testing tools
We've been using Selenium for 6 months now, and quite happily. Occasionally the browser will do something stupid like ask to install an update and ruin the test, but that happens pretty rarely. It works pretty well across IE, Chrome Firefox. Through the grapevine, I heard that Selenium is used by Google internally, which is why we chose it initially. They use it to test Gmail, Google.com, Chrome, etc. Sachin is correct about setting IDs to make tests work better. If you are not able to modify the code to add IDs, then there's no test strategy that I know of that will work well. Ryan On Thursday, August 23, 2012 12:19:30 PM UTC-5, Sachin Shekhar R wrote: We have hundreds of Forms which are tested using internal library based on Selenium Automation. It works really well across browsers and with both GXT and GWT. The key thing is to avoid using Record feature which generates flaky test and instead rely on ID/Xpath based Java api to wrap test cases. On Friday, 10 August 2012 06:33:38 UTC+5:30, 退5的工科苹岷 wrote: Selenium is suggested in a book Essential GWT Building for web with Google Web Toolkit 2. I never touched. Can anyone give some samples if it is a good solution for GWT auto test? Thanks. 2012/8/9 Ocean_Living winter...@gmail.com I'm having some performance issues using Rational Functional Tester as an automated testing tool when testing a web app built on GWT. Can anyone recommend an automated tool that works and plays well with GWT? 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/-/g3DtPqxfvJwJ. To post to this group, send email to google-we...@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. -- Gong Min gongm...@gmail.com -- 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/-/M-jA10O4UioJ. 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 future
FunkForce, do the math. If GWT 2.4 came out before the browser was even in beta, how could they have tested it? Now with that said, browsers are generally tested against a multitude of different sites. At least a few of them are using GWT. So it's highly improbable that your site won't work at all. There will be a few things off though, for sure. A border that's not quite right here, a button 10 pixels off of where it should be there, that kind of thing. The biggest problem is usually IE. They allow a meta tag that tells the browser render it in version X please that you can put in your base html. That should get you through until you can fix whatever small thing is off. Ryan On Monday, August 6, 2012 3:05:55 AM UTC-5, funkforce wrote: Thomas, Reading this: but until then, GWT will have adapt to each new browser version, and your app would have to be recompiled with the newer version of GWT to take advantage of it. Do you meant that if I deploy an app compiled with GWT 2.4 today and in a few weeks a new browser version is released , that app wont work with the new browser? Regards FF Den fredagen den 27:e juli 2012 kl. 17:32:15 UTC+2 skrev Thomas Broyer: On Friday, July 27, 2012 4:53:43 PM UTC+2, Andrei wrote: A few thoughts on the future of GWT. 1. GWT, as we currently know it, will die. It will be replaced by a more native way of writing apps for the web. This process will take years. Hopefully, GWT will also adjust, keeping its relevance for a long time. Elemental is the step in that direction. 2. Google wants to kill Java. It started with a lawsuit from Oracle - Google responded by launching Dart and Go. It won't be clear for at least another year if either Dart or Go become viable alternatives to Java. I will not be surprised if both of these efforts will be quietly abandoned by Google now that the threat from Oracle is over. They will most likely make no such decision any time soon, but I would not recommend starting any major projects in Dart for at least another year. I absolutely do NOT agree with the above two points. Dart isn't there to replace GWT, it's been created to compete with JavaScript (and compile to JavaScript for a smooth transition: you don't want to code your app twice, right?) because the dynamic nature of JavaScript makes it really hard to optimize JS engines. And Go has been created to compete with C++, at least for some usage of it ( http://commandcenter.blogspot.fr/2012/06/less-is-exponentially-more.html) Finally, I cannot see a single reason Google would like to kill Java. Sure there was the Oracle lawsuit, but Google has too much dependency on Java. Switching over from Java would likely kill Android, and could cost Google way too much to be a viable move, unless Google would have no other choice (e.g. if Oracle had won the case, but then Oracle would have killed Java, not the other way around). 3. Even though GWT is not as enthusiastically supported by Google as it should be (in my opinion), I would certainly recommend against forcing your team to learn a completely new platform. If you are a Java shop, GWT is the best available option for any project starting this year. 4. Web browsers have really matured (i.e. stabilized) over the past couple of years. Unless you are building a cutting-edge 3D game or a web-based replacement for Photoshop, your new GWT app will stay relevant for a decade. It will morph, like all good projects do, but GWT is a very solid foundation for data manipulation, i18n, history management, and page rendering. And you can add as much (or as little) HTML5 and CSS3 on the presentation side as you want - I don't feel like GWT is restricting me in any way. +1 to that though (even though you'd have to recompile your app regularly against the updated versions of GWT if you want it to last a decade: browsers have matured, but GWT still has to handle each one of them specifically; in the future maybe we'd have a single permutation across all browsers, but until then, GWT will have adapt to each new browser version, and your app would have to be recompiled with the newer version of GWT to take advantage of it. -- 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/-/RFR3SeYai14J. 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: RequestFactory Error -- java.lang.IllegalArgumentException: Something other than a Java object was returned from JSNI method
It's already been reported here: http://code.google.com/p/google-web-toolkit/issues/detail?id=5778 Looks like it's a devMode only issue. Ryan On Wednesday, April 25, 2012 10:14:04 PM UTC-5, Pradeep B Pillai wrote: The following is the other error i get frequently and this seems like its more related to request factory and I dont know why its happening ..Should I open a bug ? I'm using GWT 2.4, browser Chrome 18.0.1025.1065 One or more exceptions caught, see full set in UmbrellaException#getCauses - CAUSE java.lang.IllegalArgumentException: Something other than a Java object was returned from JSNI method '@com.google.web.bindery.autobean.gwt.client.impl.ClientPropertyContext $Setter::beanSetter(Lcom/google/web/bindery/autobean/shared/impl/ AbstractAutoBean;Ljava/lang/String;)': JS value of type boolean, expected java.lang.Object java.lang.IllegalArgumentException: Something other than a Java object was returned from JSNI method '@com.google.web.bindery.autobean.gwt.client.impl.ClientPropertyContext $Setter::beanSetter(Lcom/google/web/bindery/autobean/shared/impl/ AbstractAutoBean;Ljava/lang/String;)': JS value of type boolean, expected java.lang.Object STACKTRACE : com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext $StandardPayloadDialect.processPayload(AbstractRequestContext.java: 387) com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext $5.onTransportSuccess(AbstractRequestContext.java:1108) com.google.web.bindery.requestfactory.gwt.client.DefaultRequestTransport $1.onResponseReceived(DefaultRequestTransport.java:136) com.citrix.ws.democenter.module.shared.client.requestfactory.DemoCenterRequestTransport $1.onResponseReceived(DemoCenterRequestTransport.java:84) com.google.gwt.http.client.Request.fireOnResponseReceived(Request.java: 287) com.google.gwt.http.client.RequestBuilder $1.onReadyStateChange(RequestBuilder.java:395) sun.reflect.GeneratedMethodAccessor352.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25) java.lang.reflect.Method.invoke(Method.java:597) com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71) com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java: 172) com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java: 337) com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java: 218) com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java: 136) com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java: 561) com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java: 269) com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java: 91) com.google.gwt.core.client.impl.Impl.apply(Impl.java) com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213) sun.reflect.GeneratedMethodAccessor345.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25) java.lang.reflect.Method.invoke(Method.java:597) com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71) com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java: 172) com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java: 292) com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java: 546) com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java: 363) java.lang.Thread.run(Thread.java:680) from sourceClasscom.google.web.bindery.event.shared.UmbrellaExceptionwith exception com.google.web.bindery.event.shared.UmbrellaException: One or more exceptions caught, see full set in UmbrellaException#getCauses -- 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/-/r-_YNz5nAWgJ. 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: RequestFactory Error -- java.lang.IllegalArgumentException: Something other than a Java object was returned from JSNI method
I've been seeing something similar for ages. My code isn't anywhere in this stack trace. I have no idea what to do. I'll report it. java.lang.IllegalArgumentException: Something other than a Java object was returned from JSNI method '@com.google.gwt.core.client.impl.Impl::apply(Ljava/lang/Object;Ljava/lang/Object;Ljava/lang/Object;)': JS value of type boolean, expected java.lang.Object at com.google.gwt.dev.shell.JsValueGlue.get(JsValueGlue.java:178) at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:271) at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91) at com.google.gwt.core.client.impl.Impl.apply(Impl.java) at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213) at sun.reflect.GeneratedMethodAccessor181.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71) at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172) at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:292) at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:546) at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:363) at java.lang.Thread.run(Thread.java:619) Ryan On Wednesday, April 25, 2012 10:14:04 PM UTC-5, Pradeep B Pillai wrote: The following is the other error i get frequently and this seems like its more related to request factory and I dont know why its happening ..Should I open a bug ? I'm using GWT 2.4, browser Chrome 18.0.1025.1065 One or more exceptions caught, see full set in UmbrellaException#getCauses - CAUSE java.lang.IllegalArgumentException: Something other than a Java object was returned from JSNI method '@com.google.web.bindery.autobean.gwt.client.impl.ClientPropertyContext $Setter::beanSetter(Lcom/google/web/bindery/autobean/shared/impl/ AbstractAutoBean;Ljava/lang/String;)': JS value of type boolean, expected java.lang.Object java.lang.IllegalArgumentException: Something other than a Java object was returned from JSNI method '@com.google.web.bindery.autobean.gwt.client.impl.ClientPropertyContext $Setter::beanSetter(Lcom/google/web/bindery/autobean/shared/impl/ AbstractAutoBean;Ljava/lang/String;)': JS value of type boolean, expected java.lang.Object STACKTRACE : com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext $StandardPayloadDialect.processPayload(AbstractRequestContext.java: 387) com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext $5.onTransportSuccess(AbstractRequestContext.java:1108) com.google.web.bindery.requestfactory.gwt.client.DefaultRequestTransport $1.onResponseReceived(DefaultRequestTransport.java:136) com.citrix.ws.democenter.module.shared.client.requestfactory.DemoCenterRequestTransport $1.onResponseReceived(DemoCenterRequestTransport.java:84) com.google.gwt.http.client.Request.fireOnResponseReceived(Request.java: 287) com.google.gwt.http.client.RequestBuilder $1.onReadyStateChange(RequestBuilder.java:395) sun.reflect.GeneratedMethodAccessor352.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25) java.lang.reflect.Method.invoke(Method.java:597) com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71) com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java: 172) com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java: 337) com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java: 218) com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java: 136) com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java: 561) com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java: 269) com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java: 91) com.google.gwt.core.client.impl.Impl.apply(Impl.java) com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213) sun.reflect.GeneratedMethodAccessor345.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25) java.lang.reflect.Method.invoke(Method.java:597) com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
Re: GWT ui:style how big of a bad idea (or not) is it to use it?
I don't use JQuery, and I can't see a reason why you would. JQuery is
Javascript, which brings you back into the world of not having your code
compiled until you (or worse your user) executes it.
If you really want to use JQuery for something, you can always us the
@external flag. Then it won't get obstruficated.
http://code.google.com/p/google-web-toolkit/wiki/CssResource#External_and_legacy_scopes
Ryan
On Saturday, August 4, 2012 9:40:23 AM UTC-5, Nuno Godinho de Matos wrote:
Hi,
I am wondering how big a mistake is it to take advantage of the ui:style
feature in ui binder interfaces?
Say your styles are all comprised within ui:style tags, and you always
refer to them using the {style.} notation.
Now, on the browser, this shall all become obfuscated after
gwt:compilation, the style name are not recognizable.
If we were to follow this approach for every style used on the
application, wouldn't we also lose the potential of navigating the page dom
with css selectors for example using library such as the Jquery gwt wrapper?
What's the policy here?
One should never depend on the defined style names for executing, say,
presentation logic such as collapsing dom elements?
--
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/-/vDlEbkLHFNMJ.
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.
