Re: How to override gwt styles in uibinder?

[V.B.]

Hi Thomas,
   In your post above you mention "@external .gwt-*;". You also use the 
same trick in 
this
 StackOverflow 
question. But, I have never been able to make that work. Instead I have to 
have @external for every gwt type that I need to override, which is quite a 
hassle. (Note: in your post above you don't have the leading period. I have 
tried it both ways just to be sure.)

When I try to use "@external .gwt-*;" I get errors of this flavor:
[ERROR]  Line 69: The annotation @CssResource.ClassName is disallowed for 
this location
[ERROR]  Line 70: Syntax error on token "*", delete this token

The generated lines in question look like this:
  @ClassName("gwt-*")
  String gwt*();

Am I doing something wrong?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to mark a field as completely hidden for smartgwt ListGrid?

[Gustavo Matias]

actullally,  

listGrid.hideField("my_field"); worked too, but I had to make sure this was 
set AFTER the field was added and its values set.

On Wednesday, January 4, 2012 5:04:23 AM UTC-5, Daniel wrote:
>
> Hi guys, 
>
> How to mark a field as completely hidden for smartgwt ListGrid? 
> I do listGridFields[i].setHidden(true) according to API,But it still 
> could be able to show the field via a context menu. 
> and the API said 'canPickFields' has been set false can solve this 
> problem,but where the canPickFields ? 
>
> Thank you 
>
> Best Regards 
> Daniel

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to mark a field as completely hidden for smartgwt ListGrid?

[Gustavo Matias]

 

setCanHide(flase) didn't work for me... I had to set the height of the 
field as 0. field.setWidth(0);

On Wednesday, January 4, 2012 5:04:23 AM UTC-5, Daniel wrote:
>
> Hi guys, 
>
> How to mark a field as completely hidden for smartgwt ListGrid? 
> I do listGridFields[i].setHidden(true) according to API,But it still 
> could be able to show the field via a context menu. 
> and the API said 'canPickFields' has been set false can solve this 
> problem,but where the canPickFields ? 
>
> Thank you 
>
> Best Regards 
> Daniel

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

[Jens]

>
> Do you have a specific example?  I'm curious.
>

Existing widgets should also work great on mobile devices, its not just 
about writing new widgets. 

Its also not just about widgets in general. For example there is currently 
an issue in GWT-RPC where only IE9 has a memory leak because GWT-RPC uses 
eval() to parse the server response and IE9 keeps everything eval'd in 
memory. Slightly changing the server code and switching to JSON.parse() on 
the client would solve the problem, but IE6/7 do not support JSON.parse(). 
So to fix this issue for IE9 the server serialization needs to figure out 
which IE version is talking to the server and then generate different 
responses (either JS or JSON). Targeting different browsers on client side 
is easy (deferred binding) but this time the server must target different 
browser versions as well. So its more complicated than it could be.

https://code.google.com/p/google-web-toolkit/issues/detail?id=5736
https://gwt-review.googlesource.com/#/c/2900/

I think thats a good example where IE6/7 support costs more development 
resources although you know that IE6/7 doesn't really play a big role 
anymore. Microsoft recommends to not use them anymore and 2014 they will 
stop supporting IE6-8 as Windows XP extended support ends in April 2014.

So would you invest a lot of work today in supporting browsers whose 
support officially ends in less than a year? Probably not. Its a good time 
now to slowly phasing out IE6/7 and later IE 8 support.

-- J.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Google Apps Dev With GWT

[Charles Odili]

Hello guys. I know there is Google App Script, but it runs online and it is 
JavaScript sort of. Is it possible to develop GWT apps that can integrate 
with Google Apps (Gmail, Spreadsheets e.t.c).

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Spring Security and Google App Engine

[Joey Wilkinson]

I'm having the same issue with my GWT web application.  issue still happens 
with the default GWT GAE sample project and basic spring security setup.





Has anyone else experienced this kind of issue? or has found a work around?


On Wednesday, November 28, 2012 4:09:14 PM UTC-6, Ronnie Schaniel wrote:
>
> I'm working on Spring Security implementation for a few days now. The 
> login form is displayed if I integrate spring security in a sample project. 
> When I enable the Google App Engine in the eclipse project settings the 
> redirect to the login form is not working anymore, so I can not secure the 
> EntryPoint. If I have a single service on a specific URL which is not using 
> RPC calls the spring security works well.
> On the part of the application that uses RPC the login form is not 
> rendered correctly and an exception is thrown. So most likely the rpc 
> service is the source of the problem. 
>
> In addition my Spring Security configuration:
> 
>
> http://www.springframework.org/schema/security";
> xmlns:beans="http://www.springframework.org/schema/beans"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.springframework.org/schema/beans 
> http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
> http://www.springframework.org/schema/security 
> http://www.springframework.org/schema/security/spring-security-3.0.xsd";>
>  
> 
>  access="IS_AUTHENTICATED_ANONYMOUSLY" />
>  access="IS_AUTHENTICATED_ANONYMOUSLY" />
> 
> 
> 
> 
>  />
> 
>
> 
>  class="com.nfl.economapp.security.CustomAuthenticationProvider" />
>  
> 
> 
> 
>
> 
>
> Does anyone have an idea how to solve this? Or should I try Apache Shiro 
> as an alternative?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

[Alex Epshteyn]

