jqm4gwt ver. 1.4.7 released

[Slava Pankov]

jqm4gwt is an advanced wrapper over the jQuery Mobile framework

GWT 2.8 is supported, see here https://github.com/jqm4gwt/jqm4gwt

-- 
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+unsubscr...@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: Unchanged transient field received as null on server using RequestFactory - how to force to send?

[TimOnGmail]

Ok - our code has a default finder used generically for all calls, though 
some locators override it.  I hadn't been very aware of it - it was this 
that was causing the issue.

Once I overrode the finder to fill in transient values, my problems went 
away.

Thanks for pointing me in the right direction!

- Tim

-- 
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+unsubscr...@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.

[gwt-contrib] org.eclipse.jetty.apache.jsp.JuliLog not a subtype

[Gordon Vidaver]

Hi,
 I've seen some comment on this but I'm trying to launch a gwt project from 
Jetbrains IDEA and I'm seeing the org.eclipse.jetty.apache.jsp.JuliLog not 
a subtype message as below.

 I'm trying to use gwt 2.8.0 but I'm not using maven to manage dependencies.

 Any suggestions on how to avoid this or debug it?  

 Thanks,
 Gordon

[Loaded com.google.gwt.dev.shell.jetty.JettyLauncher$ClientAuth from 
file:/Users/go22670/master/netPron2/gwt/gwt-dev.jar]
[main] WARN org.eclipse.jetty.util.component.AbstractLifeCycle - FAILED 
c.g.g.d.s.j.WebAppContextWithReload@2d408556{/,file:/Users/go22670/Library/Caches/IntelliJIdea2016.2/gwt/netPron2.a7aa86c3/netPron2.8dfd5ffa/run/www/,STARTING}{/Users/go22670/Library/Caches/IntelliJIdea2016.2/gwt/netPron2.a7aa86c3/netPron2.8dfd5ffa/run/www}:
 
java.util.ServiceConfigurationError: org.apache.juli.logging.Log: Provider 
org.eclipse.jetty.apache.jsp.JuliLog not a subtype
java.util.ServiceConfigurationError: org.apache.juli.logging.Log: Provider 
org.eclipse.jetty.apache.jsp.JuliLog not a subtype
[Loaded java.lang.Throwable$PrintStreamOrWriter from 
/Library/Java/JavaVirtualMachines/jdk1.8.0_111.jdk/Contents/Home/jre/lib/rt.jar]
[Loaded java.lang.Throwable$WrappedPrintStream from 
/Library/Java/JavaVirtualMachines/jdk1.8.0_111.jdk/Contents/Home/jre/lib/rt.jar]
at java.util.ServiceLoader.fail(ServiceLoader.java:239)
at java.util.ServiceLoader.access$300(ServiceLoader.java:185)
at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
at org.apache.juli.logging.LogFactory.(LogFactory.java:78)
at org.apache.juli.logging.LogFactory.(LogFactory.java:66)
at org.apache.jasper.servlet.JspServlet.(JspServlet.java:69)
at org.eclipse.jetty.jsp.JettyJspServlet.(JettyJspServlet.java:39)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at 
org.eclipse.jetty.server.handler.ContextHandler$Context.createInstance(ContextHandler.java:2372)
at 
org.eclipse.jetty.servlet.ServletContextHandler$Context.createServlet(ServletContextHandler.java:1166)
at 
org.eclipse.jetty.servlet.ServletHolder.newInstance(ServletHolder.java:1207)
at 
org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:588)
at 
org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:396)
at 
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:871)
at 
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
at 
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
at 
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
at 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
at 
com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:550)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at 
org.eclipse.jetty.server.handler.RequestLogHandler.doStart(RequestLogHandler.java:140)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.server.Server.start(Server.java:387)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:354)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at 
com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:759)
at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:634)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:923)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:706)
at com.google.gwt.dev.DevMode.main(DevMode.java:430)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 

Re: Bazel rules now available for GWT

[Brandon Donnelson]

Cool! Nice job!

