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:

<repositories>
    <repository>
        <id>gwt-sl-mvn-repo</id>
        <url>https://raw.github.com/ggeorgovassilis/gwt-sl/mvn-repo/</url>
        <snapshots>
            <enabled>true</enabled>
            <updatePolicy>always</updatePolicy>
        </snapshots>
    </repository>
</repositories>

and use it like this:

<dependency>
    <groupId>net.sf.gwt-widget</groupId>
    <artifactId>gwt-sl</artifactId>
    <version>1.5</version>
</dependency>

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.

[Juan Pablo Gardella]

Thanks!

--
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-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[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:

<repositories>
    <repository>
        <id>gwt-sl-mvn-repo</id>
        <url>https://raw.github.com/ggeorgovassilis/gwt-sl/mvn-repo/</url>

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:

<dependency>
    <groupId>net.sf.gwt-widget</groupId>
    <artifactId>gwt-sl</artifactId>
    <version>1.5</version>
</dependency>

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!

[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

[George Georgovassilis]

Hi Thomas

I follow you on twitter so I'm used to your way of communicating - no offence taken. That having said, the project always welcomes contributions be it patches or administrative support.

[George Georgovassilis]

Hi Joseph,

I don't know much about spring4gwt other than that the GWT-SL predates it by a while. After Robert Hanson and I released the SL in 2005 (or 2006, I forgot - at the time a SF project called "GWT Widget Library") it continuously evolved covering many corner cases such as exception translation. We also cooperated closely with the gilead (now defunc, I think) project that allowed transparent serialization of hibernate objects. The main idea is that the SL does not require that you extend any class; it rather works on an interface basis constructing proxies in run time that translate the GWT RPC protocol to method invocations on your POJO services. I personally use the SL for my own projects, so I've been keeping it up to date. Other than that, I see no reason to use the SL over anything else you feel comfortable with. After all, the best tools are the ones you know best :-)

[BRF]

It appears all the links to jectbd.com in the readme.md file are broken and go to a japanese hentai site now.

[George Georgovassilis]

BRF, I don't know what kind of weed you're on.

[BRF]

None. This link,http://jectbd.com/?p=1174, appears in the readme.md at least twice. I clicked it to read the referenced article and did not get the expected result. It goes to a site that has a bunch of japanese hentai images. I personally don't care, but was only trying to be helpful. I know if I wanted anyone to take my project seriously then I would want all the links to go to the correct locations. If that link does not take you to a japanese hentai site, please let mw know so that I can check wth is wrong on my end.

[George Georgovassilis]

That's probably the funniest goof I've made in a while... and I owe you
a big apology! Unfortunately I can't find the original article about RPC
payload inlining anymore which I think was written by Matt Mastracci.

[George Georgovassilis]

Correction, Alex Moffat from Lombardi. Still can't find the article.