Re: Firefox 13 DevMode Plugin

[Sudhakar Camilos]

Hi,

Where can I find FF13 plugin for Win64?
Empower your Business with BlackBerry® and Mobile Solutions from Etisalat

-Original Message-
From: Yuri C 
Sender: google-web-toolkit@googlegroups.com
Date: Fri, 8 Jun 2012 11:39:41 
To: 
Reply-To: google-web-toolkit@googlegroups.com
Subject: Re: Firefox 13 DevMode Plugin

I confirm 64bit linux is good. It even seems to run faster. Or is it just 
me  :)

On Thursday, June 7, 2012 3:46:49 PM UTC-4, koma wrote:
>
> working now fine on 64bit linux 
> thx !
>

-- 
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/-/gOpRUgeea4YJ.
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: GWT JSNI Callback

[Chris Price]

I'd assumed the bulk landing of messages was due to them being held in
a new-poster queue until being approved (normally on a Friday
morning)?

On Fri, Jun 8, 2012 at 8:55 PM, Joseph Lust  wrote:
> On May 30th, I submitted a reply. It then appeared as 'Deleted' in the
> thread. I rewrote it and submitted again. Then the next day it was undeleted
> and appeared in the web interface. Since I then had two of them, I deleted
> the first, but never deleted it on the 30th. Something wonky on their
> backend.
>
> Even weirder, on May 30th, I went from having 0 unread message on the group
> to a week's worth (all the way back to May 24th). You'll notice that a very
> large number of posts appeared from no where that day that no body had
> replied to yet and had no views, since they were living in some parallel
> universe until then.
>
> I wonder if it has to do with the 'eventual consistency' of DataStore on
> AppEngine? Anyway, I concur the groups interface can behave in odd ways.
>
>
>
> Joe
>
> --
> 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/-/6Mq6aZK5JMUJ.
>
> 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: GWT JSNI Callback

[Joseph Lust]

On May 30th, I submitted a 
reply.
 
It then appeared as 'Deleted' in the thread. I rewrote it and submitted 
again. Then the next day it was undeleted and appeared in the web 
interface. Since I then had two of them, I deleted the first, but never 
deleted it on the 30th. Something wonky on their backend.

Even weirder, on May 30th, I went from having 0 unread message on the group 
to a week's worth (all the way back to May 24th). You'll notice that a very 
large number of posts appeared from no where that day that no body had 
replied to yet and had no views, since they were living in some parallel 
universe until then.

I wonder if it has to do with the 'eventual consistency' of DataStore on 
AppEngine? Anyway, I concur the groups interface can behave in odd ways.



Joe

-- 
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/-/6Mq6aZK5JMUJ.
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 13 DevMode Plugin

[koma]

that's my impression too... could be FF13 being faster?

On Friday, June 8, 2012 8:39:41 PM UTC+2, Yuri C wrote:
>
> I confirm 64bit linux is good. It even seems to run faster. Or is it just 
> me  :)
>
> On Thursday, June 7, 2012 3:46:49 PM UTC-4, koma wrote:
>>
>> working now fine on 64bit linux 
>> thx !
>>
>

-- 
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/-/0kxNvDEfD0kJ.
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 13 DevMode Plugin

[Yuri C]

I confirm 64bit linux is good. It even seems to run faster. Or is it just 
me  :)

On Thursday, June 7, 2012 3:46:49 PM UTC-4, koma wrote:
>
> working now fine on 64bit linux 
> thx !
>

-- 
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/-/gOpRUgeea4YJ.
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+JPA Persistence.Exception source code not found

[jmbz84]

solved in 
http://stackoverflow.com/questions/10858772/gwtjpa-persistence-exception-source-code-not-found/10952567#10952567

-- 
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: Looking for Printing suggestions

[Thomas Mancini]

Thanks for the response.  I did try this approach, however it could
potentially become an issue that it's resetting the entire HTML each
time.  Even if I only get the next "chunk" each RPC, setInnerHtml
would have to also take in all of the previous chunks that were
retrieved.

On Jun 8, 10:40 am, jhulford  wrote:
> I would probably have the frame page itself be a simple entry point and
> just have it keep requesting your updated HTML content via an RPC and
> update your frame's innerHTML to set the content to the HTML returned by
> the call, you can probably even get it set to only return the "next" chunk
> of HTML instead of the whole page by remember some file marker (byte
> count?) that tells the servlet where the last read left off at.  I think
> this would probably fix your scrollbar issue as well since you're not
> reloading the page with each request, instead just resetting some innerHTML.
>
>
>
>
>
>
>
> On Thursday, June 7, 2012 3:11:12 PM UTC-4, Thomas Mancini wrote:
>
> > Hello All,
>
> > I am currently working on a GWT application that requires report
> > printing.  The use can select report parameters from a screen, and
> > upon clicking print we would like to display the file as it is being
> > generated.  Currently we have server side code that is generating HTML
> > and writing it to a file.  When the user clicks print, an RPC is being
> > made to pass the report parameters to the server and begin the
> > report.  A second RPC is made after the report has started to obtain
> > the report's URL.  From here, we are creating a Frame and setting the
> > URL to be the URL retrieved by the second RPC.
>
> > The issue I am currently running into, is that when setUrl gets
> > called, it only displays as much HTML that was contained in the file
> > at the time of the call.  What would be the best way to refresh just
> > the frame containing the HTML report?  It appears making subsequent
> > calls to setUrl passing in the same Url each time would do the trick,
> > but it actually doesn't seem to contain the additional content that
> > would've been written since the last call.  It is also resetting the
> > vertical scroll bar's position each time back to the top of the bar
> > which is something else I would like to prevent.  Is there a better
> > way to go about doing this?
>
> > Thanks.

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

Re: Invoke external servlet from gwt client

[Joseph Lust]

Have you tried 
JsonpRequestBuilderto
 get around the SOP?

Joe

-- 
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/-/UZJ2zUeB7MAJ.
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: compatibility issue between GWTGoogleMapsUtility and GWTGoogleMapsV3

[Joseph Lust]

Mario,

