Google Web Toolkit: October 2017

Tuesday, October 31, 2017

Re: Migrating from GWT 2.5.1 to 2.8.2 - Problem with Super dev mode

Hi Thomas,

Many thanks for your time and answer! I was indeed playing with the legacy plugin ... :) Things work much better now. The super dev mode is really great by the way.

I used your plugin and revamped slightly the client project (moved my main mymodule.gwt.xml to /src/main/java/module.gwt.xml and all my sources to /src/main/java). I'm then running code server with launcherDir arg pointing to my php root.

As for the downside of overriding nocache.js, I think the ideal process of deploying is compiling within a CI chain so it won't matter at all :)

Many thanks again,

Ludovit

Le mardi 31 octobre 2017 11:41:31 UTC+1, Thomas Broyer a écrit :

On Tuesday, October 31, 2017 at 10:31:39 AM UTC+1, Martones wrote:
Hey guys,

I'm trying to migrate my app which looks like this :
GWT 2.5.1 front, PHP back, no maven -> GWT 2.8.2 front, PHP back, maven with gwt-maven-plugin.

I manage to mvn gwt:compile and mvn gwt:run-codeserver.

I actually think I'm confused about how the SDM runs now in 2.7+ but here is what I was thinking :
Run compile (optional ? ) via mvn gwt:compile
Run code server via mvn gwt:run-codeserver
Save the bookmarklet and compile via the popup on my gwt page
re-compile on every code change manually

In 2.7+, you can do:
Run code server with -launchDir pointing to the directory served by your server
(there's no other step, code server will automatically compile/recompile on page load)
With Mojo's plugin (you did notice the maintainer now "strongly encourage[s you] to use the new [plugin]" though, right? see https://gwt-maven-plugin.github.io/gwt-maven-plugin/ ), that's <launcherDir> and <webappDirectory>.

The only downside is that code server when run this way will overwrite the mymodule.nocache.js, so make sure you recompile the app before packaging/deploying (gwt-maven-plugin staleness check might be confused, so "mvn clean", or force recompilation with -Dgwt.compiler.force)

The third point is the one that isn't working anymore (was ok in 2.5.1). In the popup I have :

mymodule : off This module doesn't have Super Dev Mode enabled.

Here is my module file: removed all the SDM lines that I understood are now useless, doesn't work anyway if I keep them :)

<module rename-to='mymodule'>    <entry-point class="com.mycompany.mymodule.client.mymodule"></entry-point>  <source path='client' /> <source path='shared' />   <set-configuration-property name="CssResource.conversionMode" value="strict" /> </module>

I'm serving my php page from a docker container on my localhost (so no HTTPS).

Any help is much appreciated :)

Ludovit

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: RequestBuilder, safely send data to server

HI Thomas, are the GWT methods XsrfProtectedService on client side and XsrfProtectedServiceServlet on server side still experimental? The GWT documentation has described csrf protection in detail using them... Can I follow that?

On Thursday, 2 March 2017 17:19:11 UTC+2, Thomas Broyer wrote:

On Thursday, March 2, 2017 at 8:01:18 AM UTC+1, gitzzz wrote:
Hi! I use RequestBuilder for client-server communication. And I have some questions:

For example we make http request to ".../get.php"(function(), select some data from DB and send it back). Response is an array[1,2,3,4,5]

On client side onTheButtonClick we can change the data, the new_array[1,3,6,8,9], and now we need to send this changes to DB. And onSaveButtonClick() we make http post request to ".../set.php" with parameters = new_array

The question is: does it safe? Is it possible that anybody authed user can make this call by creating JS script with http post request and send his own(fake) data?(e.g. fake_array[10,20,30,23,12]) without clicking a button. How can I send change data from client side to a server safely?