Fair enough, but I'm curious to know why leaving the code that supports
legacy browsers would interfere with implementing new features.  For
example, if you want to implement a new widget called XPanel, it think it's
perfectly fine to say that this widget doesn't support IE6/7/8, and leave
it up to userland to chose whether to use the new widget and how to work
around it for new browsers.

Do you have a specific example?  I'm curious.


On Thu, May 23, 2013 at 5:54 PM, Jens  wrote:

> To simplify the code base and moving on (HTML 5) I would say.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

[Jens]

> I'd like to ask, however, the reasons for planning to remove support for 
> IE6/7/8?  Why would we do that?  
>

To simplify the code base and moving on (HTML 5) I would say. 

JQuery for example already did that transition. JQuery 2.0 does not support 
IE6-8 anymore but they still maintain JQuery 1.9.x for people that still 
need IE6-8 browser support. In terms of GWT you can still use the last 
version that supports IE6-8 and then decide yourself when its time to move 
to a newer GWT version for your site.

-- J.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

[Juan Pablo Gardella]

I agree on do not remove IE7 and IE8. A lot of user still using them.


2013/5/23 Alex Epshteyn 

> Hi Thomas,
>
> Thanks for chiming in and providing the extra info.  Good to know.
>
> I'd like to ask, however, the reasons for planning to remove support for
> IE6/7/8?  Why would we do that?  It's already there and doesn't require too
> much maintenance.
>
> As of today, nearly 8% of my site's visitors are on IE8 and close to 1%
> are still on IE7.  These are pretty big numbers for a high traffic website,
> and would translate into lost revenue if the browsers weren't supported.  I
> can't imagine Google pulling support for a browser with that kind of usage
> for one of its products. .  Here's the full data:
> https://docs.google.com/spreadsheet/ccc?key=0AvMlWdpkpAA6dGdpa3lsZTVQWl9qcFJrWmZCZ0ZZb0E#gid=0
>
> Also, as you guys can see from the data, stack emulation is still required
> for 54% of my site's traffic.
>
> While I'd like to see users upgrading to the latest browsers as much as
> any developer, let's be realistic: WinXP is not going away any time soon
> (Microsoft dropping support for it isn't going to make people like my dad
> go out and buy a new computer).  Google Analytics is shows that 80% of my
> users are on Windows and 21% of those are still on Windows XP: that is a
> very big number!
>
>
>
> On Thu, May 23, 2013 at 5:13 AM, Thomas Broyer  wrote:
>
>>
>>
>> On Wednesday, May 22, 2013 11:53:47 PM UTC+2, Alex Epshteyn wrote:
>>>
>>> Thanks for your comment.  Let me respond to your points:
>>>
>>> 1) I've seen this point discussed before, and the standard
>>> counter-argument is that the spirit of OSS is free as in "freedom," not
>>> "beer."  Lots of developers get paid to work on OSS projects.
>>>
>>> 2) This is actually one of the reasons I'm thinking about raising funds.
>>>  I am already on the verge of using my patch inside my own GWT-based app,
>>> but if I get some funding I'd be able to justify taking the extra time to
>>> make sure the patch will pass the review process.
>>>
>>
>> +1 to those 2 points.
>>
>>
>>>  3) I must point out that your third argument is not in the spirit of
>>> GWT, which aims to support as many browsers as possible.
>>>
>>
>> That's not entirely true. GWT only ever supported the 4 major browser
>> engines: Trident (IE), WebKit (SquirrelFish / V8; aka Safari / Chromium),
>> Gecko (Firefox) and Presto (Opera).
>>
>> Jens is right: we'll soon remove support for IE6 and 7, and then for IE8
>> (not long after MS drops support for WinXP).
>> GWT never really "supported" Opera, and the level of support was only
>> against the latest version. Now that Opera is moving from Presto to
>> Chromium, that means one less platform to support in the very near future
>> (by the next GWT release, but we'll probably keep the "opera" permutation
>> along for one more release).
>>
>> As of today, you will not get good stack traces with GWT on any modern
>>> browser, including WebKit.  By "relevant information", I assume you mean
>>> sourcemaps support.  Well, Chrome is the only browser that currently
>>> supports sourcemaps but GWT's existing support for generating stack traces
>>> with that information is very buggy, and this is one of the things I'm
>>> working on improving.  I'm also not optimistic that sourcemaps will achieve
>>> universal support any time soon, if ever.
>>>
>>
>> Chromium has it for a while (hence Chrome –all platforms–, Opera for
>> Android –though what matters is the remote debugger, not the browser– and
>> Opera.next), and Firefox is starting to roll it out [1,2] in 23 (currently
>> Aurora channel) and I'm told the next Safari should have it too [3].
>> Will IE ever have it? I believe so, particularly now that MS is pushing
>> languages that compile to JS (TypeScript, which can generate sourcemaps).
>> Obviously that would only be available in IE11 (or later), but it seems
>> like it would be possible to have support in your IDE with the help of an
>> IE plugin [4] for IE8/9/10 (would it work in Windows 8 though?)
>>
>> That said, source maps support in the browser is related to, but
>> different from stack trace resymbolization.
>>
>> [1]
>> https://hacks.mozilla.org/2013/05/firefox-developer-tool-features-for-firefox-23/
>> [2]
>> https://hacks.mozilla.org/2013/05/compiling-to-javascript-and-debugging-with-source-maps/
>> [3]
>> http://stackoverflow.com/questions/16446114/is-it-possible-to-enable-javascript-source-maps-in-safari-6
>> [4] http://wiki.eclipse.org/JSDT/Debug/IE
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Google Web Toolkit" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/google-web-toolkit/hP8cQ7AdDUc/unsubscribe?hl=en
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> Visit this group at
>> ht

Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