There is no MarkerCluster in the V3 Maps 
API. 
It is a 3rd party 
library.
 
As such, neither GWT V3 library 
(GWT-Maps-V3-APIor 
GWT-Google-Maps-V3 ) has this 
feature since it is not part of the API.

You'll need to wrap that library in a JSNI implementation. You said it is 
not working for you right now. What have you tried implementing so far?

Sincerely,
Joseph

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/HpJnuXvruxcJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RequestFactory - Error: The requested type is not default-instantiable

[zorro]

Dne pátek, 8. června 2012 16:48:47 UTC+2 Thomas Broyer napsal(a):
>
>
>
> On Friday, June 8, 2012 4:14:44 PM UTC+2, zorro wrote:
>>
>> Well, I have the requestFactory-apt set as annotation processor. But 
>> maybe problem is that the type that I wanted to create on server is an 
>> interface! And this is not covered by compiler at all!
>
>
> Would you mind filing an issue on the tracker?
> (DomainChecker should check that the type is instantiable, i.e. neither an 
> interface or an abstract class –or an enum!)
>

Actually, it would make sense that type is an Interface if used together 
with "locator". What do you think?
In my case I am using valueproxies only, since I am only sending "packages" 
of data that do not "live" on themselves on the server.

>  
>
>> Can I say to this magical RequestFactory stuff say what type to 
>> instantiate on the server, if interface is allowed (apparently) in the 
>> ProxyFor annotation?
>>
>
> You can use a Locator (on server-side, responsible for "instantiating your 
> interface") and link to it from the ProxyFor annotation.
>
> https://developers.google.com/web-toolkit/doc/latest/DevGuideRequestFactory#locators
>  
>
>> I woudl really appreciate that because I am using interfaces to get rid 
>> of tuns of necessary copying among proxy objects and real gwt objects. My 
>> original intention was to use gwt so I can move functionality execution 
>> easily from server to client. Therefore RF proxies in my case should be the 
>> same as the domain objects. Therefore interfaces.
>>
>
> In your case, I'd make sure to reference the real domain object (that 
> implements the same interface that the proxy extends).
> I suppose that's what you were willing to do, but somehow forgot to change 
> the ProxyFor value during the refactoring, and the bug in ValidationTool 
> didn't tell you you were wrong, right?
>

You are absolutely right here:- But I need to reference interfaces, cause 
this allows me to make types of proxies and my JSO objects more adjacent 
and thus save me some code. E.G. At least I can save some handcrated:- 
copying like this:

List toServerItems = syncPushToServer.getItems();
serverPush.setItems(new ArrayList(toServerItems)); 

I have 
1. public class SyncItem implements Serializable, ISyncItem {
@ProxyForName(value = "com.roamtopix.shared.SyncItem")
public interface SyncItemProxy extends ValueProxy {
   ..a lot of setters/getters
}

2.  @ProxyFor(IWindow.class) 
   public interface WindowProxy extends ValueProxy, IWindow {
   ..NOTING, everythig is on IWindow
   }

Difference between 1 and 2 is in what direction I need to "copy" objects on 
the client (from proxy to gwt-normal or JSO to gwt-normal or to gwt-proxy)
And can go with it. However I need interfaces to work in @ProxyFor annot. 
In my case IWindow is an interface. If I find out that this does not work 
wint EntityProxy I fill in that bug. 


 

-- 
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/-/jj4FdefObiAJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RequestFactory - Error: The requested type is not default-instantiable

[Thomas Broyer]

On Friday, June 8, 2012 4:14:44 PM UTC+2, zorro wrote:
>
> Well, I have the requestFactory-apt set as annotation processor. But maybe 
> problem is that the type that I wanted to create on server is an interface! 
> And this is not covered by compiler at all!


Would you mind filing an issue on the tracker?
(DomainChecker should check that the type is instantiable, i.e. neither an 
interface or an abstract class –or an enum!)
 

> Can I say to this magical RequestFactory stuff say what type to 
> instantiate on the server, if interface is allowed (apparently) in the 
> ProxyFor annotation?
>

You can use a Locator (on server-side, responsible for "instantiating your 
interface") and link to it from the ProxyFor annotation.
https://developers.google.com/web-toolkit/doc/latest/DevGuideRequestFactory#locators
 

> I woudl really appreciate that because I am using interfaces to get rid of 
> tuns of necessary copying among proxy objects and real gwt objects. My 
> original intention was to use gwt so I can move functionality execution 
> easily from server to client. Therefore RF proxies in my case should be the 
> same as the domain objects. Therefore interfaces.
>

In your case, I'd make sure to reference the real domain object (that 
implements the same interface that the proxy extends).
I suppose that's what you were willing to do, but somehow forgot to change 
the ProxyFor value during the refactoring, and the bug in ValidationTool 
didn't tell you you were wrong, right?

-- 
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/-/q4bAIHeQk5gJ.
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 JSNI Callback

[zorro]

Yep, You are right. No need for my callback to be JSO. Prevopisly I was 
passing it to another callback, oh no.
I need only call callback as $wnd.gwt.executeCallback(callback, param); and 
the example you gave applies.
Thanks


Dne pátek, 8. června 2012 14:09:43 UTC+2 Thomas Broyer napsal(a):
>
>
>
> On Friday, June 8, 2012 2:04:37 PM UTC+2, zorro wrote:
>>
>> "gwt-2.4.0/doc/helpInfo/jsoRestrictions.html" comes with GWT 
>> distribution. So far best readable document on the topic. However, a bit of 
>> disappointment. b/c It implies I can not implement callbacks in a neat way 
>> and in general.
>>
>> The example you pointed me two days ago is no more relevat, since it 
>> breaks all the RULES.
>>
>> https://code.google.com/p/gwt-in-the-air/source/browse/trunk/src/net/ltgt/gwt/browserplus/core/client/BrowserPlus.java#145
>>
>
> Not as long as Callback is not a JSO.
>  
>
>> From gwt-2.4.0/doc/helpInfo/jsoRestrictions.html:
>>
>> 4. JSO classes cannot have instance fields. -- this is waht callbacks 
>> are about.
>>
>> 2. An interface type may be implemented by at most one JSO subtype. -- 
>> this excludes possibility of having a general interface for callbacks
>>
>>
> Why the hell are you trying to have your callback extend JavaScriptObject 
> ?!
>
> Maybe you need to give more details on what you're trying to achieve.
>

-- 
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/-/uYcqe0HooeoJ.
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: Looking for Printing suggestions

[jhulford]

I would probably have the frame page itself be a simple entry point and 
just have it keep requesting your updated HTML content via an RPC and 
update your frame's innerHTML to set the content to the HTML returned by 
the call, you can probably even get it set to only return the "next" chunk 
of HTML instead of the whole page by remember some file marker (byte 
count?) that tells the servlet where the last read left off at.  I think 
this would probably fix your scrollbar issue as well since you're not 
reloading the page with each request, instead just resetting some innerHTML.

On Thursday, June 7, 2012 3:11:12 PM UTC-4, Thomas Mancini wrote:
>
> Hello All, 
>
> I am currently working on a GWT application that requires report 
> printing.  The use can select report parameters from a screen, and 
> upon clicking print we would like to display the file as it is being 
> generated.  Currently we have server side code that is generating HTML 
> and writing it to a file.  When the user clicks print, an RPC is being 
> made to pass the report parameters to the server and begin the 
> report.  A second RPC is made after the report has started to obtain 
> the report's URL.  From here, we are creating a Frame and setting the 
> URL to be the URL retrieved by the second RPC. 
>
> The issue I am currently running into, is that when setUrl gets 
> called, it only displays as much HTML that was contained in the file 
> at the time of the call.  What would be the best way to refresh just 
> the frame containing the HTML report?  It appears making subsequent 
> calls to setUrl passing in the same Url each time would do the trick, 
> but it actually doesn't seem to contain the additional content that 
> would've been written since the last call.  It is also resetting the 
> vertical scroll bar's position each time back to the top of the bar 
> which is something else I would like to prevent.  Is there a better 
> way to go about doing this? 
>
> Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/UdLgGX5ptwYJ.
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 architecture

[Jonathan Franchesco Torres Baca]

i'm propose this: http://www.youtube.com/watch?v=bFGeIh3Cyq0&feature=plcp

2012/6/8 Akram Moncer 

> thanks
>
>
> 2012/6/3 Gonzalo Ferreyra Jofré 
>
>> Hi Akram,
>>
>> you can start with this video
>> Google I/O 2009 - Best Practices for Architecting GWT 
>> App
>> or this one
>> Google I/O 2010 - Architecting GWT 
>> apps
>> and also this article from GWT web page
>> Large scale application development and 
>> MVP
>>
>> Bon courage!! ;)
>>
>> Gonzalo
>>
>> --
>> 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/-/ETwXfPwoCwUJ.
>> 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.
>>
>
>
>
> --
> Akram MONCER
> Etudiant à l' ENSI
> Tel: (+216)27753866
> CV: http://akram.moncer.netcv.com/
>
>  --
> 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: RequestFactory - Error: The requested type is not default-instantiable

