Re: Request Context clear queue on method invocations when onConstraintViolation is called

[darren . hurt]

In fact I can't just make a new context and send cancel(Proxy).fire() to it 
as the proxy was created by the original request (the one holding the save 
call in its invocation queue) , and it tries to call edit on the proxy in 
the GWT internals when I call cancel on the new request (why, I don't know 
- I only want to pass it across as an argument, and have no intention of 
editing it in the new context) and then falls over because the proxy was 
already edited in the original request. 

I guess my cancel will have to take different arguments and do the query 
for the object I want to get hold of and clean up in my server code 
(annoying as I'll be duplicating what the find methods on the locator do - 
albeit my factoring will mean I can do it without duplicating code, but 
still.).

Any better ideas anyone?  


On Thursday, September 11, 2014 10:43:48 AM UTC+1, darre...@gmail.com wrote:
>
> What about if your request context interface has multiple methods?
>
> I have a save and a cancel on mine, and I have to use the cancel to do 
> some server side cleanup if the user decides to abandon their changes. If I 
> call save and it fails validation or whatever, and then the user decides to 
> cancel, then the save method invocation is still present on the request 
> context, when for a cancel call I only want a cancel call in the queue. I 
> really don't understand why there is no API for manipulating the invocation 
> queue, as it seems a valid thing to want to do.
> I can probably make a separate context for the cancel, and do it this way, 
> as in that case I'm not interested in anything that has changed in the 
> 'editing' context.
> Is this the right approach?
>
>

-- 
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/d/optout.

Re: GWT-SL 1.5 released

[Joseph Lust]

Thanks for your efforts. Clearly you've been working on this for some time.

I'm curious what this framework does beyond the existing Spring annotation 
driven integration with RPC. Using SpringGwtRemoteServiceServlet 
,
 
all the mapping of (annotated) service beans to paths can be done with 
Spring alone using @RemoteServiceRelativePath and extending RemoteService. 
In your loads of great documentation I see the ability to have XML files 
full of URL endpoint to bean mappings, which is more *Springy*. However, 
what else can you do here that generic Spring/GWT cannot? Thanks.

Joe

-- 
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/d/optout.

Re: Moving to Maven

[Magnus]

This even holds for the App.java generated by mvn with the archetype 
modular-webapp:

Import the Maven project in eclipse, open App.java, and hover "EntryPoint":
There is no tooltip like "com.google.gwt.core.client.EntryPoint", just 
nothing.

As a result, you also cannot automatically generate the needed imports.

The src/main/java folder looks like a normal "non-code" folder in eclipse.
It seems that eclipse does not recognize the file as java source code.

Can you fix this?

Magnus

-- 
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/d/optout.

Re: GWT-SL 1.5 released

[Thomas Broyer]

On Thursday, September 11, 2014 4:35:24 PM UTC+2, George Georgovassilis 
wrote:
>
> Dear all,
>
> It has been quiet for a while, but we're back with news:
>
>
>- The project repository moved to github: 
>https://github.com/ggeorgovassilis/gwt-sl
>- Updated dependencies to GWT 2.6 and Spring 3.2
>- There is a maven repository hosted on github now:
>
> 
> 
> gwt-sl-mvn-repo
> https://raw.github.com/ggeorgovassilis/gwt-sl/mvn-repo/
>
>
GitHub really should forbid serving binaries that way.
The way Maven handles repositories, you're basically mounting a DDoS 
against GitHub; this does not good to anyone.
You're also forcing everyone who wants to contribute to your repo to 
download *all of your binaries* because of the way Git (and DVCS in 
general) work (oh sure you can tell Git to only clone one single branch and 
then whitelist the branches you want to synchronize, but who would want to 
do that?!)


> and use it like this:
>
> 
> net.sf.gwt-widget
> gwt-sl
> 1.5
>
> There are still not any plans for moving the maven repository to maven 
> central, but the git hosted repository should get most of you going.
>
>
Deploy to Central or JCenter/BinTray; or possibly "host" your repo on 
GitHub Pages, but please don't deteriorate the service many of us rely on 
just because you're lazy (it's a one-time setup, probably even easier to 
setup than deploying into a branch of your Git repo!)
Sorry if that sounds harsh, but this madness has to stop!

-- 
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/d/optout.

Re: Unit Test for GWT Activities and Places

[Joseph Lust]

As Thomas points out, you can test your tokenizers and mappers in JUnit. 
Testing any higher level orchestration between them is more of an 
integration test. I leave these to some basic Selenium smoke tests that 
ensure that navigation between states works correctly.