[Alex Epshteyn]

Hi Thomas,

Thanks for chiming in and providing the extra info.  Good to know.

I'd like to ask, however, the reasons for planning to remove support for
IE6/7/8?  Why would we do that?  It's already there and doesn't require too
much maintenance.

As of today, nearly 8% of my site's visitors are on IE8 and close to 1% are
still on IE7.  These are pretty big numbers for a high traffic website, and
would translate into lost revenue if the browsers weren't supported.  I
can't imagine Google pulling support for a browser with that kind of usage
for one of its products. .  Here's the full data:
https://docs.google.com/spreadsheet/ccc?key=0AvMlWdpkpAA6dGdpa3lsZTVQWl9qcFJrWmZCZ0ZZb0E#gid=0

Also, as you guys can see from the data, stack emulation is still required
for 54% of my site's traffic.

While I'd like to see users upgrading to the latest browsers as much as any
developer, let's be realistic: WinXP is not going away any time soon
(Microsoft dropping support for it isn't going to make people like my dad
go out and buy a new computer).  Google Analytics is shows that 80% of my
users are on Windows and 21% of those are still on Windows XP: that is a
very big number!



On Thu, May 23, 2013 at 5:13 AM, Thomas Broyer  wrote:

>
>
> On Wednesday, May 22, 2013 11:53:47 PM UTC+2, Alex Epshteyn wrote:
>>
>> Thanks for your comment.  Let me respond to your points:
>>
>> 1) I've seen this point discussed before, and the standard
>> counter-argument is that the spirit of OSS is free as in "freedom," not
>> "beer."  Lots of developers get paid to work on OSS projects.
>>
>> 2) This is actually one of the reasons I'm thinking about raising funds.
>>  I am already on the verge of using my patch inside my own GWT-based app,
>> but if I get some funding I'd be able to justify taking the extra time to
>> make sure the patch will pass the review process.
>>
>
> +1 to those 2 points.
>
>
>>  3) I must point out that your third argument is not in the spirit of
>> GWT, which aims to support as many browsers as possible.
>>
>
> That's not entirely true. GWT only ever supported the 4 major browser
> engines: Trident (IE), WebKit (SquirrelFish / V8; aka Safari / Chromium),
> Gecko (Firefox) and Presto (Opera).
>
> Jens is right: we'll soon remove support for IE6 and 7, and then for IE8
> (not long after MS drops support for WinXP).
> GWT never really "supported" Opera, and the level of support was only
> against the latest version. Now that Opera is moving from Presto to
> Chromium, that means one less platform to support in the very near future
> (by the next GWT release, but we'll probably keep the "opera" permutation
> along for one more release).
>
> As of today, you will not get good stack traces with GWT on any modern
>> browser, including WebKit.  By "relevant information", I assume you mean
>> sourcemaps support.  Well, Chrome is the only browser that currently
>> supports sourcemaps but GWT's existing support for generating stack traces
>> with that information is very buggy, and this is one of the things I'm
>> working on improving.  I'm also not optimistic that sourcemaps will achieve
>> universal support any time soon, if ever.
>>
>
> Chromium has it for a while (hence Chrome –all platforms–, Opera for
> Android –though what matters is the remote debugger, not the browser– and
> Opera.next), and Firefox is starting to roll it out [1,2] in 23 (currently
> Aurora channel) and I'm told the next Safari should have it too [3].
> Will IE ever have it? I believe so, particularly now that MS is pushing
> languages that compile to JS (TypeScript, which can generate sourcemaps).
> Obviously that would only be available in IE11 (or later), but it seems
> like it would be possible to have support in your IDE with the help of an
> IE plugin [4] for IE8/9/10 (would it work in Windows 8 though?)
>
> That said, source maps support in the browser is related to, but different
> from stack trace resymbolization.
>
> [1]
> https://hacks.mozilla.org/2013/05/firefox-developer-tool-features-for-firefox-23/
> [2]
> https://hacks.mozilla.org/2013/05/compiling-to-javascript-and-debugging-with-source-maps/
> [3]
> http://stackoverflow.com/questions/16446114/is-it-possible-to-enable-javascript-source-maps-in-safari-6
> [4] http://wiki.eclipse.org/JSDT/Debug/IE
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google Web Toolkit" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/hP8cQ7AdDUc/unsubscribe?hl=en
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web To

Does GWT will work on mobile for drag and drop

[Rahul Gurjar]

Currently i am working on a project in which i have to make UI with drag 
and drop feature, but problem is i would like work it on android mobile.
Please suggest some resource and idea.
Here is screen shot of intented UI.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Offline debugging my gwt app

[emurmur]

Yves, I would try SuperDev mode and debug using Chrome Dev Tools and the 
source maps produced by the super dev mode code server.  You don't need any 
special changes to your project, you just need to create a way to launch 
the super dev mode code server.  This is documented at 
gwtproject.org.here. 
 Here 
is
 
a blog post I wrote with detailed instructions.

Ed