[zorro]

Well, I have the requestFactory-apt set as annotation processor. But maybe 
problem is that the type that I wanted to create on server is an interface! 
And this is not covered by compiler at all! 

Can I say to this magical RequestFactory stuff say what type to instantiate 
on the server, if interface is allowed (apparently) in the ProxyFor 
annotation? 
I woudl really appreciate that because I am using interfaces to get rid of 
tuns of necessary copying among proxy objects and real gwt objects. My 
original intention was to use gwt so I can move functionality execution 
easily from server to client. Therefore RF proxies in my case should be the 
same as the domain objects. Therefore interfaces.

GWT RPC does not work for me for several reasons. One of them is that I can 
not obfuscate errors in the RPC.class everything is static and final. I can 
not hook in.


Dne pátek, 8. června 2012 14:29:46 UTC+2 Thomas Broyer napsal(a):
>
>
>
> On Friday, June 8, 2012 2:14:27 PM UTC+2, zorro wrote:
>>
>> Why the aforementioned error message "The requested type is not 
>> default-instantiable" does not include concrete type info?
>> It would speed up development.
>>
>
> I agree (kind of), though in theory this should have been caught up by the 
> ValidationTool at compile time (and really, it should: 
> http://code.google.com/p/google-web-toolkit/source/browse/tags/2.4.0/user/src/com/google/web/bindery/requestfactory/apt/DomainChecker.java#239
>  )
>
> In the mean time, set a breakpoint in ReflectiveServiceLayer and look at 
> the value of the clazz argument:
>
> http://code.google.com/p/google-web-toolkit/source/browse/tags/2.4.0/user/src/com/google/web/bindery/requestfactory/server/ReflectiveServiceLayer.java#84
>
>

-- 
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/-/tUWOMOBywC4J.
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 13 DevMode Plugin

[Jim Douglas]

Thanks, Alan!  Looks good on Mac OS X 10.7.4.

On Jun 7, 5:47 pm, Alan Leung  wrote:
> Last but not least, Mac:
>
> http://acleung.com/ff13-mac.xpi
>
> Enjoy and happy GWT hacking.
>
> -Alan
>
> On Thu, Jun 7, 2012 at 1:52 PM, Juan Pablo Gardella <
>
>
>
>
>
>
>
> gardellajuanpa...@gmail.com> wrote:
> > Thanks Alan!
>
> > 2012/6/7 Alan Leung 
>
> >> For folks with shinny Windows OSes.
>
> >>http://acleung.com/ff13-win.xpi
>
> >> -Alan
>
> >> On Thu, Jun 7, 2012 at 12:46 PM, koma  wrote:
>
> >>> working now fine on 64bit linux
> >>> thx !
>
> >>> --
> >>> 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/-/8dQJQ1FXteAJ.
>
> >>> 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.
>
> >  --
> > 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: Firefox 13 DevMode Plugin

[Dimitrijević Ivan]

Tested on Win 7 64bit.
So far so good.