Joe

-- 
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/d/optout.

Re: GWT-SL 1.5 released

[Juan Pablo Gardella]

Thanks!

On 11 September 2014 11:35, George Georgovassilis <
g.georgovassi...@gmail.com> wrote:

> Dear all,
>
> It has been quiet for a while, but we're back with news:
>
>
>- The project repository moved to github: https://github.com/
>ggeorgovassilis/gwt-sl
>- Updated dependencies to GWT 2.6 and Spring 3.2
>- There is a maven repository hosted on github now:
>
> 
> 
> gwt-sl-mvn-repo
> https://raw.github.com/ggeorgovassilis/gwt-sl/mvn-repo/
> 
> true
> always
> 
> 
>
> and use it like this:
>
> 
> net.sf.gwt-widget
> gwt-sl
> 1.5
>
> There are still not any plans for moving the maven repository to maven 
> central, but the git hosted repository should get most of you going.
>
> --
> The Server Library for GWT (gwt-sl) is a collection of server side GWT 
> utility classes, currently focusing on exposing Spring managed beans as RPC 
> services.
>
>  --
> 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/d/optout.
>

-- 
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/d/optout.

GWT-SL 1.5 released

[George Georgovassilis]

Dear all,

It has been quiet for a while, but we're back with news:


   - The project repository moved to github: 
   https://github.com/ggeorgovassilis/gwt-sl
   - Updated dependencies to GWT 2.6 and Spring 3.2
   - There is a maven repository hosted on github now:



gwt-sl-mvn-repo
https://raw.github.com/ggeorgovassilis/gwt-sl/mvn-repo/

true
always



and use it like this:


net.sf.gwt-widget
gwt-sl
1.5

There are still not any plans for moving the maven repository to maven central, 
but the git hosted repository should get most of you going.

--
The Server Library for GWT (gwt-sl) is a collection of server side GWT utility 
classes, currently focusing on exposing Spring managed beans as RPC services.

-- 
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/d/optout.

Re: Unit Test for GWT Activities and Places

[Thomas Broyer]

On Thursday, September 11, 2014 11:46:49 AM UTC+2, VaraKalyan Maddi wrote:
>
>
> Hi All,
>
> I couldn't get much documentation about unit testing for activities and 
> places.
> Can any one point me an example or an doc for this.
>

Well, there's not much to say.

PlaceTokenizers and ActivityMappers can quite easily be unit-tested.
Activities are a bit different, but you should be able to "simulate" their 
lifecycle from your test (call start()→mayStop()→onStop(), and/or 
start()→onCancel()). You can use a mock/stub/fake/dummy AcceptsOneWidget 
and a real event bus on which you'll listen to events (you might want to 
use a CountingEventBus).
And to test "navigation", you can use mock/stub/fake/dummy 
PlaceController.Delegate and/or PlaceHistoryHandler.Historian.

It all depends on what your activities are doing though, and possibly 
whether you're using MVP in your activities, and in which form (abstracting 
the view behind an interface –you can then mock/stub the view– vs. using 
UiBinder –you can then use GWTMockito from Google). The hardest is to 
mock/stub your data access, so you'd probably better abstract them behind 
interfaces you can easily mock/stub.

-- 
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/d/optout.

Unit Test for GWT Activities and Places

[VaraKalyan Maddi]

Hi All,

I couldn't get much documentation about unit testing for activities and 
places.
Can any one point me an example or an doc for this.


Thanks 
Kalyan

-- 
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/d/optout.

Re: Producing output with two different linkers at one compile

[Thomas Broyer]

On Thursday, September 11, 2014 10:36:22 AM UTC+2, Bora wrote:
>
> Is there a way to define two linkers and produce output from both to the 
> same output directory in GWT? the element "add-linker" does not actually 
> add a new linker but overrides the previously defined one.
>

This is only true for "primary" linkers.

There might be a way to do what you want (with two distinct primary 
linkers) by running the Precompile, CompilePerms and Link phases 
separately, so you could run the Link phase twice with the same input but 
different linkers. Not sure that would work though.
See https://code.google.com/p/google-web-toolkit/wiki/DistributedBuilds
Much easier to just compile twice ;-)

-- 
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/d/optout.

Re: Getting java.lang.NoClassDefFoundError: com.google.gwt.user.server.rpc.RemoteServiceServlet

[Thomas Broyer]

Do you have a gwt-servlet JAR in your webapp's WEB-INF/lib?
If not, look no further.