On Monday, May 20, 2013 11:46:08 AM UTC-7, yves wrote:
>
> Hello All,
>
> I need to debug my gwt app. The problem is that I need to debug it OFFLINE.
> After a tour on the net, I didn't found an answer.
>
> Thus here is the scenario.
>
> My GWT version is 2.4.0
>
> Debugging the code is ok.
> Running in production offline is ok, using a cache manifest.
>
> But I can't do both : debugging offline.
>
> To avoid any config difference, I use exactly the same tomcat server 
> deployment to run in production or in debug mode (thus with the debug 
> option -noserver).
> The cache manifest is built in runtime by a dedicated service whose 
> response depends on the current permutation.
>
> When online, the manifest is always requested in debug and in production 
> mode (confirmed by tracing). (a subsidiary question is : why in production 
> the manifest is called twice and in debug it is called once ?).
>
> Then I stopped tomcat.
> => In production offline the gwt app is running correctly.
> => In debug offline, nothing is displayed : the browser has loaded the app 
> html file from its cache (confirmed by displaying the page source code), 
> but the browser remains empty, the gwt app is not running.
>
> It seems that when offline, the google dev plugin doesn't communicate 
> correctly with the IDE as it even doesn't realize when the development mode 
> is stopped in the IDE (the black overlay with the message "Plugin failed to 
> connect to Development Mode server at localhost:9997" is no displayed). May 
> be the plugin is not started when offline ?
>
> In order to help me test my app when offline, does anybody knows why the 
> app is not running in debug offline mode and how to make it run ?
>
> Thanks a lot !
> Yves
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: asm.js

[emurmur]

My understanding is that asm.js is all or nothing.  It is designed as a 
target for languages that manage their own memory (that is generally not 
garbage collected, but you could implement garbage collection in such a 
system).  Firefox looks at the JavaScript and decides if it is asm.js, then 
switches to another JavaScript interpreter that is optimized for asm.js. 
 If this interpreter detects anything outside of the asm.js subset, it 
kicks all execution back to the standard interpreter.  This means you can't 
pick part of a gwt compile to target asm.js; it would be all on none.

Ed


On Thursday, May 23, 2013 12:52:00 AM UTC-7, RyanZA wrote:
>
> Have a quick read through this article if you don't know what asm.js is:
>
> http://arstechnica.com/information-technology/2013/05/native-level-performance-on-the-web-a-brief-examination-of-asm-js/
>
> With firefox already supporting it, GWT should have the firefox compile 
> target target asm.js for, at least, things like ArrayList.
> I didn't see anything about it in the recent I/O talk - has anybody looked 
> at how difficult it would be to support in the GWT compiler ?
>
> Ryan
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: asm.js

[Thomas Broyer]

On Thursday, May 23, 2013 9:52:00 AM UTC+2, RyanZA wrote:
>
> Have a quick read through this article if you don't know what asm.js is:
>
> http://arstechnica.com/information-technology/2013/05/native-level-performance-on-the-web-a-brief-examination-of-asm-js/
>
> With firefox already supporting it, GWT should have the firefox compile 
> target target asm.js for, at least, things like ArrayList.
> I didn't see anything about it in the recent I/O talk - has anybody looked 
> at how difficult it would be to support in the GWT compiler ?
>
>
Copied from Ray Cromwell's comment on 
https://plus.google.com/107037260910017774154/posts/179TxALiF5v:

> Well, GWT assumes garbage collection semantics, and ASM.JS assumes typed 
> arrays for everything and malloc/free semantics. So it wouldn't hard to 
> support asm.js, but we'd end up memory leaking like crazy unless we 
> implemented a mark/sweep collector in JS :) 

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: primer for mobile development

[Ashton Thomas]

Here is a playlist of mobile web videos form Google IO 2013:

http://www.youtube.com/watch?v=EPYnGFEcis4&list=PLAbrfaVBC6kWiNBI1wPYhXtTke64QkLqC



-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: JPA issue: A parent cannot be established or changed once an object has been persisted.

[Nermin]

When I try to do that, I get a following error:

java.lang.NullPointerException
at 
com.google.appengine.datanucleus.StoreFieldManager.storeRelations(StoreFieldManager.java:848)
at 
com.google.appengine.datanucleus.DatastorePersistenceHandler.insertObjectsInternal(DatastorePersistenceHandler.java:367)
at 
com.google.appengine.datanucleus.DatastorePersistenceHandler.insertObject(DatastorePersistenceHandler.java:218)
at 
org.datanucleus.state.JDOStateManager.internalMakePersistent(JDOStateManager.java:2377)
at 
org.datanucleus.state.JDOStateManager.flush(JDOStateManager.java:3769)
at 
org.datanucleus.state.JDOStateManager.getExternalObjectId(JDOStateManager.java:1088)
at 
org.datanucleus.state.JDOStateManager.getObjectId(JDOStateManager.java:958)
at com.emajstor.server.persistence.Company.jdoGetObjectId(Company.java)
at 
org.datanucleus.api.jpa.JPAAdapter.getIdForObject(JPAAdapter.java:272)
at 
com.google.appengine.datanucleus.EntityUtils.getKeyForObject(EntityUtils.java:245)
at 
com.google.appengine.datanucleus.EntityUtils.getParentKey(EntityUtils.java:853)
at 
com.google.appengine.datanucleus.StoreFieldManager.establishEntityGroup(StoreFieldManager.java:939)
at 
com.google.appengine.datanucleus.DatastorePersistenceHandler.insertObjectsInternal(DatastorePersistenceHandler.java:244)
at 
com.google.appengine.datanucleus.DatastorePersistenceHandler.insertObject(DatastorePersistenceHandler.java:218)
at 
org.datanucleus.state.JDOStateManager.internalMakePersistent(JDOStateManager.java:2377)
at 
org.datanucleus.state.JDOStateManager.flush(JDOStateManager.java:3769)
at 
org.datanucleus.ObjectManagerImpl.flushInternalWithOrdering(ObjectManagerImpl.java:3884)
at 
org.datanucleus.ObjectManagerImpl.flushInternal(ObjectManagerImpl.java:3807)
at org.datanucleus.ObjectManagerImpl.flush(ObjectManagerImpl.java:3747)
at 
org.datanucleus.ObjectManagerImpl.preCommit(ObjectManagerImpl.java:4137)
at 
org.datanucleus.ObjectManagerImpl.transactionPreCommit(ObjectManagerImpl.java:428)
at 
org.datanucleus.TransactionImpl.internalPreCommit(TransactionImpl.java:400)
at org.datanucleus.TransactionImpl.commit(TransactionImpl.java:288)
at org.datanucleus.ObjectManagerImpl.close(ObjectManagerImpl.java:1090)
at 
org.datanucleus.api.jpa.JPAEntityManager.close(JPAEntityManager.java:193)
at com.emajstor.server.persistence.Company.persist(Company.java:110)
at 
com.emajstor.server.test.MyTestServlet.testPersistenceOne(MyTestServlet.java:74)
at com.emajstor.server.test.MyTestServlet.doGet(MyTestServlet.java:39)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at 
com.google.appengine.api.socket.dev.DevSocketFilter.doFilter(DevSocketFilter.java:74)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.appengine.tools.development.ResponseRewriterFilter.doFilter(ResponseRewriterFilter.java:123)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.appengine.tools.development.HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:34)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:61)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:125)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.appengine.tools.development.BackendServersFilter.doFilter(BackendServersFilter.java:97)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at 
com.google.appengine.tools.de

Re: primer for mobile development

[Ed]

Of course you can use ADT and spin up the environment, I use
ANDROVM
because it loads a whole lot faster than ADT.



On Wed, May 22, 2013 at 11:33 PM, mike b  wrote:

> Nino , thx for the links. I will look into those.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Retrieving and manupulating search result from gwtsearch

[Condeas]

Please, is there anyway to manipulate the search result from the gwtsearch 
option.

It returns a list. How can i retrieve this list and make my manipulations 
on the list; maybe change the order the contents appear, e.t.c.
The SearchContolOptions class does not have any method like 
getSearchList(). As a matter of fact, the results are contained in a final 
List variable.

Thank you.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: gwt-maven-archetypes with multiple client modules

[Thomas Käfer]

Am Donnerstag, 23. Mai 2013 13:18:47 UTC+2 schrieb Thomas Broyer:

>
> If you use  then the gwt.xml has to be in group.id, 
> otherwise only group.id.client.client.* classes are in the source path. 
> group.id.client.App is not an thus cannot be found.
>
>
Oh my god, I'm so stupid.. Thanks so much! I'm really not worth the money 
they pay me ;)
 

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: gwt-maven-archetypes with multiple client modules

[Thomas Broyer]

On Thursday, May 23, 2013 12:48:50 PM UTC+2, Thomas Käfer wrote:
>
> Okey! So you've helped me make a huge step forward yesterday, thanks for 
> that Thomas!
>
> Now I've got a new problem I can't find my way around: I've tried to move 
> the App.java & App*.gwt.xml into from the package "group.id" into the 
> package "group.id.client" package, and adapted the references within the 
> pom.xml and gwt.xml files (and also in gwt.xml change  to 
>  ), but when I try to do a maven build it always 
> fails:
>
> [INFO] Compiling module group.id.client.App
>> [INFO]Finding entry point classes
>> [INFO]   [ERROR] Unable to find type 'group.id.client.App'
>> [INFO]  [ERROR] Hint: Previous compiler errors may have made this 
>> type unavailable
>> [INFO]  [ERROR] Hint: Check the inheritance chain from your 
>> module; it may not be inheriting a required module or a module may not be 
>> adding its source path entries properly
>
>
> The step "Finding entry point classes" takes quite long, around 5 seconds 
> before the failure shows..
> When I undo the move and restore the references to group.id.App it works 
> again as expected.
>
> Do you have an idea, what could cause that? Have I missed something that 
> needs adapting when moving the module & entrypoint?
>

If you use  then the gwt.xml has to be in group.id, 
otherwise only group.id.client.client.* classes are in the source path. 
group.id.client.App is not an thus cannot be found.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: gwt-maven-archetypes with multiple client modules

[Thomas Käfer]

Okey! So you've helped me make a huge step forward yesterday, thanks for 
that Thomas!

Now I've got a new problem I can't find my way around: I've tried to move 
the App.java & App*.gwt.xml into from the package "group.id" into the 
package "group.id.client" package, and adapted the references within the 
pom.xml and gwt.xml files (and also in gwt.xml change  to 
 ), but when I try to do a maven build it always 
fails:

[INFO] Compiling module group.id.client.App
> [INFO]Finding entry point classes
> [INFO]   [ERROR] Unable to find type 'group.id.client.App'
> [INFO]  [ERROR] Hint: Previous compiler errors may have made this 
> type unavailable
> [INFO]  [ERROR] Hint: Check the inheritance chain from your 
> module; it may not be inheriting a required module or a module may not be 
> adding its source path entries properly


The step "Finding entry point classes" takes quite long, around 5 seconds 
before the failure shows..
When I undo the move and restore the references to group.id.App it works 
again as expected.

Do you have an idea, what could cause that? Have I missed something that 
needs adapting when moving the module & entrypoint?

Am Mittwoch, 22. Mai 2013 14:46:53 UTC+2 schrieb Thomas Broyer:
>
>
>
> On Wednesday, May 22, 2013 1:08:38 PM UTC+2, Thomas Käfer wrote:
>>
>> Thanks for your reply, and thanks for the info! Have a working debug-able 
>> environment now!
>>
>> With this "Debug As… → Web Application (running on an external server)" 
>> on the client project, I get the error "Could not find any host-pages in 
>> project -client" 
>>
> My setup is generated by your maven archetype "modular-webapp" and nearly 
>> no changes, only played around with debug configurations and maven a little 
>> bit.
>>
>
> This is strange 'cause I tested it as I was replying, with a freshly 
> created "modular-webapp" project. I had an error about 
> test-client/target/test-client-1.0.0-SNAPSHOT not existing, but that was 
> because I hadn't previously "mvn package" (or even run "mvn tomcat7:run"). 
> I deleted the launch config and started again (Debug As…) and it just 
> worked.
>
> But based on your other info I've managed to create a "Web Application" 
>> debug configuration manually, and it works!
>>
>
> That's generally what I do, as I like to have control. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GWT RPC Serialization on web and app server

[Entlog]

Awesome!! Thanks. I was having problems with a jmeter test and I saw your 
solution...it's really that! The jmeter captured request had the reference 
to the hash for another deployed environment and when trying to test 
against another deployed war it was throwing the serializable error. Now I 
know how to fix it :)...

El jueves, 1 de noviembre de 2012 10:27:54 UTC+1, Jens escribió:
>
> Make sure that your app server can still find the .rpc file. Thats 
> your GWT-RPC serialization policy file that the server must know in order 
> to serialize anything that implements Serializable. If it does not find 
> this file it falls back to the old IsSerializable mechanism and if you do 
> not have implemented that interface serialization will fail. 
>
> Normally you should see a warning in the app server log on the first RPC 
> request when GWT's RemoteServiceServlet tries to load the serialization 
> policy file but can not find it.
>
> For example I often have to change the lookup of that file because my 
> deployment does not conform to GWT's standard assumptions.
>
> -- J.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: JPA issue: A parent cannot be established or changed once an object has been persisted.

[Juan Pablo Gardella]

In the loop, do user.setCompany(company). You need a transaction. Create it
and do the commit.


2013/5/23 Nermin 

> Dear Juan,
>
> For this purpose I use the GWT-s Request Factory.
> However, in order to simplify the problem, I have created a server side
> persistence example using a simple servlet where one company and two users
> are created. Please have a look at the MyTestServlet.java within the Zip
> File.
>
> https://dl.dropboxusercontent.**com/u/2983671/JPA_Problem/JPA_**
> Problem.zip
>
> The funny thing is, I get now a different Eror:
>
> javax.persistence.PersistenceException: Illegal argument
> 
> Caused by: java.lang.IllegalArgumentException: cross-group transaction
> need to be explicitly specified, see TransactionOptions.Builder.withXGfound
> both Element {
>   type: "Tradesman"
>   id: 361
> }
>  and Element {
>   type: "Tradesman"
>   id: 362
> }
>
> When I remove the @PrePersit from "User class" it works just fine!
> The Error pops up as soon as i modify a parameter on "Tradesman" entity
> (more exactly on its parent class "User").
>
> I really do not understand this behavior. ... I also must admit that I am
> not very advanced in JPA.
>
> Thank you for very much for your help.
>
> Best regards:
>
> Nermin
>
>
> Am Mittwoch, 22. Mai 2013 15:28:50 UTC+2 schrieb Juan Pablo Gardella:
>>
>> Show how you are persisting the entities.
>>
>>
>> 2013/5/22 Nermin 
>>
>>> Dear Alfredo and Juan,
>>>
>>> obviously there is an hidden problem with my code i simply do not see.
>>> Could you please have a short look at these 3 classes (full code) and
>>> tell me what am I doing wrong here:
>>>
>>> https://dl.dropboxusercontent.**com/u/2983671/JPA_Problem/JPA_**
>>> Problem.zip
>>>
>>> Please note: Everything works fine as log as I do not try to make any
>>> changes to the Tradesman entity (its parameters).
>>> When is set new password or any other parameter, i get an error message
>>> of type:
>>>
>>> Detected attempt to establish Company(no-id-yet) as the parent of
>>> Tradesman(358) but the entity identified by Tradesman(358) has already been
>>> persisted without a parent.  A parent cannot be established or changed once
>>> an object has been persisted.
>>>
>>> I am using: JPA with DataNucleus on Google Datastore. (Standard setting
>>> that come with GWT 2.5)
>>>
>>> Thank you in advance for your help!!
>>>
>>> Best regards:
>>>
>>> Nermin
>>>
>>>
>>> Am Dienstag, 21. Mai 2013 18:29:54 UTC+2 schrieb Alfredo
>>> Quiroga-Villamil:

 Or use a cascade persist, merge to force creation or merge respectively

 Sent from my iPhone

 On May 21, 2013, at 7:02 AM, Juan Pablo Gardella 
 wrote:

 You should persist company before persist Tradesman or attach to an
 existent company. This relation should be explicit. Create
 company.addTrademan(Trademan t) method:

 company.addTrademan(Trademan t){
 users.add(t);
 t.setCompany(this);
 }

 Call this in a transactional method.

 Juan






 2013/5/21 Nermin 