On Friday, June 8, 2012 2:47:24 AM UTC+2, Alan Leung wrote:
>
> Last but not least, Mac:
>
> http://acleung.com/ff13-mac.xpi
>
> Enjoy and happy GWT hacking.
>
> -Alan
>
>
>
>
> On Thu, Jun 7, 2012 at 1:52 PM, Juan Pablo Gardella <
> gardellajuanpa...@gmail.com> wrote:
>
>> Thanks Alan!
>>
>>
>> 2012/6/7 Alan Leung 
>>
>>> For folks with shinny Windows OSes.
>>>
>>> http://acleung.com/ff13-win.xpi
>>>
>>> -Alan
>>>
>>> On Thu, Jun 7, 2012 at 12:46 PM, koma  wrote:
>>>
 working now fine on 64bit linux 
 thx !

 -- 
 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/-/8dQJQ1FXteAJ.

 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.
>>>
>>
>>  -- 
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/hKs4HZSPKPwJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: SuperDevMode and APT

[Stefano Ciccarelli]

The .gwt.rpc files are correctly generated in the war relative to the
CodeServer workDir, I have to found a way to copy them to the container war
when they change (not quite often), would be nice if the CodeServer could
do that for me :)


2012/6/8 Thomas Broyer 

>
>
> On Friday, June 8, 2012 2:18:28 PM UTC+2, Stefano Ciccarelli wrote:
>>
>> I know, I'm using App Engine as a servlet container. But the problem is
>> to generate .gwt.rpc files that are compatibles with the compiled
>> javascript generated by SuperDevMode.
>
>
> Oops, sorry; I read too fast.
>
> Switch to RequestFactory? ;-)
>
> More seriously, I doubt it'll ever be possible to use GWT-RPC with
> SuperDevMode, due to how/where it generates its output; though maybe you
> could tweak the way serialization policies are loaded on the server-side?
> (hmm, with AppEngine, that might be impossible, as you'd have to access
> files on the file-system; or maybe set SuperDevMode's workDir as a
> subfolder of your -war?)
>
> --
> 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/-/Rj4sG6PpW_oJ.
>
> 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.
>



-- 
Nel mondo esistono 10 categorie di persone, quelle che capiscono il binario
e quelle che non lo capiscono.

-- 
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: Getting data from nodejs server at GWT

[Thomas Broyer]

On Sunday, June 3, 2012 5:25:38 PM UTC+2, Kuenga wrote:
>
> HI,
>
> I have created a web server using NodeJS. At the server side, i have
> string of numbers (2,3,4). I want to convert it to Array object at the
> GWT object. I was not able to do.
>
> So was trying to display simple text message at GWT using the following 
> code:
>
> Window.alert("Connecting to server");
>String Strurl = "http://127.0.0.1:1337/";;
>RequestBuilder builder = new RequestBuilder(RequestBuilder.
> GET,
> URL.encode(Strurl));
>

Unless you run your GWT app from http://127.0.0.1:1337/ (which I doubt) or 
your NodeJS server at that URL sends back an appropriate 
Access-Control-Allow-Origin response header (see http://www.w3.org/TR/cors/ ), 
then onError will be called (and in browsers that do not support CORS, such 
as Internet Explorer, RequestBuilder#sendRequest() will throw)

-- 
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/-/_DnO8koil-AJ.
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: Server error code 413 - Request entity too large

[Thomas Broyer]

On Friday, June 8, 2012 2:48:14 PM UTC+2, Aldo wrote:
>
> Thank you Jens for you quick reply.
>
> I understand now what is going on. However, I still don't understand why 
> that part of the code is sending such huge amount of data to the server, so 
> do you know a way I can debug that? I tried enabling the 
> gwt.rpc.dumpPayload flag but that part is not even reached. I tried to 
> search where that error is raised but I didn't find it either.
>

Have you checked in your browser's developer tools (Firebug, Chrome Web 
Inspector, etc.) what goes on the wire?

-- 
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/-/RVWm9TwYQugJ.
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: Getting data from nodejs server at GWT

[Ümit Seren]

I have not much experience with node.js but I would recommend to use 
Chrome's Developer Tool or FireBug to check the XHTML request and response. 


On Sunday, June 3, 2012 5:25:38 PM UTC+2, Kuenga wrote:
>
> HI,
>
> I have created a web server using NodeJS. At the server side, i have
> string of numbers (2,3,4). I want to convert it to Array object at the
> GWT object. I was not able to do.
>
> So was trying to display simple text message at GWT using the following 
> code:
>
> Window.alert("Connecting to server");
>String Strurl = "http://127.0.0.1:1337/";;
>RequestBuilder builder = new RequestBuilder(RequestBuilder.
> GET,
> URL.encode(Strurl));
>try {
>Request request = builder.sendRequest(null, new 
> RequestCallback() {
>public void onError(Request request, Throwable exception) {
>// Couldn't connect to server (could be timeout, SOP
> violation, etc.)
>}
>public void onResponseReceived(Request request, 
> Response response) {
>if (200 == response.getStatusCode()) {
>// Process the response in 
> response.getText()
>Window.alert(response.getText());
>}
>else {
>//   Handle the error.  Can get the status text 
> from
> response.getStatusText()
>}
>
>}
>});
>Window.alert(request.toString());
>} catch (RequestException e) {
>
>}
>
>
> Got the 'Conecting to Server' alert message but do not get the alert
> message inside the RequestBuilder call back.
>
> Below the javascript code of Nodejs
>
> http.createServer(function (req, res) {
>
> res.writeHead(200, {'Content-Type': 'text/plain'});
> res.write("From node js");
>res.end();
> }).listen(1337, '127.0.0.1');
>
> How can i get the data at the GWT side from NodeJS server javascript code ?
>  
>
> Thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/Nl8RcUuYHUoJ.
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: Server error code 413 - Request entity too large

[Aldo Neto]

Thank you Jens for you quick reply.

I understand now what is going on. However, I still don't understand why
that part of the code is sending such huge amount of data to the server, so
do you know a way I can debug that? I tried enabling the
gwt.rpc.dumpPayload flag but that part is not even reached. I tried to
search where that error is raised but I didn't find it either.

