Security vulnerability in GWT 2.4: what's this?
I read in the 2.5 release notes here: https://developers.google.com/web-toolkit/release-notes#Release_Notes_Current Security vulnerability from 2.4 to 2.5 Final The GWT team recently learned that the Security vulnerability discovered in the 2.4 Beta and Release Candidate releases was only partially fixed in the 2.4 GA release. A more complete fix was added to the 2.5 GA release. If you have an app that's been built with GWT 2.4 or one of the 2.5 RCs, then you'll need to get the latest 2.5 release, recompile your app, and redeploy. I can't find any recent announcement of a security vulnerability or related posts in the group. Is there some information around about what this issue is? Having some applications in production with 2.4 we want to decide whether to wait for the Eclipse update or not. Thank you all Lorenzo -- 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/-/Q-gfSXgRxc8J. 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: Security vulnerability in GWT 2.4: what's this?
Thanks Thomas, I meant Eclipse Plugin (we develop and compile using Eclipse and update GWT version with the plugin - managing update by hand lead to some trouble with out-of-date jars found in some builds). The real problem is not the plugin availability (just updated) but the couple of days to go through compiling and deploying all apps, so we wanted to know which ones to recompile first *and* if the vulnerability depended on some features of GWT not used in our applications - so we can skip the upgrade for them. I appreciate the caution of the team, still believe that knowing exactly what is vulnerable helps everyone schedule a faster update if it's really needed. Thanks for your collaboration. Regards Lorenzo On Monday, November 12, 2012 5:45:25 PM UTC+1, Thomas Broyer wrote: On Monday, November 12, 2012 2:44:17 PM UTC+1, l.denardo wrote: I read in the 2.5 release notes here: https://developers.google.com/web-toolkit/release-notes#Release_Notes_Current Security vulnerability from 2.4 to 2.5 Final The GWT team recently learned that the Security vulnerability discovered in the 2.4 Beta and Release Candidate releases was only partially fixed in the 2.4 GA release. A more complete fix was added to the 2.5 GA release. If you have an app that's been built with GWT 2.4 or one of the 2.5 RCs, then you'll need to get the latest 2.5 release, recompile your app, and redeploy. I can't find any recent announcement of a security vulnerability or related posts in the group. Is there some information around about what this issue is? It's always delicate to disclose the details of security issues when you know that some people (including high-traffic apps) still use the vulnerable version. However a git log --grep security gives http://code.google.com/p/google-web-toolkit/source/detail?r=10458, and there indeed are other changes to these 2 files between 2.4 and 2.5. Only people with the GWT DevMode plugin installed are at risk of XSSI here. An example of what was *fixed* in 2.4: Having some applications in production with 2.4 we want to decide whether to wait for the Eclipse update or not. What does Eclipse has to do with 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/-/5V6cFEfkKMgJ. 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 in Same WAR File
I don't know what server-side technology you use, but I guess there's something similar to Spring Mobile (http://www.springsource.org/spring-mobile) in any framework of your choice. That allows you to detect the user agent on the server side and serve the optimized version of the UI simply rendering the correct view (i.e. a different page, or a page including a different javascript). Mobile and desktop apps are simply included in different pages. The GWT showcase uses a different approach, if I understood it correctly, serving the same javascript (in the same page, of course) to the client in both cases and then switching the view directly on the client (plus, code splitting optimizes performance so only the correct version is really downloaded). This can be used if your app is entirely GWT, but I guess it cannot handle a mobile UI built with a different technology like JQuery. Regards Lorenzo On Thursday, August 30, 2012 1:37:57 AM UTC+2, jduffy wrote: Hi All, We are developing a GWT application for desktop browsers that is deployed to a Tomcat 7 container as a WAR file. We are also developing a companion mobile application that is written in JavaScript and JQuery. We would now like to embed both applications into the same WAR file so that the appropriate version is served based on the user-agent property of the browser. For example, if a user hits 'ourapp.com' from a desktop browser, they should be served the GWT application and if they hit it from mobile Safari on an iPhone, they should get the JavaScript/JQuery application. Can anyone shed some light on how we might be able to accomplish this? We're fairly new to GWT and web programming so I apologize if the question is a bit vague or non GWT specific. Jim -- 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/-/qSGeJ4TquLQJ. 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 - dev environment ...
I'm also on Ubuntu since 10.10 with regular upgrades. Latest install is a 64 bit 12.04 + eclipse 3.7 indigo, no Unity (I prefer the traditional menus). I don't use WindowBuilder and GWT Designer, still I recommend having 8GB RAM to work without hassle, 4GB tend to get slow. Don't even think about using Eclipse or NetBeans with 2GB RAM, The problem isn't GWT per se, but the fact that Eclipse goes up to 1.2GB used RAM, Tomcat and GWT code server (I use an external server with the -noserver option in DevMode) 750MB each, so 4GB tend to be a little scarce. Regards Lorenzo On Friday, July 13, 2012 11:19:20 AM UTC+2, Nick Floros wrote: Hi, I have been evaluating GWT as a development framework in building a call handling application; maybe this is nuts idea but this is another story. It has been going kind of ok up to the point where my eclipse started running out of memory ; host os is Windows XP 32 bit. In addition corporate PC are full of anti-virus software which makes compilation and opening WindowsBuilder design a bit of a pain. So have been considering using 64 bit LINUX; in an attempt to avoid all the av software. Does anybody out there has any recommendations about which version of LINUX 64 bit and eclipse go together with GWT and WindowBuilder ? Been trying (admittedly on a VM) - Ubuntu 12.04 (32bit + 64bit) + eclipse 3.7 no joy tried also eclipse 4.2 - Mint Linux Cinnamon I get only a working environment but only with eclipse 3.6 - OpenSuse + eclipse 3.7 works when using standard GWT widgets. Any attempt to use GWT-EXT results in eclipse death. Any suggestions will be appreciated. Thanks Nick -- 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/-/UROBoRqe1GMJ. 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 make an (load)image overlay an panel
Two simple ptions (forgive me if they're too basic): *Your widgets to be activated are likely FocusWidgets: simply register them in a collection while you build your GUI and iterate over that to activate-deactivate them all *Use a (modal, if you don't want the background to be clickable) PopupPanel or DialogBox with the load image you prefer: set a primary style name to the widget using setStylePrimaryName(String name), add that to your CSS and adust the CSS properties to have no border and a transparent background, then center() / hide() your popup before and after load. regards Lorenzo On Apr 24, 1:26 pm, tanteanni tantea...@hotmail.com wrote: thx but i need complete deactivation of specific widgets - so this i have to do manually? Since i don't use uiBinder how would such an view look like written in java ? On Tuesday, 24 April 2012 13:20:42 UTC+2, Jens wrote: in my app i have some interactive widgets but while loading data from server this widgets must be inactivated and activated again after loading is complete. i don't want to make the widgets invisible or inactivate every single field/button. the best solution would be a transparent panel with an loading image in its center or corner overlaying the widgets while loading - but how to achieve that? If you only want to overlay specific parts of your app (a complete overlay would be a PopupPanel with glass panel active), I would probably create a simple UiBinder view based on HTML (give it an absolute position with top,left,bottom,right being 0) and then just append/remove it to/from the appropriate parent element. The parent element should have a position:relative applied. But this only will disallow mouse events.. you can still tab through the controls and activate them using the keyboard I think. -- J. -- 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: Serialization Error
Moreover, Set, just like List, Object etc. is NOT Serializable. If the interface does not extend Serializable, a serialization error is thrown. The fact of Set not being serializable is all but obvious, I think we all forgot this problem with RPC. Btw, this behavior is documented (in a couple of lines at the bottom of https://developers.google.com/web-toolkit/doc/latest/DevGuideServerCommunication#DevGuideSerializableTypes) but interface based RPC worked fine, despite documentation stating the opposite, until 2.2 i guess, so some of your applications may just step into this problem when you update your GWT release. Regards Lorenzo On Apr 13, 5:15 pm, Philippe Lhoste phi...@gmx.net wrote: On 13/04/2012 09:08, Vincenz M ssenb ck wrote: private SetBestellpositionDTO alBestellpositionDTO; One of the first advices I got for making DTOs is to avoid using interfaces in them. GWT will try and generate JavaScript for all the interface implementations it can find in the classpath, which is rather costly, and can fail if it finds a non-serializable implementation... In short, use HashSet or similar instead of Set. -- Philippe Lhoste -- (near) Paris -- France -- http://Phi.Lho.free.fr -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 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 history handling library - give it a try
You're partly right in my opinion. What I exposed is (part of) a (siplified) library approach VS the typed, Place approach. A Place is an Object Oriented representation of a client side URL, tied to your browser history, and offers you typed methods to have in an object oriented way all the parameters (from the URL) you need to have to restore your objects' state correctly, and to save them to an URL. To have an efficient serialization the recommended approach is to have a base Place with its tokenizer, i.e. one class handling serialization and deserialization from and to your URL, then extend it. It's just the matter to write a single serialization/deserialization class (or a library, if you prefer). The point is that all this comes in standard GWT, so looks like there's no need to develop a separate library to do exactly the same. regards Lorenzo On Apr 3, 11:58 am, Kostya Kulagin kkula...@gmail.com wrote: Thank you for a response. If I understood you correctly - you propose some kind of Place which will contain props of all components. (sorry if I misunderstood you) Personally myself don't like this solution. Place has nothing to do with its components state. When writing an application I don't want speak on a language of params in URL, parsing those and update state of components. I want to speak on a Object language. My object has a state - it saves it, it restores it. Serialization is a lib's job. This is an idea. thanks! On 2 avr, 11:33, Kostya Kulagin kkula...@gmail.com wrote: So, for me to resume (my opinion): 1) Using components state for bookmarks is a bad idea - URL should contain only 'Place' information. If you need to have an ability to bookmark state different then initial page state - use different Place. As an example - if in a gmail I want to have a shortcut to some of my favorite folders (for example:https://mail.google.com/mail/#label/hello_thomas;-) )- this is rather different Place, not a state of all Components on a page. 2) For a history navigation probably it would be better to have some key generated. Components states should be stored under that key (either in cookies or in HTMLs 5 browser cache) 3) If an application does not use Places and Activities - I should think what to do in that case. Will make necessary updates, though. thanks! On 30 mar, 17:09, Thomas Broyer t.bro...@gmail.com wrote: On Friday, March 30, 2012 3:49:11 PM UTC+2, Kostya Kulagin wrote: What you'll have to do to be assured that sub-params (or there is an other way to do it?) in the browser history string does not intercept? Create a specific Place that can hold those two parameters and navigate from place to place, changing only one value at a time? If you want to decouple your pagers from the places then, well, abstract that out behind some navigator component that'll manage the places for you (e.g. moveSecondPager(2) would navigate to a place with the same value for the first pager and the value 2 for the second pager; the second pager doesn't need to know about that). This is a bad approach from my point of view (see big comment above). Place should not depend or know anything about components inside of it. It is mostly like marker. A Place is a type-safe representation of the URL. No more, no less. If you want to put something in the URL, then put it in a Place and have a PlaceTokenizer transform it to your URL (and back when navigating to the URL, either through a bookmark, link, or browser history). As I said, there might be cases where you want some history entries to change the URL and some others that won't (but honestly, I still cannot find any use case). In that case, I'd investigate HTML5's pushState to see if it supports the use case, and if it does then simply punt for browsers that don't support it (only handle the case where it changes the URL, i.e. true navigation, not intermediate state). I believe it'd be possible to mix a hidden iframe hidden state change and manipulating the URL's #hash for navigation, I'm really not sure it's worth it = use pushState and let oldIE users with a not as good experience as others (and possibly have them installChrome Frame, so you could use pushState). And I still strongly believe that if you have two truly independent things on a page, only one should affect the browser history, or you have a serious design issue (Er, I clicked the back button 3 times, now if I click it once more, will it change the left side or the right side of the screen?). That was the main issue with frames (apart from addressability, i.e. bookmarkability), that are now officially dead (as in:http://www.w3.org/TR/html5/obsolete.html#frames) Of course, YMMV. -- You received this message because you are subscribed to the Google Groups Google
Re: GWT history handling library - give it a try
To be clear, I looked into your library. If I understand it correctly what you do (just like in the sample I posted above) is to map an URL from/to a ComponentState, which has a representation of the state of the object as a MapString, String. Your ComponentState is at last a wrapper of the string map. A Place is similar in concept, with the difference that you don't have just a MapString, String but a series of methods to have the properties with their correctly typed class. The ComponentStateSerializer builds an history token using that map, or breaks your current history token to the map. This is the same as a PlaceTokenizer will do, with the difference that the PlaceTokenizer returns a Place, which is a typed object and has typed accessors. Your library is very similar tho the one I developed when Places were not in GWT, and if you look at my code above you'll notice it's similar to your DefaultComponentStateSerializer.toHistoryString(ComponentState ), the only difference being some more configuration options for yours. Just spend a couple of hours trying out the Places tutorial Thomas Broyer posted and you'll immediately see the benefits of Places over the approach you are using (which is not bad: I used it succesfully for a long time. Places do the same, but better :-)) Regards Lorenzo On Apr 3, 5:58 pm, Kostya Kulagin kkula...@gmail.com wrote: Thank you for a response. If I understood you correctly - you propose some kind of Place which will contain props of all components. (sorry if I misunderstood you) Personally myself don't like this solution. Place has nothing to do with its components state. When writing an application I don't want speak on a language of params in URL, parsing those and update state of components. I want to speak on a Object language. My object has a state - it saves it, it restores it. Serialization is a lib's job. This is an idea. thanks! On 2 avr, 11:33, Kostya Kulagin kkula...@gmail.com wrote: So, for me to resume (my opinion): 1) Using components state for bookmarks is a bad idea - URL should contain only 'Place' information. If you need to have an ability to bookmark state different then initial page state - use different Place. As an example - if in a gmail I want to have a shortcut to some of my favorite folders (for example:https://mail.google.com/mail/#label/hello_thomas;-) )- this is rather different Place, not a state of all Components on a page. 2) For a history navigation probably it would be better to have some key generated. Components states should be stored under that key (either in cookies or in HTMLs 5 browser cache) 3) If an application does not use Places and Activities - I should think what to do in that case. Will make necessary updates, though. thanks! On 30 mar, 17:09, Thomas Broyer t.bro...@gmail.com wrote: On Friday, March 30, 2012 3:49:11 PM UTC+2, Kostya Kulagin wrote: What you'll have to do to be assured that sub-params (or there is an other way to do it?) in the browser history string does not intercept? Create a specific Place that can hold those two parameters and navigate from place to place, changing only one value at a time? If you want to decouple your pagers from the places then, well, abstract that out behind some navigator component that'll manage the places for you (e.g. moveSecondPager(2) would navigate to a place with the same value for the first pager and the value 2 for the second pager; the second pager doesn't need to know about that). This is a bad approach from my point of view (see big comment above). Place should not depend or know anything about components inside of it. It is mostly like marker. A Place is a type-safe representation of the URL. No more, no less. If you want to put something in the URL, then put it in a Place and have a PlaceTokenizer transform it to your URL (and back when navigating to the URL, either through a bookmark, link, or browser history). As I said, there might be cases where you want some history entries to change the URL and some others that won't (but honestly, I still cannot find any use case). In that case, I'd investigate HTML5's pushState to see if it supports the use case, and if it does then simply punt for browsers that don't support it (only handle the case where it changes the URL, i.e. true navigation, not intermediate state). I believe it'd be possible to mix a hidden iframe hidden state change and manipulating the URL's #hash for navigation, I'm really not sure it's worth it = use pushState and let oldIE users with a not as good experience as others (and possibly have them installChrome Frame, so you could use pushState). And I still strongly believe that if you have two truly independent things on a page, only one should affect the browser history, or you have a
Re: GWT history handling library - give it a try
--3) If an application does not use Places and Activities - I should
think what to do in that case.
I just stepped into reworking an application that used a custom
history mapper (developed before places were available) to a Places
design, so here's what I found.
If you don't use Places, you'll go and use GWT native history support
(https://developers.google.com/web-toolkit/doc/latest/
DevGuideCodingBasicsHistory) building an HistoryToken based on your
object properties, and viceversa.
This is a sample from my own code
private MapString, String parseHistoryToken(String token){
MapString, String properties = new HashMapString, String();
if (!token.startsWith(MAIN_LBL + /))
return properties;
String toParse = token.substring(MAIN_LBL.length() + 1,
token.length());
String[] propList = toParse.split(/);
for (int i = 0; i propList.length; i++){
String property = propList[i];
if (property.length() 3)// il controllo serve perché
il primo
// split ritorna un array con una
// stringa vuota e non un array vuoto
continue;
String[] values = property.split(=);
//nella history il valore null è salvato come stringa
== null
String value = (values[1].equals(null)) ? null :
values[1];
properties.put(values[0], value);
}
return properties;
}
It will cut a history token like #home/prop1=123/prop2=zaq into a map
like prop1, 123, prop2, zaq, and map.get(prop1) will return a
String 123.
This is *exactly* what a PlaceTokenizer and a PlaceHistoryMapper will
do, except for the fact that you can then access your HistoryToken
properties in a type safe way (i.e. you'll call some methods on your
Place).
You'll write a PlaceTokenizer to build sort of a CustomPlace, and call
( (CustomPlace) PlaceController.getWhere()).getProp1().
The *huge* difference is that getProp1() can return a type (String,
Integer, CustomObject etc.) and once you defined a tokenizer from your
place to the URL and viceversa this will work correctly.
This means getPlace1() will return the Integer 123, not a String, and
if you build a bad URL you'll get (and handle) a meaningful
exception.
If you try to dig into the Places tutorial Thomas Broyer linked before
you'll find out that this is the behavior you get.
So if you don't use places, but want a good history support, the best
way is, er, go for Places :-) You don't need Activities for history
support, using Places, a PlaceHistoryMapper and listening to
PlaceChangeEvent will do a top class history support by themselves.
Again, the article mentioned above is a clear and helpful starting
point, just try to code a simple use case.
Regards
Lorenzo
On Apr 2, 10:33 am, Kostya Kulagin kkula...@gmail.com wrote:
So, for me to resume (my opinion):
1) Using components state for bookmarks is a bad idea - URL should
contain only 'Place' information. If you need to have an ability to
bookmark state different then initial page state - use
different Place. As an example - if in a gmail I want to have a
shortcut to some of my favorite folders (for
example:https://mail.google.com/mail/#label/hello_thomas;-) )- this is rather
different Place, not a state of all Components on a page.
2) For a history navigation probably it would be better to have some
key generated. Components states should be stored under that key
(either in cookies or in HTMLs 5 browser cache
3) If an application does not use Places and Activities - I should
think what to do in that case.
Will make necessary updates, though.
thanks!
On 30 mar, 17:09, Thomas Broyer t.bro...@gmail.com wrote:
On Friday, March 30, 2012 3:49:11 PM UTC+2, Kostya Kulagin wrote:
What you'll have to do to be assured that sub-params (or there is an
other way to do it?) in the browser history string does not intercept?
Create a specific Place that can hold those two parameters and
navigate
from place to place, changing only one value at a time?
If you want to decouple your pagers from the places then, well, abstract
that out behind some navigator component that'll manage the places for
you (e.g. moveSecondPager(2) would navigate to a place with the same
value
for the first pager and the value 2 for the second pager; the second
pager doesn't need to know about that).
This is a bad approach from my point of view (see big comment above).
Place should not depend or know anything about components inside of
it. It is mostly like marker.
A Place is a type-safe representation of the URL. No more, no less. If you
want to put
Using non disposable activities extracting parameters from a place
Hello, I'm facing a problem with activities and places. My use case is quite simple. I have more kind of places in my app (e.g. CalendarPlace and ResourcePlace). Each place can contain the ID of a given object. When I switch place I want to load the correct editor for the kind of object (switching if place type has changed) AND init it with the correct value. I use two activities to accomplish this. CalendarActivity and ResourceActivity. My ActivityMapper selects the correct kind, extracts the object ID from the current Place and sets it on the correct Activity, then returns it. I load the details of the object on each activity's start(...) method. My problem is that the two activities are actually singletons (not- disposable), since they have different dependencies injected through GIN. In this case the ActivityManager (line 114) does NOT fire a start(...) on the activity after the place has changed. My place switch works fine when activity kind changes, but not when the activity is the same but objectId has changed. i.e calendar13 -- resource 14 is fine, and resource14 is loaded resource14 -- resource15 is not: start is not called so resource15 is not loaded I wonder what is the best way to have a correct state change when place chages occur. *Build a GIN provider or the like for activities and have a different Activity object returned each time *Do the new object loading immediately when the ActivityMapper calls the setter instead of the start(...) method *Any other way? I noticed things can be mixed reading http://groups.google.com/group/google-web-toolkit/browse_thread/thread/d827400bda6b996b/4367bbcc2d36aa5c?lnk=gstq=reuse+activity#4367bbcc2d36aa5c but I wonder if there's a suggested way to work around this. Thanks for your help Lorenzo -- 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: Using non disposable activities extracting parameters from a place
Thank you Thomas! I ended up doing something similar to what you say, moving GIN injected dependencies into my ActivityMapper and using them to build a new Activity (I'll switch to a provider as soon as possible). I actually ended up subclassing ActivityManager (and extending Activity itself) to provide a different switching behavior, since I had some needs for optimization. Maybe I'll go back to the default as I clean up my own code using the Places/Activity architecture (I'm on an hand-made MVP, with no place tight behavior, by now). Thanks very much for your collaboration (and of course for your blog posts on the whole framework, I found them way clearer than the official documentation on this matter). Regards Lorenzo On Feb 23, 3:15 pm, Thomas Broyer t.bro...@gmail.com wrote: On Thursday, February 23, 2012 1:22:38 PM UTC+1, l.denardo wrote: My problem is that the two activities are actually singletons (not- disposable), since they have different dependencies injected through GIN. If this is the only reason, then it's not a good reason. It's too easy to not use singletons with GIN to not take advantage of it: replace your dependency on CalendarActivity to a dependency on ProviderCalendarActivity in your ActivityMapper (same for ResourceActivity) and you're done, and you'd have eliminated your issue at the same time. I wonder what is the best way to have a correct state change when place chages occur. *Build a GIN provider or the like for activities and have a different Activity object returned each time Definitely (unless you have a good reason to do otherwise) *Do the new object loading immediately when the ActivityMapper calls the setter instead of the start(...) method *Any other way? Tracker whether the activity is started or not (as I said on some other similar thread in the past few weeks, this is something you should already be doing anyway IMO) to determine what to do when the setter is called: either wait for the activity to be started, or start loading the data right away if the activity is already live and running. -- 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: changing pages in GWT
You can start from this article in documentation: http://code.google.com/webtoolkit/articles/dynamic_host_page.html It's quite simple to convert it from the basic servlet/jsp example to anything you're using on the server side. Regards Lorenzo On Feb 4, 12:19 pm, nofear adnba...@gmail.com wrote: Hello , i'm currently developing an exam project but i'm kind of started to GWT. So here's my question : I have a log in page which asks username and password to log in for students or teachers. After confirmation the informations of students or teachers, i would like to redirect user to his proper page (i mean change the log-in page to his proper page) , basicly i didn't understand how can i do that after clicking the CONFIRM button. Thanks for all help. -- 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, please don't ignore reported GWT issues.
Some time ago I stepped into the issue lifecycle wiki page. http://code.google.com/p/google-web-toolkit/wiki/BugTriageProcess http://code.google.com/p/google-web-toolkit/wiki/ManagingMerges Maybe this can clarify some things about why issues are not updated (looks like most of times this is an expected behavior). And yes, I agree this information should be more visible to people reporting issues :-) Regards Lorenzo On Oct 5, 9:41 am, stuckagain david.no...@gmail.com wrote: I have been frustrated with this as well and voiced my concern before. But all they keep on doing is adding features that most of us don't need. GWT is great, but there is a lot of old stuff in there that is half baked and nobody in the GWT team seems to be concerned with actually fixing bugs. When I complained about it the only answer (if any) I get is: you are free to send us a patch. Most of us don't have the time, or even the right to spend our time on working on code for google during our day jobs. And in the evening we need to take care of our family so fixing anything taking more than a few lines of code is totally impossible. I managed to patch one of the issues I reported, but some things are hard to fix unless you really know the GWT internals very well. There is a bug in the Event dispatching after opening a popup in IE and I really don't know how to fix this one since it goes really deep into the root event handling implementation. There is no developer docs available that explains the architecture and the devs that created the code in the first place are doing other things. I filed the bug report, I wrote in GWT and GWT contrib newsgroups and got 0 responses... This is the one:http://code.google.com/p/google-web-toolkit/issues/detail?id=4938 From what I read on google culture it seems like you only get rewarded for writing new stuff, not fixing old stuff (unless it affects a google product launch). -- 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: Changing app from one gwt version to another version problem
Hello, gwt-servlet.jar contains server-side RPC classes, and must be changed whenever you change client side implementation. If you don't you'll likely get Incompatible remote service exceptions. Up to 2.3 the plugin did not give any warning, now it does and it's one of the most useful features in my opinion. To keep things working simply delete gwt-servlet.jar from your lib directory and replace it with the one from the 2.4 sdk (you can search for it in the Eclipse plugins directory if you did the update via Eclipse). Then clean your project and gwt-compile before you start using devmode. I hope this will be automated by future plugin versions. Regards Lorenzo On Sep 16, 9:31 am, mallikarjun@gmail.com mallikarjun@gmail.com wrote: Hi previously i am using GWT 2.3 now i am using GWT 2.4 i coppied my app from 2.3 to 2.4 it shows some errors like below. couls u plz help me when any body know. The file war\WEB-INF\lib\gwt-servlet.jar has a different size than GWT SDK library gwt-servlet.jar; perhaps it is a different version? gwt- servlet.jar /Welcome/war/WEB-INF/lib Unknown Google Web Toolkit Problem Thanks and Regards in advance -- 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: google plugin/build deletes .svn directory in src/main/webapp
Are you using GWT in an Eclipse Web project? If so you must *closely* follow the directions here: http://code.google.com/eclipse/docs/faq.html#gwt_in_eclipse_for_java_ee This means you must: *Turn off the deploy from this directory option *Point the -war directory for your devmode to the *temporary* server directory used by eclipse. Then when you compile Eclipse will ask you where your real war directory is and compile into it. If you use your real war directory with the plugin in a web project, any time you start GWT devmode your war directory will be cleared and gwt plugin will recreate it without hidden directories like the .svn. I had the same issue and solved it by pointing the devmode war directory as stated in the faq linked above. Also be careful that the -war option for devmode will be resetted when you upgrade your plugin, so you'll have to correct it by hand. Hope this can be helpful. Regards Lorenzo On Aug 4, 10:47 am, Eugen Paraschiv hanrisel...@gmail.com wrote: Something like that, yes. Where should the '-war foldername' be specified? I do indeed have it active on my run configurations, but the actual Eclipse builder that's running in the background is the one that is likely responsible with the removal of the svn dirs. I also have the war directory correctly specified in the properties of the project, under Google - Web Application, but when configuring a new Eclipse workspace, that option may very well be configured minutes later, when the Eclipse builder may already have removed the svn directories (which is what just happened to me). What I'm not clear about is what does the plugin have to do with the svn directories? Why does it touch these directories in the first place? Thank you for the help and the quick response. Eugen. On Thu, Aug 4, 2011 at 11:31 AM, Michael Vogt vmei...@googlemail.comwrote: Hello This is a critical problem - the plugin simply removes the .svn directories, completely messing up the entire workspace - everything below webapp is now unversioned and shown to be committed. Is there any feedback on this? Do you mean that when you compile your application, everything inside the module folder is replaced? We solve this with the additional compiler argument '-war foldername'. That way the compiled files are saved in the specified folder. Hope I understood you correctly, 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-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: google plugin/build deletes .svn directory in src/main/webapp
I'm glad to hear it helped. I agree having this setup is a bit cumbersome and the whole process could be smarter. Anyway it looks like it's just devMode behavior, and I'm happy to have a complete development environment despite these little quirks. I think an update to documentation to better explain WHY you should not point your war directory to the actual war, and a better evidence of the correct setting in the guide, should be the optimum solution. Regards Lorenzo On Aug 4, 12:57 pm, Eugen Paraschiv hanrisel...@gmail.com wrote: About the war option, I am using it, only I was pointing it to my actual war directory and not a temporary one. Thanks for the help. Eugen. On Thu, Aug 4, 2011 at 12:12 PM, Michael Vogt vmei...@googlemail.comwrote: Something like that, yes. Where should the '-war foldername' be specified? When you click the red folder button in the toolbar of eclipse to compile a project, you find an advanced area in the dialog that is shown. There you have the additional compiler argument area to add the -war switch. I do indeed have it active on my run configurations, but the actual Eclipse builder that's running in the background is the one that is likely responsible with the removal of the svn dirs. I also have the war directory correctly specified in the properties of the project, under Google - Web Application, but when configuring a new Eclipse workspace, that option may very well be configured minutes later, when the Eclipse builder may already have removed the svn directories (which is what just happened to me). What I'm not clear about is what does the plugin have to do with the svn directories? Why does it touch these directories in the first place? Sorry, can't help here, since I have not seen this problem in my projects (which are also store in svn. Thank you for the help and the quick response. You're welcome. Greetings, 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-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.
Firefox plugin incompatible with 5.0
Hello, I just upgraded my firefox version on Ubuntu and dev mode plugin has been disabled since it's incompatible with firefox 5.0. My settings: ubuntu 11.04 natty firefox 5.0 Google Web Toolkit plugin 1.0.9863 Hope this is just a version check goin' wrong...Please let me know if some more diagnostics or configuration information is needed, I'll be glad to provide it. Regards Lorenzo -- 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: Firefox plugin incompatible with 5.0
Thank you very much, I searched too fast and missed it... No good news so, since mozilla ppa repository version is now at version 7, so we'll expect some delay for the future between FF and plugin changes. Anyway going back to FF 3.6 (4.0 package download disappeared) seems the fastest thing to do. Thanks for your collaboration. Regards Lorenzo On Jun 23, 10:59 am, Dominique L. dom@gmail.com wrote: Please, see this thread : http://groups.google.com/group/google-web-toolkit/browse_thread/threa... -- 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: UmbrellaException
You can call GWT.setUncaughtExceptionHandler(GWT.UncaughtExceptionHandler handler) to add a catch all exception handler in your code. Then take a look at GWT logging capabilities (outlined from previous poster) to print to console, log to server, etc. This saved me from an IE debugging nightmare... Regards Lorenzo On Apr 20, 5:40 pm, tjmcc18 tjmc...@gmail.com wrote: When an unexpected error occurs on the client side, such as a NullPointerException, the result is that an UmbrellaException is thrown and that generally ends up being interpreted as a javascript error by the browser. Those javascript errors are usually less than helpful in determining what the actual problem was. Does anyone have any suggestions on how to handle the case of unexpected errors? Can you put a try catch block at the top level of you app as kind of a catch all? If so, what should be done with these exceptions? Should they be sent back to the server to be logged somehow? If not, how can you try to provide some useful information to help with the debugging process? -TJ -- 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.
Incompatible RPC upgrading to 2.2 - serialization policy?
Hello, I'm currently facing an issue while upgrading to gwt 2.2. My application uses spring on server side, and gwt dispatch for communication. Strack trace is SEVERE: Exception while dispatching incoming RPC call java.lang.NullPointerException at javax.servlet.GenericServlet.getServletName(GenericServlet.java: 238) at javax.servlet.GenericServlet.log(GenericServlet.java:204) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java: 211) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java: 243) at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java: 62) at it.miriade.planner.server.service.BaseRemoteService.handleRequest(BaseRemoteService.java: 25) etc. This issue (I faced it in the past) is due to new compilation of GWT modules, and subsequent variation in serialization policy files, which make the old rpc service incompatible with the new compiled module. I noticed that GWT 2.2 compiles some files under WEB-INF/deploy/ which look related to serialization policy, and so to this bug. What I need to know is how this output folder can be configured, and if there's a workaround to make the policy files easily accessible (taking them out of WEB-INF if this is not an issue). Or maybe if this incompatibility is due to other issues. Thanks to everyone Lorenzo -- 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: Incompatible RPC upgrading to 2.2 - serialization policy?
Ok, solved... Just needed to upgrade my gwt-servlet.jar (the most obvious error :-)). Thanks anyway. Lorenzo On Feb 16, 3:47 pm, l.denardo lorenzo.dena...@gmail.com wrote: Hello, I'm currently facing an issue while upgrading to gwt 2.2. My application uses spring on server side, and gwt dispatch for communication. Strack trace is SEVERE: Exception while dispatching incoming RPC call java.lang.NullPointerException at javax.servlet.GenericServlet.getServletName(GenericServlet.java: 238) at javax.servlet.GenericServlet.log(GenericServlet.java:204) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java: 211) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java: 243) at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java: 62) at it.miriade.planner.server.service.BaseRemoteService.handleRequest(BaseRemoteService.java: 25) etc. This issue (I faced it in the past) is due to new compilation of GWT modules, and subsequent variation in serialization policy files, which make the old rpc service incompatible with the new compiled module. I noticed that GWT 2.2 compiles some files under WEB-INF/deploy/ which look related to serialization policy, and so to this bug. What I need to know is how this output folder can be configured, and if there's a workaround to make the policy files easily accessible (taking them out of WEB-INF if this is not an issue). Or maybe if this incompatibility is due to other issues. Thanks to everyone Lorenzo -- 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: Strict Mode - replacement for HorizontalPanel needed
AFAIK, if you use nested layout panels you must explicitly set the size of the container panel (i.e. your DockLayoutPanel) to 100%-100% (or whatever you want) to make the children visible, otherwise they will not show. I think there are some discussion about it in the groups, and I verified myself that explicit setting of the container size is most of the times the solution when children don't show at all. Regards Lorenzo On Dec 15, 6:21 am, Magnus alpineblas...@googlemail.com wrote: BTW: I found that DockLayoutPanel hase some LTR (left to right) mode. Could I use this for my purpose? I made a first try, replaced the FlowPanel by a DockLayoutPanel for the whole row, but my children were not visible at all... #-) Magnus -- 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: Strict Mode - replacement for HorizontalPanel needed
Hello, you could simply use a FlowPanel and set a float:left property. I did it, overriding the add(Widget w) method to recursively set the float on children of added widgets, and it proved to work well. Regards Lorenzo On Dec 14, 7:09 am, Hilco Wijbenga hilco.wijbe...@gmail.com wrote: On 13 December 2010 21:41, Jim Douglas jdou...@basis.com wrote: for strict mode I need a replacement for HorizontalPanel. Why? What's wrong with HorizontalPanel? http://code.google.com/webtoolkit/doc/latest/DevGuideUiPanels.html#St... HorizontalPanel is for quirks mode. -- 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: Strict Mode - replacement for HorizontalPanel needed
You're right, I read the op without the right attention. What I suggested works well if you just need to lay out your widgets in a row, as many button bars do. In that case the solution I suggest will work, and the bar will be truncated or wrap around if there's not enough space for all widgets, depending on layout, but natural wodget size won't be affected. A layout panel, the way you suggested, will certainly be better. Regards Lorenzo On Dec 14, 4:09 pm, Brian Reilly brian.irei...@gmail.com wrote: It's a bit more complicated than that, and you really have to look at the provided example in IE7 (not IE8, which works fine) to understand what's happening. From what I understand, you want to have 2 widgets, a text field and a button, displayed in a row. Your layout is fluid, so the width of the row adjusts with the width of the window. You want the button on the right to take up it's natural size based on the button text and the text field on the left to take up the remaining space available. Unfortunately, I'm not sure how to accomplish that. You may be able to get something to work by explicitly setting the width of the button's panel (em units would probably be best). I could imagine a DockLayoutPanel with an east panel containing the button and the center panel containing the text field. Set the width of both elements to 100% and the panel should constrain the sizes. Other than that, you may have to resort to doing some layout in code... measuring sizes and setting widths explicitly. -Brian On Tue, Dec 14, 2010 at 4:09 AM, l.denardo lorenzo.dena...@gmail.com wrote: Hello, you could simply use a FlowPanel and set a float:left property. I did it, overriding the add(Widget w) method to recursively set the float on children of added widgets, and it proved to work well. Regards Lorenzo On Dec 14, 7:09 am, Hilco Wijbenga hilco.wijbe...@gmail.com wrote: On 13 December 2010 21:41, Jim Douglas jdou...@basis.com wrote: for strict mode I need a replacement for HorizontalPanel. Why? What's wrong with HorizontalPanel? http://code.google.com/webtoolkit/doc/latest/DevGuideUiPanels.html#St... HorizontalPanel is for quirks mode. -- 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 athttp://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-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 and Internet Explorer
Also, if the page loads but is completely blank in IE, check that you don't have comments before the !DOCTYPE ... declaration. This is a very annoying bug in IE many people (including myself) got stuck into. Regards Lorenzo On Dec 9, 8:35 am, rjcarr rjc...@gmail.com wrote: The GWT will compile for IE by default so that shouldn't be your problem. If you open your page in IE and nothing is shown you likely have a javascript error. Your best bet is to run the app in devmode (using IE, of course) and see what errors are thrown. That should give you some direction as to what's going wrong. On Dec 8, 12:32 pm, Marcelo L marcelo.a.l...@gmail.com wrote: I've developed an app using GWT and work with Firefox, Chrome and Safari, but not with Explorer, I can´t make Explorer to load the GWT script. Is there any configuration (of javascript) that I have to set on Explorer for running my app? Is there any rules to consider? -- 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: GAE Channels API in GWT
Hello, I haven't looked thru that project, but I think that server side should be plain AppEngine stuff (docs came out a couple of days ago). The only thing for GWT should be a wrapper for the native javascript api, so nothing else should be needed. Google IO session for channel API is here: http://www.google.com/events/io/2010/sessions/building-real-time-apps-app-engine-feed-api. This features a usage example, a little old but should be a good starting point for use. I'm sorry I cannot give more help, I'll post more if I found out something useful. Regards Lorenzo On Dec 6, 10:12 pm, Andrea mariofut...@googlemail.com wrote: On 06/12/10 11:40, l.denardo wrote: This other project was linked by the App Engine team: http://code.google.com/p/gwt-gae-channel/ (discussion thread is http://groups.google.com/group/google-appengine-java/browse_thread/th...). Code should be derived from the DanceDanceRobots demo, which is explained in Google IO sessions. Regards Lorenzo This seems to be only client side. I was expecting something on the server side too. But maybe I did not understand how it works. Andrea -- 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: GAE Channels API in GWT
This other project was linked by the App Engine team: http://code.google.com/p/gwt-gae-channel/ (discussion thread is http://groups.google.com/group/google-appengine-java/browse_thread/thread/8cdf8e0a2276a9dd/fcb91bc1c62deb32?lnk=raot#fcb91bc1c62deb32). Code should be derived from the DanceDanceRobots demo, which is explained in Google IO sessions. Regards Lorenzo On Dec 5, 10:25 pm, Andrea mariofut...@googlemail.com wrote: Hi, after the recent release of GAE supporting push services via the Channels API I wonder what is the best way to use it a GWT application. I mean, the example given in GAE requires use of javascript (client side) and servlets (server side). Is the a pure java way, fully integrated in GWT? I've foundhttp://code.google.com/p/gwt-channel/but it does not look too active. Any other solution? Andrea -- 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: Oauth and open id
You're surely right for the OpenID part. If you use appEngine as a backend, see this article for details http://code.google.com/appengine/articles/openid.html, which uses Google as a provider (should work by simply replacing the provider endpoint for other providers). A well known general library is http://code.google.com/p/openid4java/. This should work well outside of appEngine, and has good tutorials for what I remember (I am on appEngine, so I switched tho their native support). I can't help for the oAuth part, sorry. Regards Lorenzo On Nov 2, 8:15 am, Fendy Tjin fendyt...@gmail.com wrote: Hi, I've searched all over the places, what I found is that, I need to redirect or forward to authenticate to Google account or other accounts. And it seems it required me to save the token. Am I in the right direction? Thank you, Fendy Tjin -- 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.