On Thursday, October 27, 2016 at 2:10:54 PM UTC-7, Erik Kuefler wrote:
>
> In case anyone is looking into using Bazel  as 
> part of a GWT project, there are now some simple GWT rules available in the 
> Bazel repositories at https://github.com/bazelbuild/rules_gwt. These 
> rules have been updated to support GWT 2.8 and define a build target that 
> creates a .war file containing the GWT-compiled artifacts and a run target 
> that executes Super Dev Mode. Please report any problems on the issue 
> tracker .
>

-- 
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+unsubscr...@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: Google Plugin for Eclipse Mars

[Brandon Donnelson]

What version of Eclipse, mars or neon? Was there an earlier version 
installed? 

If GPE was previously installed and you're replacing it with the GWT 
Eclipse Plugin V3 there is a possibility there are some left over bits from 
the previous install causing issues. I added a conflict, although there are 
cases I've seen where the uninstall wasn't perfect. Check your plugins 
list, and be sure any previous plugins that were owned by GPE were removed 
before install. 

If that doesn't work, I'd suggest installing a clean version of Eclipse and 
installing the plugin. I haven't seen any issues with a clean install, at 
least not yet. You're should be ok to use the same working directory. 

Would that help? 

On Friday, October 28, 2016 at 2:26:54 AM UTC-7, Thomas Lacroix wrote:
>
>
> Le jeudi 27 octobre 2016 16:42:57 UTC+2, Brandon Donnelson a écrit :
>>
>> I'm not sure why the SDBG plugin failed to install. Those artifacts come 
>> from another repo. I would try again. 
>>
>>  
> It looks like my eclipse has a problem with installing the SGBD plugin, I 
> don't know why yet.
> I have opened a thread on the SGBD group for their input.
> In the meantime, when I install the GWT Eclipse Plugin V3 without SGBD it 
> seems to work fine.
> It says it could not create the view: com.google.gwt.eclipse.DevModeView 
> but I am able to debug in the browser dev tool.
> Thomas 
>

-- 
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+unsubscr...@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.

GWTReact release

[Paul Stockley]

I have pushed new versions of the GWTReact  
projects to support the final release of GWT2.8

The versions of the individual JS projects they depend on have also been 
updated as follows:

react 15.3.2,
react-dom 15.3.2
redux 3.5.2,
react-redux 4.4.5
redux-undo 1.0.0-beta
react-router 2.4.1
mobx 2.5.2
mobx-react 3.5.6
mobx-react-devtools 4.2.6

-- 
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+unsubscr...@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.

Code splitting and interfaces

[Rocco De Angelis]

Hi All,

I have a some problems with the GWT code splitting in the case that one 
module calls a method from another module that expect an interface.

Lets say that we two modules in our project named ModuleA and ModuleB. 
ModuleA is executing a method from ModuleB which expect an interface.
Now ModuleA is providing an implementation for that interface and calling 
ModuleB.

Here a very simple example: 



public class ModuleA {

public void execute() {
GWT.runAsync(ModuleA.class, new RunAsyncCallback() {
@Override
public void onFailure(Throwable throwable) {}

@Override
public void onSuccess() {
executeInternal();
}
});
}

private void executeInternal() {
ModuleAFunc moduleAFunc = new ModuleAFunc();
moduleAFunc.doSomething();

ModuleB.Callback callback = new ModuleB.Callback() {
@Override
public void done() {
ModuleAFunc moduleAFunc = new ModuleAFunc();
moduleAFunc.doSomething();
}
};

ModuleB moduleB = new ModuleB();

   moduleB.execute(callback);
}
}


public class ModuleB {

public void execute(Callback callback) {
GWT.runAsync(ModuleB.class, new RunAsyncCallback() {
@Override
public void onFailure(Throwable throwable) {}

@Override
public void onSuccess() {
ModuleBFunc moduleBFunc = new ModuleBFunc();
moduleBFunc.doSomething();
callback.done();
}
});
}

public interface Callback {
void done();
}
}


I would expect that the code of "ModuleAFunc" will be put into the splite 
point "ModuleA" and the code of "ModuleBFunc" will be added to the splite 
point "ModuleB".

But this is not the case. The code of the class "ModuleAFunc" will be moved 
into the left over code because the GWT compiler thinks that "
ModuleAFunc.doSomething" is also accessible from ModuleB because
ModuleB is executing the interface method Callback.done(). 
Somebody and idea how to handle this problem???

BR
Rocco