I'm asking that because perhaps I'm doing something wrong by sending so
much data to the server, so I'd like to make sure before increasing the
server acceptance configuration.

Do you have any idea how to check that?

Thanks,
Aldo

On Thu, Jun 7, 2012 at 3:23 PM, Jens  wrote:

> I'm getting a very strange error here. When creating a new entry to an
>> entity, I'm getting a "Server error 413".
>>
>
> This basically means that your data you send to the server is too large
> and hits a limit configured somewhere on your server. So you should check
> how large your request is that fails and check your server documentation
> what default values apply for maximum form uploads, header/request/response
> buffers, etc and increase them as needed.
>
> However, the strange part is: I use this same creation in other place and
>> it works just fine.
>
>
> The data you send to the server is probably just a tiny bit smaller and
> thus it works because you don't hit a server limit anymore.
>
>
>> In addition to that, this problem only happens when I'm in development
>> mode. When I deploy the application, the error doesn't happen.
>>
>
> That would mean that your development mode server (GWT's embedded Jetty or
> anything else if you use -noserver) is configured differently (has
> different default values) than your server you deploy to. Or you possibly
> have load balancers in front of your deployment servers so that the whole
> situation is a bit different.
>
> In general its not bad seeing this error because it protects your server
> from being knocked down with very large (denial of service) requests. So
> don't go crazy and configure your server to accept 1GB of POST data or
> something. Configure it to a value that suites your needs.
>
> -- J.
>
>  --
> 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/-/euXk7NKJR2sJ.
> 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: SuperDevMode and APT

[Thomas Broyer]

On Friday, June 8, 2012 2:18:28 PM UTC+2, Stefano Ciccarelli wrote:
>
> I know, I'm using App Engine as a servlet container. But the problem is to 
> generate .gwt.rpc files that are compatibles with the compiled javascript 
> generated by SuperDevMode.


Oops, sorry; I read too fast.

Switch to RequestFactory? ;-)

More seriously, I doubt it'll ever be possible to use GWT-RPC with 
SuperDevMode, due to how/where it generates its output; though maybe you 
could tweak the way serialization policies are loaded on the server-side? 
(hmm, with AppEngine, that might be impossible, as you'd have to access 
files on the file-system; or maybe set SuperDevMode's workDir as a 
subfolder of your -war?)

-- 
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/-/Rj4sG6PpW_oJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RequestFactory - Error: The requested type is not default-instantiable

[Thomas Broyer]

On Friday, June 8, 2012 2:14:27 PM UTC+2, zorro wrote:
>
> Why the aforementioned error message "The requested type is not 
> default-instantiable" does not include concrete type info?
> It would speed up development.
>

I agree (kind of), though in theory this should have been caught up by the 
ValidationTool at compile time (and really, it should: 
http://code.google.com/p/google-web-toolkit/source/browse/tags/2.4.0/user/src/com/google/web/bindery/requestfactory/apt/DomainChecker.java#239
 )

In the mean time, set a breakpoint in ReflectiveServiceLayer and look at 
the value of the clazz argument:
http://code.google.com/p/google-web-toolkit/source/browse/tags/2.4.0/user/src/com/google/web/bindery/requestfactory/server/ReflectiveServiceLayer.java#84

-- 
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/-/Gqn8l8xCufcJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RequestFactory - Error: The requested type is not default-instantiable

[zorro]

That breakpoint really helped. (It is trying to instantiate an interface - 
due to some refactoring)

Dne pátek, 8. června 2012 10:00:41 UTC+2 Thomas Broyer napsal(a):
>
>
> On Friday, June 8, 2012 12:59:57 AM UTC+2, zorro wrote:
>>
>> Is there a way to find out WHICH TYPE other then scanning my large 
>> codebase?
>
>
> Isn't ValidationTool giving you warnings?
>
> You can also simply put a breakpoing into ReflectiveServiceLayer where 
> this error is reported and look at the value of the 'clazz' argument.
>

-- 
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/-/QRDoXlJOoCAJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: SuperDevMode and APT

[Stefano Ciccarelli]

I know, I'm using App Engine as a servlet container. But the problem is to
generate .gwt.rpc files that are compatibles with the compiled javascript
generated by SuperDevMode.


2012/6/8 Thomas Broyer 

>
>
> On Friday, June 8, 2012 2:04:48 PM UTC+2, Stefano Ciccarelli wrote:
>>
>> Yes, I've tried it and doesn't work, but the -cp solution works well.
>>
>> Now I have to understand how to deal with gwt-rpc because the server
>> misses .gwt.rpc files...
>>
>
> CodeServer is only about the "code server" part [1] (although it can serve
> your static resources too, for cases where you don't have server-side
> code), you still need a Servlet container if you have server-side code.
>
> [1]
> https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDebugging#DevGuideDevMode
>
> --
> 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/-/JBlBvMXgmrYJ.
>
> 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.
>



-- 
Nel mondo esistono 10 categorie di persone, quelle che capiscono il binario
e quelle che non lo capiscono.

-- 
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: RequestFactory - Error: The requested type is not default-instantiable

[zorro]

Compiler gives me errors related to JSNI. Nothing more.

>>Isn't ValidationTool giving you warnings? 

I have:

symbolMapsDirectory

WEB-INF/classes/symbolMaps/

And I am compiling with -extra WEB-INF/classes/symbolMaps

Q: Does this mean that errors will send stack traces ? 
Q: Does obfuscation apply to debugging mode as well?
--

Why the aforementioned error message "The requested type is not 
default-instantiable" does not include concrete type info?
It would speed up development.


Dne pátek, 8. června 2012 10:00:41 UTC+2 Thomas Broyer napsal(a):
>
>
> On Friday, June 8, 2012 12:59:57 AM UTC+2, zorro wrote:
>>
>> Is there a way to find out WHICH TYPE other then scanning my large 
>> codebase?
>
>
> Isn't ValidationTool giving you warnings?
>
> You can also simply put a breakpoing into ReflectiveServiceLayer where 
> this error is reported and look at the value of the 'clazz' argument.
>

-- 
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/-/HkkLUVCPk_cJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: SuperDevMode and APT