What you're describing is a Cross-Site Request Forgery (CSRF) attack and is absolutely possible.
Your server code needs to check the origin of the request to prevent them (if there's an Origin header, use it, otherwise use the Referer header; check that the scheme, hostname and port match the current request –or any origin you decide to trust for issuing such requests–; and if there's neither you should refuse the POST request, but you should know that some corporate proxies remove Referer headers, so without HTTPS to prevent this man-in-the-middle situation you're going to need CSRF "tokens" and this is a bit painful to manage correctly).
See https://www.w3.org/TR/cors/ for the gory details.

GWT csrf protection

Gwt Documentation http://www.gwtproject.org/doc/latest/DevGuideSecurityRpcXsrf.html as well as GWT IN action https://manning-content.s3.amazonaws.com/download/d/07888ea-bada-44cc-9c55-ead15ea7fe85/GWT_sample-07.pdf recommend extending XsrfProtectedService on client side and XsrfProtectedServiceServlet on server side....

But both thse methods are still marked as "EXPERIMENTAL and subject to change. Do not use this in production code. "

What gives? is this a leftover - or are they now safe to use in production?

Thanks for your help in advance!

Re: Migrating from GWT 2.5.1 to 2.8.2 - Problem with Super dev mode

On Tuesday, October 31, 2017 at 10:31:39 AM UTC+1, Martones wrote:

Hey guys,

I'm trying to migrate my app which looks like this :
GWT 2.5.1 front, PHP back, no maven -> GWT 2.8.2 front, PHP back, maven with gwt-maven-plugin.

I manage to mvn gwt:compile and mvn gwt:run-codeserver.

I actually think I'm confused about how the SDM runs now in 2.7+ but here is what I was thinking :
Run compile (optional ? ) via mvn gwt:compile
Run code server via mvn gwt:run-codeserver
Save the bookmarklet and compile via the popup on my gwt page
re-compile on every code change manually

In 2.7+, you can do:

Run code server with -launchDir pointing to the directory served by your server

(there's no other step, code server will automatically compile/recompile on page load)

With Mojo's plugin (you did notice the maintainer now "strongly encourage[s you] to use the new [plugin]" though, right? see https://gwt-maven-plugin.github.io/gwt-maven-plugin/ ), that's <launcherDir> and <webappDirectory>.

The only downside is that code server when run this way will overwrite the mymodule.nocache.js, so make sure you recompile the app before packaging/deploying (gwt-maven-plugin staleness check might be confused, so "mvn clean", or force recompilation with -Dgwt.compiler.force)

The third point is the one that isn't working anymore (was ok in 2.5.1). In the popup I have :

mymodule : off This module doesn't have Super Dev Mode enabled.

Here is my module file: removed all the SDM lines that I understood are now useless, doesn't work anyway if I keep them :)

<module rename-to='mymodule'>    <entry-point class="com.mycompany.mymodule.client.mymodule"></entry-point>  <source path='client' /> <source path='shared' />   <set-configuration-property name="CssResource.conversionMode" value="strict" /> </module>

I'm serving my php page from a docker container on my localhost (so no HTTPS).

Any help is much appreciated :)

Ludovit

Migrating from GWT 2.5.1 to 2.8.2 - Problem with Super dev mode

Hey guys,

I'm trying to migrate my app which looks like this :

GWT 2.5.1 front, PHP back, no maven -> GWT 2.8.2 front, PHP back, maven with gwt-maven-plugin.

I manage to mvn gwt:compile and mvn gwt:run-codeserver.

I actually think I'm confused about how the SDM runs now in 2.7+ but here is what I was thinking :

Run compile (optional ? ) via mvn gwt:compile
Run code server via mvn gwt:run-codeserver
Save the bookmarklet and compile via the popup on my gwt page
re-compile on every code change manually

The third point is the one that isn't working anymore (was ok in 2.5.1). In the popup I have :

mymodule : off This module doesn't have Super Dev Mode enabled.

Here is my module file: removed all the SDM lines that I understood are now useless, doesn't work anyway if I keep them :)

<module rename-to='mymodule'>
 <!-- Inherits -->
        <!-- ... -->

 <!--  Entry point -->
 <entry-point class="com.mycompany.mymodule.client.mymodule"></entry-point>

 <!-- paths -->
 <source path='client' />
 <source path='shared' />

 <!--  SDM  -->
  <!-- <add-linker name="xsiframe"/>
  
  <set-configuration-property name="devModeRedirectEnabled" value="true"/>
 <set-property name="compiler.useSourceMaps" value="true"/> -->
  
  <set-configuration-property name="CssResource.conversionMode"    value="strict" />
</module>

I'm serving my php page from a docker container on my localhost (so no HTTPS).

Any help is much appreciated :)