-- 
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+unsubscr...@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.

Problem with GWT RPC and Enhanced classes that are not.

[Will Phillips]

I have recently run into a problem with GWT RPC.  I use Hibernate and I 
send my entities over the wire using GWT-RPC.  Object graphs are 
transformed before they are sent to the client to snip unwanted references 
and replace lazy loading collections, similar to Gilead if my understanding 
is correct.  At any rate, the object graph being sent over RPC is intended 
to be a graph of POJO's, and this has seemingly worked well for several 
months until I unexpectedly received a deserialization error on the server. 
 I won't post the specifics of this error here or why it suddenly occurred; 
I have debugged it and the cause of the problem appears to be:

1.  My POJO's are also Hibernate Entities and are annotated with @Entity
2.  This annotation triggers the GWT-RPC SerializableTypeOracleBuilder to 
determine my class as "Maybe Enhanced"
3.  Being "maybe enhanced" triggers the GWT serialization framework to look 
for set() methods for setting fields and, where found, to use these in 
preference to direct field access when deserializing a graph.
4.  My classes are not enhanced (and if they were, I would not want them 
treated the way GWT RPC currently does; I find the implemented solution to 
enhanced classes makes me queasy).
5.  The implementation, as it stands, can call methods on partially 
deserialized objects.  I believe this has been a long standing issue with 
GWT-RPC which has been noted before with respect to Object.hashCode and 
Object.equals being called on partially deserialized objects while 
populating collections.  I wonder if RPC deserialization should proceed in 
two passes; one to construct all objects and silently set all fields on 
those objects and a second pass to allow collections and perhaps this 
bizarre Enhanced mechanism to call methods on these objects to finalize the 
graph.  However, this question is not the nature of my post.

My issue with this is that I am unable to find a satisfactory way to 
disable this "enhanced" class detection and subsequent serialization 
behaviour that it triggers.  What I want is field based serialization and 
deserialization.  My options for disabling this "feature" seem to be:
1.  Remove the @Entity annotation from by entity beans and declare them as 
entities in xml.  Not appealing to me; I like the simplicity and 
cleanliness of using annotations.
2.  Modify the set() methods on my Entity beans so that they avoid 
generating exceptions by accessing fields which may not have been 
deserialized yet.  This is one workaround, but it's not appealing either: I 
really don't want methods being called on my objects until they are fully 
deserialized, and I don't want to litter my code with checks which 
otherwise would not be there.  I already have a specific HashMap 
implementation I use for GWT serialization which avoids calling hashCode() 
or equals() during deserialization, but at least this is self-contained.
3.  Hammer the GWT ServiceInterfaceProxyGenerator to stop it declaring my 
classes enhanced.  I did this with some success - I use a custom SIPG which 
inherits from the GWT standard SIPG, and I forcibly unset the enhanced 
setting on all JClassType instances in an overridden generateTypeHandlers() 
method.  This works well - at least the .gwt.rpc files do not have 
@ClientFields entries in them, and RPC works fine.  However it is obviously 
horrible and not a permanent solution, but it is better to me than the 
alternatives.  Unfortunately, and more critically, it does not seem to work 
in SuperDev mode, which I use extensively.  Does anyone have any 
suggestions why this might be or how I can fix it?  Happy to post in detail 
about the errors experienced here if someone feels they might be able to 
shed light on it.

What I would really like is a way of turning off this enhanced class 
detection feature which works throughout the GWT toolchain...

Any help most gratefully received

- Will


-- 
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+unsubscr...@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: Google Plugin for Eclipse Mars

['Thomas Lacroix' via GWT Users]

Le jeudi 27 octobre 2016 16:42:57 UTC+2, Brandon Donnelson a écrit :
>
> I'm not sure why the SDBG plugin failed to install. Those artifacts come 
> from another repo. I would try again. 
>
>  
It looks like my eclipse has a problem with installing the SGBD plugin, I 
don't know why yet.
I have opened a thread on the SGBD group for their input.
In the meantime, when I install the GWT Eclipse Plugin V3 without SGBD it 
seems to work fine.
It says it could not create the view: com.google.gwt.eclipse.DevModeView 
but I am able to debug in the browser dev tool.
Thomas 

-- 
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+unsubscr...@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.