> Dear Juan,
>
> I tried *@ManyToOne(optional=false)*, unfortunately no changes.
> In my current setting, the @PrePersist is called only once. (I see it
> on system out) That means: no multiple attempts to persist Tradesman 
> entity.
>
> However, it looks to me that whenever I change parameters on the
> Tradesman entity JPA creates/persists for some reason the Tradesman in the
> DB, independently from the Company entity.
> I use Standard GWT settings: GWT 2.5, DataNucleus on Appengine
> Datastore.
>
> The scenario I am describing here is a standard scenario you will face
> when using GWT with JPA. I am surprised that my code is not working.
> @PrePersist works fine as long as the Entity is not in a owned
> relation with other entities.
>
> Does anyone has an idea what could be wrong here?
>
> Thank you!!
>
> Nermin
>
> @Thomas: Thank you for the advise. I will
>
> Am Dienstag, 21. Mai 2013 12:01:43 UTC+2 schrieb Juan Pablo Gardella:
>>
>> Update your entity as:
>>
>> @Entity
>> public class Tradesman extends User{
>> @ManyToOne(optional=false)
>> private Company company;
>>
>> *@PrePersist*
>> public void hashPassword(){
>> setPassword(BCrypt.hashpw(**enti**ty.getPassword(),
>> BCrypt.gensalt());
>> }
>>
>> And then check where are you persisting Tradesman without company.
>>
>>
>>
>> 2013/5/21 Thomas Broyer 
>>
>>>
>>>
>>> On Tuesday, May 21, 2013 11:18:42 AM UTC+2, Nermin wrote:

 Dear GWT developers,

 I have a "probably simple" problem with my application which I am
 obviously not abl

Re: JPA issue: A parent cannot be established or changed once an object has been persisted.

[Nermin]

Dear Juan,

For this purpose I use the GWT-s Request Factory.
However, in order to simplify the problem, I have created a server side 
persistence example using a simple servlet where one company and two users 
are created. Please have a look at the MyTestServlet.java within the Zip 
File.

https://dl.dropboxusercontent.com/u/2983671/JPA_Problem/JPA_Problem.zip

The funny thing is, I get now a different Eror:

javax.persistence.PersistenceException: Illegal argument

Caused by: java.lang.IllegalArgumentException: cross-group transaction need 
to be explicitly specified, see TransactionOptions.Builder.withXGfound both 
Element {
  type: "Tradesman"
  id: 361
}
 and Element {
  type: "Tradesman"
  id: 362
}

When I remove the @PrePersit from "User class" it works just fine!
The Error pops up as soon as i modify a parameter on "Tradesman" entity 
(more exactly on its parent class "User").

I really do not understand this behavior. ... I also must admit that I am 
not very advanced in JPA. 

Thank you for very much for your help.

Best regards:

Nermin


Am Mittwoch, 22. Mai 2013 15:28:50 UTC+2 schrieb Juan Pablo Gardella:
>
> Show how you are persisting the entities.
>
>
> 2013/5/22 Nermin >
>
>> Dear Alfredo and Juan,
>>
>> obviously there is an hidden problem with my code i simply do not see.
>> Could you please have a short look at these 3 classes (full code) and 
>> tell me what am I doing wrong here:
>>
>> https://dl.dropboxusercontent.com/u/2983671/JPA_Problem/JPA_Problem.zip
>>
>> Please note: Everything works fine as log as I do not try to make any 
>> changes to the Tradesman entity (its parameters).
>> When is set new password or any other parameter, i get an error message 
>> of type:
>>
>> Detected attempt to establish Company(no-id-yet) as the parent of 
>> Tradesman(358) but the entity identified by Tradesman(358) has already been 
>> persisted without a parent.  A parent cannot be established or changed once 
>> an object has been persisted.
>>
>> I am using: JPA with DataNucleus on Google Datastore. (Standard setting 
>> that come with GWT 2.5)
>>
>> Thank you in advance for your help!!
>>
>> Best regards:
>>
>> Nermin
>>
>>
>> Am Dienstag, 21. Mai 2013 18:29:54 UTC+2 schrieb Alfredo Quiroga-Villamil:
>>>
>>> Or use a cascade persist, merge to force creation or merge respectively
>>>
>>> Sent from my iPhone
>>>
>>> On May 21, 2013, at 7:02 AM, Juan Pablo Gardella  
>>> wrote:
>>>
>>> You should persist company before persist Tradesman or attach to an 
>>> existent company. This relation should be explicit. Create 
>>> company.addTrademan(Trademan t) method:
>>>
>>> company.addTrademan(Trademan t){
>>> users.add(t);
>>> t.setCompany(this);
>>> }
>>>
>>> Call this in a transactional method.
>>>
>>> Juan
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2013/5/21 Nermin 
>>>
 Dear Juan,

 I tried *@ManyToOne(optional=false)*, unfortunately no changes.
 In my current setting, the @PrePersist is called only once. (I see it 
 on system out) That means: no multiple attempts to persist Tradesman 
 entity.

 However, it looks to me that whenever I change parameters on the 
 Tradesman entity JPA creates/persists for some reason the Tradesman in the 
 DB, independently from the Company entity.
 I use Standard GWT settings: GWT 2.5, DataNucleus on Appengine 
 Datastore.

 The scenario I am describing here is a standard scenario you will face 
 when using GWT with JPA. I am surprised that my code is not working.
 @PrePersist works fine as long as the Entity is not in a owned relation 
 with other entities.

 Does anyone has an idea what could be wrong here?

 Thank you!!

 Nermin

 @Thomas: Thank you for the advise. I will 

 Am Dienstag, 21. Mai 2013 12:01:43 UTC+2 schrieb Juan Pablo Gardella:
>
> Update your entity as: 
>
> @Entity
> public class Tradesman extends User{
> @ManyToOne(optional=false)
> private Company company;
>
> *@PrePersist*
> public void hashPassword(){
> setPassword(BCrypt.hashpw(**entity.getPassword(), 
> BCrypt.gensalt());
> }
>
> And then check where are you persisting Tradesman without company. 
>
>
>
> 2013/5/21 Thomas Broyer 
>
>>
>>
>> On Tuesday, May 21, 2013 11:18:42 AM UTC+2, Nermin wrote:
>>>
>>> Dear GWT developers,
>>>
>>> I have a "probably simple" problem with my application which I am 
>>> obviously not able to solve.
>>>
>>> Two Classes: Company, Tradesman
>>>
>>> @Entity
>>> public class Company {
>>> @OneToMany(cascade = CascadeType.ALL, mappedBy = "company")
>>> private List users = new ArrayList();
>>>
>>> 
>>> }
>>>
>>>
>>> @Entity
>>> public class Tradesman extends User{
>>> @ManyToOne
>>> private Company company;
>>>
>>> *@PrePersist*
>>

Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?

[Thomas Broyer]

On Wednesday, May 22, 2013 11:53:47 PM UTC+2, Alex Epshteyn wrote:
>
> Thanks for your comment.  Let me respond to your points:
>
> 1) I've seen this point discussed before, and the standard 
> counter-argument is that the spirit of OSS is free as in "freedom," not 
> "beer."  Lots of developers get paid to work on OSS projects.
>
> 2) This is actually one of the reasons I'm thinking about raising funds. 
>  I am already on the verge of using my patch inside my own GWT-based app, 
> but if I get some funding I'd be able to justify taking the extra time to 
> make sure the patch will pass the review process.
>

+1 to those 2 points.
 

> 3) I must point out that your third argument is not in the spirit of GWT, 
> which aims to support as many browsers as possible.
>

That's not entirely true. GWT only ever supported the 4 major browser 
engines: Trident (IE), WebKit (SquirrelFish / V8; aka Safari / Chromium), 
Gecko (Firefox) and Presto (Opera).

Jens is right: we'll soon remove support for IE6 and 7, and then for IE8 
(not long after MS drops support for WinXP).
GWT never really "supported" Opera, and the level of support was only 
against the latest version. Now that Opera is moving from Presto to 
Chromium, that means one less platform to support in the very near future 
(by the next GWT release, but we'll probably keep the "opera" permutation 
along for one more release).

As of today, you will not get good stack traces with GWT on any modern 
> browser, including WebKit.  By "relevant information", I assume you mean 
> sourcemaps support.  Well, Chrome is the only browser that currently 
> supports sourcemaps but GWT's existing support for generating stack traces 
> with that information is very buggy, and this is one of the things I'm 
> working on improving.  I'm also not optimistic that sourcemaps will achieve 
> universal support any time soon, if ever.
>

Chromium has it for a while (hence Chrome –all platforms–, Opera for 
Android –though what matters is the remote debugger, not the browser– and 
Opera.next), and Firefox is starting to roll it out [1,2] in 23 (currently 
Aurora channel) and I'm told the next Safari should have it too [3].
Will IE ever have it? I believe so, particularly now that MS is pushing 
languages that compile to JS (TypeScript, which can generate sourcemaps). 
Obviously that would only be available in IE11 (or later), but it seems 
like it would be possible to have support in your IDE with the help of an 
IE plugin [4] for IE8/9/10 (would it work in Windows 8 though?)

That said, source maps support in the browser is related to, but different 
from stack trace resymbolization.

[1] 
https://hacks.mozilla.org/2013/05/firefox-developer-tool-features-for-firefox-23/
[2] 
https://hacks.mozilla.org/2013/05/compiling-to-javascript-and-debugging-with-source-maps/
[3] 
http://stackoverflow.com/questions/16446114/is-it-possible-to-enable-javascript-source-maps-in-safari-6
[4] http://wiki.eclipse.org/JSDT/Debug/IE

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

asm.js

[RyanZA]

Have a quick read through this article if you don't know what asm.js is:
http://arstechnica.com/information-technology/2013/05/native-level-performance-on-the-web-a-brief-examination-of-asm-js/

With firefox already supporting it, GWT should have the firefox compile 
target target asm.js for, at least, things like ArrayList.
I didn't see anything about it in the recent I/O talk - has anybody looked 
at how difficult it would be to support in the GWT compiler ?

Ryan

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.