Ludovit

Monday, October 30, 2017

elemental2 and create object url?

How do I access URL.createObjectUrl(Blob) using elemental2?

Re: Element may only contain a single child element, but found (:3)

When removing all the details of your UiBinder the file looks like:

<!DOCTYPE ui:UiBinder SYSTEM "http://dl.google.com/gwt/DTD/xhtml.ent">
<ui:UiBinder xmlns:ui="urn:ui:com.google.gwt.uibinder"
 xmlns:g="urn:import:com.google.gwt.user.client.ui">

  <ui:with type="com.folder.client.resources.Css" field="CSS" />
  <ui:with type="com.folder.client.resources.Strings" field="STRINGS" />

  <ui:style type="com.folder.client.presenters.main.common.dialog.HelpDialog.LocalStyle">
    // ....
  </ui:style>
 
  // the first root element inside <ui:uibinder>
  <g:HTMLPanel ui:field="uiPanelOptions" >

  </g:HTMLPanel>

  // the second root element inside <ui:binder>
  <g:HTMLPanel ui:field="uiPanelFooter">

  </g:HTMLPanel>


</ui:UiBinder>

With UiBinder you can only have a single Widget / Element inside the <ui:UiBinder> tag. You would need to wrap your two HTMLPanels with a third one. The reason is that in your Java code the call to uibinder.createAndBindUi(this) returns this single Widget / Element. So you can not have two root Widgets / Elements.

-- J.

Element may only contain a single child element, but found (:3)

<!DOCTYPE ui:UiBinder SYSTEM "http://dl.google.com/gwt/DTD/xhtml.ent">

<ui:UiBinder xmlns:ui="urn:ui:com.google.gwt.uibinder"

xmlns:g="urn:import:com.google.gwt.user.client.ui">

<ui:with type="com.folder.client.resources.Css" field="CSS" />

<ui:with type="com.folder.client.resources.Strings" field="STRINGS" />

<ui:style

type="com.folder.client.presenters.main.common.dialog.HelpDialog.LocalStyle">

.title {

padding-top: 30px;

padding-bottom: 20px;

padding-left: 80px;

padding-right: 80px;

color: #555555;

text-align: center;

font-weight: 700;

font-size: 30px;

font-family: 'Titillium Web', sans-serif;

padding-bottom: 20px;

}

.scroll {

max-height: 280px;

overflow-x: hidden;

overflow-y: auto;

}

.options {

width: 100%;

color: #555555;

text-align: center;

font-weight: 400;

font-size: 24px;

font-family: 'Titillium Web', sans-serif;

margin-left: auto;

margin-right: auto;

padding-left: 40px;

padding-right: 40px;

padding-bottom: 20px;

}

.options li {

text-align: left;

}

.options>div {

text-align: center;

padding-bottom: 40px;

}

.option-divider {

position: relative;

display: inline-block;

height: 20px;

top: 15px;

border-left: 1px solid rgba(0, 0, 0, 0.15);

}

.image {

width: 60px;

height: 60px;

margin: 10px;

margin-right: 20px;

}

.dialog {

width: 620px;

height: 300px;

min-height: 300px;

left: 0;

right: 0;

margin-left: auto;

margin-right: auto;

}

.content {

padding: 0px !important;

}

</ui:style>

<g:HTMLPanel ui:field="uiPanelOptions" >

<g:FocusPanel ui:field="uiPanelWelcomeTutorial" styleName="{style.options}">