Yeah I have it working like that already, but it's still unfortunate. Maybe
the best long term bet is to not use JSR 303 at all? It adds a bit more
boilerplate code though.
On Mon, Feb 10, 2014 at 3:51 PM, Jens jens.nehlme...@gmail.com wrote:
Slightly off topic, but do you know if the
Perhaps we could collect a small bounty (probably even 1k would be
enough?), and start a competition for the community to submit designs with
the best design being chosen by some judges.
On Wed, Jul 31, 2013 at 4:18 PM, salk31 sal...@gmail.com wrote:
They have typesafe behind them so
Hetzner is also very good if you need something with massive RAM (32gb+),
CPU(4 core i7) and disk space(2TB) for a low price:
http://www.hetzner.de/en/hosting/produkte_rootserver/ex40
They've been around for ages also, so expect good reliability.
Basically: Avoid AppEngine if you care about
Hi Thomas,
It would be great if you (or anybody who understands how to set it up)
could add a small article on gwtproject.org about setting up the different
methods of getting stack traces in production on exceptions?
Thanks!
Ryan
On Thu, Jul 18, 2013 at 3:30 PM, Thomas Broyer
Oh, my bad! I read posts from people that seemed to imply that they had
managed to get working stack traces using some method - but no matter what
I tried I couldn't get it to work. Is this likely to be fixed for the next
GWT release (or already fixed in git?), or still on the backburner?
On
According to that article it will work without Vaadin, and just requires
that you replace 'widgetset' with 'module'. How exactly you'd go about
doing that is unclear and I haven't tried, but the article definitely
seems to be saying that it should work without issue.
I've had plans to give it a
It's been (erroneously) merged into issue 8162, which is just a generic
CSS3 issue. So I wouldn't get your hopes up too quickly.
https://code.google.com/p/google-web-toolkit/issues/detail?can=2q=8162colspec=ID%20Type%20Status%20Owner%20Milestone%20Summary%20Starsid=8162
On Fri, Jun 14, 2013
There is a project for using Futures in GWT -
http://code.google.com/p/gwt-async-future/
However, an event bus is still a better pattern for this, as futures are
just nicer syntax for single async tasks, and what is needed here is a
method to de-couple the data calls so you don't need to be