[Thomas Broyer]

On Friday, June 8, 2012 2:04:48 PM UTC+2, Stefano Ciccarelli wrote:
>
> Yes, I've tried it and doesn't work, but the -cp solution works well.
>
> Now I have to understand how to deal with gwt-rpc because the server 
> misses .gwt.rpc files...
>

CodeServer is only about the "code server" part [1] (although it can serve 
your static resources too, for cases where you don't have server-side 
code), you still need a Servlet container if you have server-side code.

[1] 
https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDebugging#DevGuideDevMode

-- 
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/-/JBlBvMXgmrYJ.
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 JSNI Callback

[Thomas Broyer]

On Friday, June 8, 2012 2:04:37 PM UTC+2, zorro wrote:
>
> "gwt-2.4.0/doc/helpInfo/jsoRestrictions.html" comes with GWT 
> distribution. So far best readable document on the topic. However, a bit of 
> disappointment. b/c It implies I can not implement callbacks in a neat way 
> and in general.
>
> The example you pointed me two days ago is no more relevat, since it 
> breaks all the RULES.
>
> https://code.google.com/p/gwt-in-the-air/source/browse/trunk/src/net/ltgt/gwt/browserplus/core/client/BrowserPlus.java#145
>

Not as long as Callback is not a JSO.
 

> From gwt-2.4.0/doc/helpInfo/jsoRestrictions.html:
>
> 4. JSO classes cannot have instance fields. -- this is waht callbacks are 
> about.
>
> 2. An interface type may be implemented by at most one JSO subtype. -- 
> this excludes possibility of having a general interface for callbacks
>
>
Why the hell are you trying to have your callback extend JavaScriptObject ?!

Maybe you need to give more details on what you're trying to achieve.

-- 
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/-/ys-0hlfMjGIJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: SuperDevMode and APT

[Stefano Ciccarelli]

Yes, I've tried it and doesn't work, but the -cp solution works well.

Now I have to understand how to deal with gwt-rpc because the server misses
.gwt.rpc files...

2012/6/8 Thomas Broyer 

> Are you sure "-src src -src .apt_generated" doesn't work?
>
>
> On Friday, June 8, 2012 12:36:22 PM UTC+2, Stefano Ciccarelli wrote:
>>
>> Hello,
>>
>> I'm poking with SuperDevMode just to understand how it works and I faced
>> the first problem: how to deal with APT generated classes? They are
>> generated to .apt_generated directory and aren't found by CodeServer, on
>> the other side I can only specify one dir as -src to CodeServer.
>>
>> Ideas?
>>
>> --
>> Nel mondo esistono 10 categorie di persone, quelle che capiscono il
>> binario e quelle che non lo capiscono.
>>
>  --
> 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/-/ovaa4RN1sqMJ.
>
> 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.
>



-- 
Nel mondo esistono 10 categorie di persone, quelle che capiscono il binario
e quelle che non lo capiscono.

-- 
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 JSNI Callback

[zorro]

"gwt-2.4.0/doc/helpInfo/jsoRestrictions.html" comes with GWT distribution. 
So far best readable document on the topic. However, a bit of 
disappointment. b/c It implies I can not implement callbacks in a neat way 
and in general.

The example you pointed me two days ago is no more relevat, since it breaks 
all the RULES.
https://code.google.com/p/gwt-in-the-air/source/browse/trunk/src/net/ltgt/gwt/browserplus/core/client/BrowserPlus.java#145
 

>From gwt-2.4.0/doc/helpInfo/jsoRestrictions.html:

4. JSO classes cannot have instance fields. -- this is waht callbacks are 
about.

2. An interface type may be implemented by at most one JSO subtype. -- this 
excludes possibility of having a general interface for callbacks

What this implies is that anythig more complex in JSNI boils down to 
TRAMPOLINE METHODS. Ugly. A lots of boilerplate code. 
The otherwise "closured" instance fileds (See 4. above) now have to be 
static Java fileds on the trapoline. (Trampoline is not very 
flexible/dynamic thing indeed) 


Dne pátek, 8. června 2012 9:57:09 UTC+2 Thomas Broyer napsal(a):
>
>
>
> On Friday, June 8, 2012 12:54:48 AM UTC+2, zorro wrote:
>>
>> Regarding callbacks there is one more error I am getting:
>> Only one JavaScriptObject type may implement the methods of an interface 
>> that declared methods.
>>
>> This
>> gwt-2.4.0/doc/helpInfo/jsoRestrictions.html
>> explains alot. But why nobody tell me that in the past? I mean tutorials, 
>> talks?
>>
>>
> You mean 
> https://developers.google.com/web-toolkit/doc/latest/DevGuideCodingBasicsOverlay
>  ?
>

-- 
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/-/M1YX8ISGOhcJ.
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: Problem installign gwt in eclipse

[Ed]

If your using AVG turn off link checker.

On Tue, Jun 5, 2012 at 1:14 PM, sahli sabrina  wrote:
> hi, i have eclipse version 3.5 and i want to set up gwt but i have
> always this error message T
>
> he operation cannot be completed. See the details.
>
>
> details
>
> Cannot complete the install because one or more required items could
> not be found.
> Software being installed: Google Plugin for Eclipse 3.5
> 2.6.1.v201205091048-rel-r35
> (com.google.gdt.eclipse.suite.e35.feature.feature.group
> 2.6.1.v201205091048-rel-r35)
> Missing requirement: Google Plugin for Eclipse 3.5 2.6.1.v201205091048-
> rel-r35 (com.google.gdt.eclipse.suite.e35.feature.feature.group
> 2.6.1.v201205091048-rel-r35) requires 'org.eclipse.mylyn.commons.ui
> 0.0.0' but it could not be
> found
> .
>
> can anyone help me to resolve this problem it is realy very important
> and urgent for me
>
> thank you
>
> --
> 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: SuperDevMode and APT

[Thomas Broyer]

Are you sure "-src src -src .apt_generated" doesn't work?