On Thursday, September 11, 2014 7:43:32 AM UTC+2, hihiren1 wrote:
>
> Hi,
>
> We have upgraded gwt 2.6.1. We have resolved all the deprecation warnings 
> which came due to gwt upgrade.
>
> Following is the stack trace of the problem.
> [9/11/14 10:45:52:489 IST] 0041 annotationW 
> com.ibm.ws.webcontainer.annotation.WASAnnotationHelper collectClasses 
> SRVE8000W: Skipped class that failed to initialize for annotation scanning.
>  java.lang.NoClassDefFoundError: 
> com.google.gwt.user.server.rpc.RemoteServiceServlet
> at 
> com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:853)
> at 
> com.ibm.ws.classloader.CompoundClassLoader.localFindClass(CompoundClassLoader.java:763)
> at 
> com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:586)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:707)
> at java.lang.Class.forNameImpl(Native Method)
> at java.lang.Class.forName(Class.java:224)
> at 
> com.ibm.ws.webcontainer.annotation.WASAnnotationHelper.loadClass(WASAnnotationHelper.java:771)
> at 
> com.ibm.ws.webcontainer.annotation.WASAnnotationHelper.collectClasses(WASAnnotationHelper.java:194)
> at 
> com.ibm.ws.webcontainer.annotation.WASAnnotationHelper.(WASAnnotationHelper.java:149)
> at 
> com.ibm.ws.webcontainer.annotation.WASAnnotationHelperManager.getAnnotationHelper(WASAnnotationHelperManager.java:63)
> at 
> com.ibm.ws.webcontainer.metadata.WebMetaDataFactory.handOffReferenceData(WebMetaDataFactory.java:440)
> at 
> com.ibm.ws.webcontainer.metadata.WebMetaDataFactory.createMetaData(WebMetaDataFactory.java:413)
> at 
> com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaDataFromFactories(MetaDataMgrImpl.java:228)
> at 
> com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaData(MetaDataMgrImpl.java:411)
> at 
> com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:631)
> at 
> com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:968)
> at 
> com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:774)
> at 
> com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2182)
> at 
> com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:445)
> at 
> com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
> at 
> com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:388)
> at 
> com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:116)
> at 
> com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:994)
> at 
> com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:502)
> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862)
> Caused by: java.lang.ClassNotFoundException: 
> com.google.gwt.user.server.rpc.RemoteServiceServlet
> at java.net.URLClassLoader.findClass(URLClassLoader.java:665)
> at 
> com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:204)
> at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:760)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:737)
> at 
> com.ibm.ws.bootstrap.ExtClassLoader.loadClass(ExtClassLoader.java:119)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:707)
> at 
> com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:62)
> at 
> com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:58)
> at 
> com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:584)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:707)
> at 
> com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:584)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:707)
> at java.lang.ClassLoader.defineClassImpl(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:306)
> at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154)
> ... 25 more
>
> [9/11/14 10:45:52:501 IST] 0041 annotationW 
> com.ibm.ws.webcontainer.annotation.WASAnnotationHelper collectClasses 
> SRVE8000W: Skipped class that failed to initialize for annotation scanning.
>  java.lang.ClassNotFoundException: 
> com.google.gwt.user.server.rpc.RemoteServiceServlet
> at java.lang.Class.forNameImpl(Native Method)
> at java.lang.Class.forName(Class.java:224)
> at 
> com.ibm.ws.webcontainer.annotation.WASAnnotationHelper.loadClass(WASAnnotationHelper.java:771)
> at 
> com.ibm.ws.webcontainer.annotation.WASAnnotationHelper.collectClasses(WASAnnotationHe

Re: Request Context clear queue on method invocations when onConstraintViolation is called

[darren . hurt]

What about if your request context interface has multiple methods?

I have a save and a cancel on mine, and I have to use the cancel to do some 
server side cleanup if the user decides to abandon their changes. If I call 
save and it fails validation or whatever, and then the user decides to 
cancel, then the save method invocation is still present on the request 
context, when for a cancel call I only want a cancel call in the queue. I 
really don't understand why there is no API for manipulating the invocation 
queue, as it seems a valid thing to want to do.
I can probably make a separate context for the cancel, and do it this way, 
as in that case I'm not interested in anything that has changed in the 
'editing' context.
Is this the right approach?

-- 
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/d/optout.

Producing output with two different linkers at one compile

[Bora]

Is there a way to define two linkers and produce output from both to the 
same output directory in GWT? the element "add-linker" does not actually 
add a new linker but overrides the previously defined one. 

-Bora

-- 
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/d/optout.