date:20130618

Re: Design Decision RPC with AsyncDataProvider

2013-06-18 Thread Jochen Schnaidt

Hi,

I now started to give my columns DataStoreNames, works much better for a 
couple of requirements.

Thank you so much for helping me on this topic.

Best regards

Jochen

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: RequestFactory, entity Id not populated when it reaches the server?

2013-06-18 Thread Thomas Broyer



On Monday, June 17, 2013 9:55:09 PM UTC+2, GWTter wrote:

 Hi,

 So I went back using the dev tools, inspected the payload, and confirmed 
 what I had before: the ID is not set at all in the user object payload. 
 Just to make sure I wasn't crazy or missing something I created just a User 
 object and tried to save it. I checked the payload in that request and 
 could clearly see the ID set in the object.

 I've persisted/sent entities that had field values set with other entities 
 before. The only difference I can make between the two cases is that in the 
 previous case the entity I was setting as the field value was from a 
 request to the server (I had not created it on the client). In this case 
 the booking entity is created on the client and the user entity is also 
 created on the client. Could this be the reason why it's failing? maybe 
 because RF only lets you add entities as fields if they already have 
 stableIDs? 

 Thanks again in advance.


If you can make a small repro case, please file an issue; it looks like a 
critical regression (which would also mean our test suite is weak)

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: JUnitShell: Why is the log level overriden to WARN?

2013-06-18 Thread Thomas Broyer



On Monday, June 17, 2013 10:54:16 PM UTC+2, Maik Riechert wrote:

 Hi,

 when developing JUnit runstyles I want to do info/trace logging, e.g.:

 shell.getTopLogger().log(TreeLogger.TRACE, Letting PhantomJS fetch  + 
 url);

 I have to change all those logging outputs to at least WARN to see 
 anything. This is caused by the following code in JUnitShell I guess:

   // Override log level to set WARN by default..
   registerHandler(new ArgHandlerLogLevel(options) {
 @Override
 protected Type getDefaultLogLevel() {
   return TreeLogger.WARN;
 }
   });

 My question is: Why? I find it very strange that I can't set a custom log 
 level via command line argument or system property. What is the reasoning 
 behind this and can it be changed?


You definitely *can* change the log level from the command line, WARN is 
just the default value.
Arguments are passed to JUnitShell through the gwt.args system property, 
the same you use to set your custom RunStyle: -Dgwt.args=-logLevel DEBUG 
-out www-test -runStyle com.example.PhantomJS:/path/to/phantomjs

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: JUnitShell: Why is the log level overriden to WARN?

2013-06-18 Thread Maik Riechert


Thomas Broyer wrote:
You definitely *can* change the log level from the command line, WARN 
is just the default value.
Arguments are passed to JUnitShell through the gwt.args system 
property, the same you use to set your custom RunStyle: 
-Dgwt.args=-logLevel DEBUG -out www-test -runStyle 
com.example.PhantomJS:/path/to/phantomjs


Hmm, I already tried setting the logLevel through the maven configuration:
https://github.com/neothemachine/KineticGWT/blob/master/pom.xml#L122

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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: AWS (CDN) GWT file deployment and 'Blocked a frame with origin' issue

2013-06-18 Thread Thomas Broyer

On Monday, June 17, 2013 7:26:43 PM UTC+2, Joseph Lust wrote:

Thomas,

Sorry I didn't catch you at the GWTogether in SF last month. I owe you a
number of beers. :)

*That did the trick*. I'll bang out an article for GWTProject.org on AWS
(and similar) CDN deployments.

BTW, I shamefully plead ignorance on the *xsiframe* linker. I'd only used
the linkers in the GWT
Docshttps://developers.google.com/web-toolkit/doc/latest/DevGuideOrganizingProjects#DevGuideModuleXml
.

Yet, a grepping against the GWT source reveals:

- appcachelinker (sample)
- direct_install
- xs
- sso
- std
- xsiframe

We'll need to ensure the new official
docshttp://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.htmlinclude
these as I've seen little documentation on most of them, or perhaps
I'm missing something and they're not all meant for prime time yet.

Yes, we need to document them (or update existing documentation) and
possibly deprecate a few of them.
When xsiframe was introduced a few releases ago, it was said that it could
eventually replace std as the default linker: it combines the best of
iframe (sandboxing in an iframe, DevMode) and xs (cross-origin), and is
modular and extensible (you can even plug your own script fragments
using set-configuration-property), and of course also brings
SuperDevMode. I think xs should be deprecated, maybe sso too (who
compiles a single permutation anyway?)
AFAICT, Google's linker (Server-Side Selection Script) is based on
xsiframe (or direct_install, which extends xsiframe)

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

49 matches

Mail list logo