On Friday, June 8, 2012 12:36:22 PM UTC+2, Stefano Ciccarelli wrote:
>
> Hello,
>
> I'm poking with SuperDevMode just to understand how it works and I faced 
> the first problem: how to deal with APT generated classes? They are 
> generated to .apt_generated directory and aren't found by CodeServer, on 
> the other side I can only specify one dir as -src to CodeServer.
>
> Ideas?
>
> -- 
> Nel mondo esistono 10 categorie di persone, quelle che capiscono il 
> binario e quelle che non lo capiscono.
>  

-- 
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/-/ovaa4RN1sqMJ.
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 JSNI Callback

[zorro]

Yeap, the interface is a bit couterintuitive thanks to Czech translation 
that I am seeing. "Publicise your answer" should be "Reply publicly". 
Anyway.

Dne pátek, 8. června 2012 9:52:56 UTC+2 Thomas Broyer napsal(a):
>
>
>
> On Friday, June 8, 2012 12:19:57 AM UTC+2, zorro wrote:
>>
>> This Google Groups interface is F* HORRIBLE. I send a response and it 
>> disappears as I never send it.
>
>
> You probably clicked "Reply to Author", as I received the mail in my 
> inbox, sent to me only, not the group.
>

-- 
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/-/PnUAphDk6zEJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RequestFactory - Error: The requested type is not default-instantiable

[zorro]

There is no such

02:47:55.811 [ERROR] [roamtopix] Uncaught exception escaped

com.google.web.bindery.event.shared.UmbrellaException: One or more 
exceptions caught, see full set in UmbrellaException#getCauses
at 
com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext.fail(AbstractRequestContext.java:727)
at 
com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext$StandardPayloadDialect.processPayload(AbstractRequestContext.java:331)
at 
com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext$5.onTransportSuccess(AbstractRequestContext.java:1108)
at 
com.google.web.bindery.requestfactory.gwt.client.DefaultRequestTransport$1.onResponseReceived(DefaultRequestTransport.java:136)
at 
com.google.gwt.http.client.Request.fireOnResponseReceived(Request.java:287)
at 
com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:395)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
at 
com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
at 
com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
at 
com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:337)
at 
com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:218)
at 
com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)
at 
com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:561)
at 
com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:269)
at 
com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)
at com.google.gwt.core.client.impl.Impl.apply(Impl.java)
at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
at 
com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
at 
com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
at 
com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:292)
at 
com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:546)
at 
com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:363)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.RuntimeException: Server Error: The requested type is 
not default-instantiable
at 
com.google.web.bindery.requestfactory.shared.Receiver.onFailure(Receiver.java:44)
at 
com.google.web.bindery.requestfactory.shared.impl.AbstractRequest.onFail(AbstractRequest.java:118)
at 
com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext.fail(AbstractRequestContext.java:707)
at 
com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext$StandardPayloadDialect.processPayload(AbstractRequestContext.java:331)
at 
com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext$5.onTransportSuccess(AbstractRequestContext.java:1108)
at 
com.google.web.bindery.requestfactory.gwt.client.DefaultRequestTransport$1.onResponseReceived(DefaultRequestTransport.java:136)
at 
com.google.gwt.http.client.Request.fireOnResponseReceived(Request.java:287)
at 
com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:395)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
at 
com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
at 
com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
at 
com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:337)
at 
com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:218)
at 
com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)
at 
com.google.gwt.dev.shell.ModuleSpace.invokeNativ

Re: SuperDevMode and APT

[Jens]

Just put update the classpath, e.g. 

java -cp ./src:./.apt_generated: 
com.google.gwt.dev.codeserver.CodeServer

-- J.


Am Freitag, 8. Juni 2012 12:36:22 UTC+2 schrieb Stefano Ciccarelli:
>
> Hello,
>
> I'm poking with SuperDevMode just to understand how it works and I faced 
> the first problem: how to deal with APT generated classes? They are 
> generated to .apt_generated directory and aren't found by CodeServer, on 
> the other side I can only specify one dir as -src to CodeServer.
>
> Ideas?
>
> -- 
> Nel mondo esistono 10 categorie di persone, quelle che capiscono il 
> binario e quelle che non lo capiscono.
>  

-- 
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/-/CJF12JPkGGoJ.
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.

SuperDevMode and APT

[Stefano Ciccarelli]

Hello,

I'm poking with SuperDevMode just to understand how it works and I faced
the first problem: how to deal with APT generated classes? They are
generated to .apt_generated directory and aren't found by CodeServer, on
the other side I can only specify one dir as -src to CodeServer.

Ideas?

-- 
Nel mondo esistono 10 categorie di persone, quelle che capiscono il binario
e quelle che non lo capiscono.

-- 
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.

Reading configuration properties in GWT server side code - GinModule

[benb]

Hi,
I'm trying to read some configuration values in my GinModule. I want
to bind specific components according to this configuration. The
configuration is set up during maven build according, influenced by
the maven profile.

I started with the obvious solution adding some
configuration.properties file with IConfiguration interface using the
i18n framework but it seems that calling GWT.create() won't work - I
get an exception that it can work only on client side code.

Another option I though possible is to add custom properties to the
gwt.xml file, but I'm not sure how to do that and how to read this
file.

I don't need my configuration to be localized or anything, just a
simple file that can be accessed easily.

Any suggestions?

-- 
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 JSNI Callback

[Thomas Broyer]

On Fri, Jun 8, 2012 at 12:15 AM, zorro  wrote:
> I am getting, when compiled with TRACE
> Error, ... references to instance methods in overlay types are illegal; use
> a stronger type or a Java trampoline method
>
> From the compiler output I found out there is:
> gwt-2.4.0/doc/helpInfo/jsoRestrictions.html
>
> There is no link to this from
> https://developers.google.com/web-toolkit/doc/latest/DevGuideCodingBasicsJSNI

Because JSOs have their own section in the Dev Guide:
https://developers.google.com/web-toolkit/doc/latest/DevGuideCodingBasicsOverlay

In this case, see
http://code.google.com/p/google-web-toolkit/wiki/OverlayTypes#Restrictions
(linked to at the bottom of the above-mentioned page):
“Native JSNI methods may not refer to instance methods within
@SingleJsoImpl types, just as they may not refer to instance methods
on overlay types.”
(note that @SingleJsoImpl doesn't actually exist, it was in an earlier
iteration, now the GWT Compiler infers it from how it's actually being
used)

