Spring 3.0.3 is Now Available

24 June 2010

I realize that this is old news from last week, but still …

Juergen Hoeller has announced that Spring 3.0.3 is now available. This minor release addresses over 100 minor issues and catches up with some recent third-party releases.

Download | Documentation | Javadoc API | Change Log | JIRA

Please note that we are not providing a dependencies download anymore. The recommended way of obtaining third-party libraries for use with Spring is Maven/Ivy; you could also download third-party distributions of your choice and take the jars from there. Note that there is no reason to upgrade third-party libraries unless you want to: The simplest solution is to keep using the versions that you know and trust.

Don’t forget that Spring users can ask questions in the community forum and identify issues in JIRA as well.

Sun CEO Announces Resignation On Twitter

4 February 2010

I always enjoyed the blog … nothing lasts forever, though:

Jonathan Schwartz was considered a longshot to stay at Sun after its acquisition by Oracle.

Sun Microsystems CEO Jonathan Schwartz, an advocate of Web 2.0, used Twitter early Thursday to announce his resignation. He was named CEO in 2006 as Sun faced a switch in strategic direction away from proprietary systems and toward open source code, including its valued Solaris 10 operating system.
“Today’s my last day at Sun. I’ll miss it,” he said in a tweet to his followers, reported the New York Times on its Web site at 1:12 a.m. Thursday. He added a bit of haiku: “Financial crisis, Stalled too many customers, CEO no more.”
Schwartz was the first CEO of a major company to use the blogging format to announce his positions and comment on issues in the industry. He advocated that blogs be given the same status as press releases with the Securities Exchange Commission. The New York Times observed that he’s the first Fortune 200 executive to use Twitter to announce his resignation.

Read the whole article on Information Week.

Time for a new job?

15 January 2010

Looking for that challenging position where you can show off your skills and have fun playing with new stuff all at the same time? SpringSource is looking for a few good candidates:

SpringSource is looking for some talented engineers to join the team of experts in the Research and Development group. If you enjoy challenging, genuinely rewarding roles that offer unique opportunities to work with industry leading technologists on open source based projects and products, then be sure to take a look at the following positions:

Spring 3.0.0 and Maven

17 December 2009

First of all, it’s always best to read the instructions.

Second, if you were successfully using the last Spring 3 release candidate in your Maven project, you cannot simply pull up the pom.xml in an editor and change all “.RC3″ to “”. Actually, to be completely accurate, you can do that — you’ll just get a “Build Failed” when you attempt to build your project. The official name of the GA release of Spring 3 is not 3.0.0 — it’s 3.0.0.RELEASE. So … you can do a change all “.RC3″ to “.RELEASE” and that will actually work:

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Thu Dec 17 07:33:41 PST 2009
[INFO] Final Memory: 4M/26M
[INFO] ------------------------------------------------------------------------

And since the artifacts are now coming from the main Maven repository, you can also remove this from your pom.xml:

  <id>Springframework milestone</id>

… unless, of course, you are also using the release candidates for Spring Security 3, which does not have a GA version out just yet. In that case, you just shot yourself in the foot by pulling that out prematurely. Not that I know anyone who would do that; I’m just saying …

It’s official: Spring 3.0.0 is now final

17 December 2009

No more release candidates; you can now download and start working with the real deal:

It’s here just in time for the holidays! Arjen Poutsma has just announced that Spring 3.0.0 is now final and Juergen Hoeller has blogged about the features in the release.

Download | Documentation | Javadoc API | Change Log | JIRA

Congratulations to Juergen, Arjen and all the other SpringSource engineers that worked so hard on the release. Also a huge thank you to all of the dedicated community members that have given feedback and identified issues along the way. Please keep up the good work so that we can continue to make all the Spring projects better and better.

Spring 3.0.0.RC3 is now available

4 December 2009

I missed this earlier in the week, but Spring 3.0.0.RC3 came out on Tuesday:

It’s getting closer. Arjen Poutsma has just announced that Spring 3.0.0.RC3 is now available. This release candidate contains lots of fixes to issues raised by community members.

