I'm pleased to announce the release of Spring Data REST 1.0.0.RC1! Beyond a number of bug fixes, this release adds support for paging and sorting and makes it easier to integrate Spring Data REST into an existing Spring MVC application.

New functionality includes:

• Paging - Add URL parameters like "page=2" and "limit=20" to control the paging of large result sets.
• Sorting - Add URL parameters like "sort=name" to control the sorting of result sets.
• Integrate with existing Spring MVC applications - Now you can easily integrate Spring Data REST into an existing Spring MVC application by simply including a JavaConfig bean into your own configuration.

New documentation includes:

• Paging and Sorting
• Adding Spring Data REST to an existing Spring MVC Application

Starter Web Application | Wiki | Release Notes

To learn more about the project, visit the Spring Data REST homepage, or visit the Github repository to download the source.

Hot on the heels of the 1.1.0 GA release of Spring Data JPA, I'm pleased to announce the milestone 2 release of Spring Data REST. Besides many bug fixes, this M2 release includes a major update of functionality for the Spring Data REST exporter.

New functionality includes:

• Query method support - Spring Data REST 1.0.0.M2 includes support for invoking query methods of Repository interfaces. Results are returned as links to top-level resources.
• Comprehensive validation support - In addition to JSR-303 validation, the Spring Data REST exporter recognizes Spring Validator beans declared in your ApplicationContext to provide rich validation support. Your Validator beans can do anything--even look up other data to verify the integrity of an object graph.
• ApplicationEvent handling - The exporter's validation support is built on top of the Spring ApplicationEvent mechanism. ApplicationEvents are emitted before and after each save or delete, allowing your code to tie into these lifecycle events and trigger other actions.
• Annotation-based URL configuration - There is a new annotation: @RestResource you can place on a Repository interface or on a Repository's query methods to influence both the URL under which the resource is exported and the "rel" attribute associated with the links generated to point to that resource.

Starter Web Application | Wiki | Release Notes

To learn more about the project, visit the Spring Data REST homepage, or visit the Github repository to download the source.

The Spring Data team is pleased to announce the (initial) 1.0.0.M1 release of Spring Data REST.

This release contains a Servlet-based web application that can be used to export JPA Repositories over HTTP to create RESTful endpoints that user agents can access to manage your exposed JPA Entities. Browsers (via Javascript) or non-interactive agents like curl or wget can perform CRUD operations on entities, including managing relationships between entities through the use of Links.

Starter Web Application | Wiki | Release Notes

To learn more about the project, visit the Spring Data REST homepage, or visit the Github repository…

Asynchronous applications can sometimes be a challenge while you're developing them since you usually need two separate components to see the full message publication and consumption lifecycle. It often happens that you write a consumer that can dump messages to System.out or your log file, just so you can make sure your publisher is doing the right thing. It would be really handy if you could mock the message publication and consumption interaction in a single component so you could actually see what's going on.

The RabbitMQ Groovy DSL aims to help with this by providing a very concise and…

Traditionally, applications have been defined by the principle technology they use. If you're building a Spring MVC application, we call it a "Java app". Since our application is primarily composed of Java components, we tend to stay in our own yards and not be terribly friendly with our neighbors until we're forced to interact with them. We set up Java-based application servers and tend to think first of going to the Java language to solve a problem in our application whether that language is the best choice or not. It has usually just been too difficult to maintain multiple sets of runtime…

As new applications take advantage of the scalability benefits of message brokers like RabbitMQ and cloud-scale datastores like Riak, it's inevitable that the two should become fast friends (the kind who actually talk to each other in person rather than the kind whose only contact is through Facebook).

So many of the applications we find ourselves writing these days have these two functions in the same application. Very often we want to update data as the result of a message or send a message as the result of updated data. Two new utilities facilitating RabbitMQ and Riak integration allow you…