What it means is that if you have a JavaScriptObject subclass
com.example.client.Foo with a "public final bar()" method (native or
not), you cannot write in JSNI:
   someo...@com.example.client.foo::bar()();
This is due to how JSOs are handled by the compiler: all methods are
transformed into static methods, they're not instance methods on the
JavaScript object (a JSO is just a Java "view" of a JS object).

> btw, What is "trampoline method"? Sounds good;-)

public static void trampoline_to_bar(Foo foo) {
  foo.bar();
}

Then you can use in JSNI:
@com.example.client.Trampoline::trampoline_to_bar(Lcom/example/client/Foo;)(someObj);

-- 
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: textbox in showcase lower right corner, has a dragger to resize the textbox

[Thomas Broyer]

On Friday, June 8, 2012 10:08:10 AM UTC+2, tong123123 wrote:
>
> in the showcase
> http://gwt.google.com/samples/Showcase/Showcase.html#!CwBasicText
> the textbox lower right corner has a dragger to resize the textbox, how to 
> do it?
>
>  I try
>
>> TextArea ta = new TextArea();
>>  ta.setCharacterWidth(80);
>>  ta.setVisibleLines(5);
>>
>
>
> but the textbox generated has no such a resize dragger.
>
>
It might because of setCharacterWidth(), that's the only difference from 
the showcase.
Anyway, the dragger is "native", added and handled by your browser, so it 
also depends which browser you use.

-- 
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/-/ExHPsmf76mcJ.
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: textbox in showcase lower right corner, has a dragger to resize the textbox

[Jens]

Its a CSS3 property named "resize", 
see: http://www.w3schools.com/cssref/css3_pr_resize.asp

Currently only supported on the browsers listed 
at: http://caniuse.com/#search=resize

-- J.

-- 
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/-/MHBANlTY-_gJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT 2.5 SuperDevMode

[Thomas Broyer]

On Friday, June 8, 2012 9:51:10 AM UTC+2, Thomas Broyer wrote:
>
>
> SuperDevMode is not currently integrated into the build, even less 
> producing a Maven artifact (I posted a review for this, which has been 
> LGTM'd but hasn't yet landed in trunk).
>

Oh oops, looks like it has, a few hours ago: 
http://code.google.com/p/google-web-toolkit/source/detail?r=11030

>

-- 
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/-/ZaBhbQlj5x0J.
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.

textbox in showcase lower right corner, has a dragger to resize the textbox

[tong123123]

in the showcase
http://gwt.google.com/samples/Showcase/Showcase.html#!CwBasicText
the textbox lower right corner has a dragger to resize the textbox, how to 
do it?

 I try

> TextArea ta = new TextArea();
>  ta.setCharacterWidth(80);
>  ta.setVisibleLines(5);
>


but the textbox generated has no such a resize dragger.

-- 
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/-/tPBtgdY_2xcJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RequestFactory - Error: The requested type is not default-instantiable

[Thomas Broyer]

On Friday, June 8, 2012 12:59:57 AM UTC+2, zorro wrote:
>
> Is there a way to find out WHICH TYPE other then scanning my large 
> codebase?


Isn't ValidationTool giving you warnings?

You can also simply put a breakpoing into ReflectiveServiceLayer where this 
error is reported and look at the value of the 'clazz' argument.

-- 
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/-/YF2eYkq68ycJ.
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 JSNI Callback

[Thomas Broyer]

On Friday, June 8, 2012 12:54:48 AM UTC+2, zorro wrote:
>
> Regarding callbacks there is one more error I am getting:
> Only one JavaScriptObject type may implement the methods of an interface 
> that declared methods.
>
> This
> gwt-2.4.0/doc/helpInfo/jsoRestrictions.html
> explains alot. But why nobody tell me that in the past? I mean tutorials, 
> talks?
>
>
You mean 
https://developers.google.com/web-toolkit/doc/latest/DevGuideCodingBasicsOverlay
 ?

-- 
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/-/HGkIQXZJyRQJ.
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 JSNI Callback

[Thomas Broyer]

On Friday, June 8, 2012 12:19:57 AM UTC+2, zorro wrote:
>
> This Google Groups interface is F* HORRIBLE. I send a response and it 
> disappears as I never send it.


You probably clicked "Reply to Author", as I received the mail in my inbox, 
sent to me only, not the group.

-- 
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/-/yYNyLqyLrfUJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT 2.5 SuperDevMode

[Thomas Broyer]

On Thursday, June 7, 2012 10:52:35 PM UTC+2, Adriano Machado wrote:
>
> How to use the recently commited SuperDevMode in a maven project? Is there 
> a snapshot build of it in the central repo? 
>

There's no snapshot published by Google. Also, SuperDevMode is not 
currently integrated into the build, even less producing a Maven artifact 
(I posted a review for this, which has been LGTM'd but hasn't yet landed in 
trunk).
That being said, have a look here: 
https://vaadin.com/blog/-/blogs/vaadin-and-superdevmode

-- 
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/-/1FWgkiNUWM8J.
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: Resubmitting RequestFactory request when server side logic requires it

[Thomas Broyer]

On Thursday, June 7, 2012 10:40:23 PM UTC+2, Ryan McFall wrote:
>
> Thanks, Thomas, I searched through the methods in 
> ServiceLayerDecorator for something like this, but somehow missed 
> these. 
>
> Using report() from with the ServiceLayerDecorator doesn't allow me to 
> re-fire the RequestFactory request, giving me the "A request is 
> already in progress" error.  If I call die() then the exception is 
> still printed out, but the onFailure method of the Receiver is in fact 
> called, and I can re-fire the request.


Be careful though: if you enqueued two invocations in your context, and the 
second one generated the die() exception (meaning the first one has been 
processed), when sending the request a second time, the first invocation 
will be processed a second time too, so it'd better be idempotent! 

-- 
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/-/bY-yvxElckMJ.
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.