Download | Documentation | Javadoc API | Change Log | JIRA

Thank you to all of the dedicated community members that have given feedback and identified issues. Please keep up the good work so that we can get a high quality 3.0 GA release.

So, another quick “change all” and BAM!:

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 22 seconds
[INFO] Finished at: Fri Dec 04 10:38:33 PST 2009
[INFO] Final Memory: 3M/48M
[INFO] ------------------------------------------------------------------------

Just the way I like it!

Spring 3.0.0.RC2 is now available

13 November 2009

Check it out:

Spring 3.0.0.RC2 is (tentatively) scheduled to be released today!



p.s. if you check JIRA now, you’ll notice that there are no more open issues on the RC2 road map.

I did a “change all <version>3.0.0.RC1</version> to <version>3.0.0.RC2</version>” in my pom.xml, but that was a little overzealous, since this announcement does not include Spring Security. So, I had to go back in and reset those back to RC1, after which I was rewarded with my favorite build/install outcome:

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9 seconds
[INFO] Finished at: Fri Nov 13 10:05:25 PST 2009
[INFO] Final Memory: 3M/52M
[INFO] ------------------------------------------------------------------------

Pretty cool!

Build a RESTful Web service using Jersey and Tomcat

15 October 2009

Unfortunately, I have been WWWAAAYYY too busy to even think about doing any blogging lately, but I have been having a lot of fun trying to figure out how to make this work with Spring 3.0.0RC1:

Summary: Representational state transfer (REST) was introduced in early 2000 by Roy Fielding’s doctoral dissertation. However, in the Java™ community, it was not standardized until the JSR 311(JAX-RS) specification was finalized in 2008. The first release of its reference implementation is even later. In this article, I introduce Jersey, which is the reference implementation of JSR 311, by describing its essential APIs and annotations. I’ll also show you how you can smoothly transfer from servlet-style services to RESTful services by integrating Jersey into Apache Tomcat.

Spring 3.0 is getting closer …

26 September 2009

The word is out:

Spring 3.0.0 Release Candidate 1 Now Available

Submitted by Adam Fitzgerald on Fri, 2009-09-25 14:31 in News and Announcements

This news just in from Arjen Poutsma‘s twitter feed: Spring 3.0.0.RC1 is now available.

Download | Javadoc API | Change Log

Thank you to all of the dedicated community members that have given feedback and identified issues. Please keep up the good work as we push toward GA.

Google Apps Now Supports OpenID

3 August 2009

Now this is an interesting slant on the latest news on the OpenID adoption front:

Google has announced that its implementation of the OpenID login standard, Google OpenID Federated Login API, has been extended to support Google Apps. This will allow individuals who have accounts on a service or application deployed by a business, school or other organization on Apps to use their login credentials on any site that supports OpenID. This should greatly boost the standard’s reach but there are those in the community who are apprehensive about Google’s approach.

“Google Apps can now become an identity hub for multiple SaaS providers, simplifying identity management for organizations. For example, when integrated with partner solutions such as PingConnect from Ping Identity, the Google Open ID Federated Login API enables a single Google Apps login to help provide secure access to services like Salesforce.com, SuccessFactors, and WebEX — as well as B2B partners, internal applications, and of course consumer web sites,” Yariv Adan, Google Security Team, wrote on the Google Code blog.

OpenID aims to provide a unified login experience over various services online by allowing users to have just one set of credentials that would work on any site. There are a number of similar products, some proprietary, like Facebook Connect, but also open standards, but OpenID is the open-source project that shows the most promise. The major problem for it, and other similar products, is that most people, even the tech savvy, find it hard to understand and cumbersome to use and this has generally staved off growth.

So a move like Google’s, which boasts one million domain names on Apps, should be very welcomed by OpenID. However, it’s not what the search giant is doing but how it’s doing it that has risen the greatest number of concerns. In order to provide the functionality the company had to use a non-standard library. The extension, developed by Janrain, allows relying parties, the sites that will allow Google Apps users to login with those credentials, to redirect to the Google OpenID service.

« Previous PageNext Page »