Search:

This is, in fact, the exact setup I'm using to develop my SpringOne demo application. :( I'm also using Maven in this example project.

Let me get a skeleton of this set up and put it on my GitHub....

What application server (and version) are you deploying to in STS?

If you're using Maven, have you tried including the Jetty 8 plugin and trying "mvn jetty:run" from the project directory to see...

There are basically two ways to set up the application so that your Repositories are properly discovered in the right ApplicationContext.

1) As separate config classes.

In the initializer in...

I just did a "./gradlew jettyRun" from the example directory and am getting exposed repositories:



< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 275
< Server:...

The long-term goal still remains to adapt Spring Data REST to high-throughput containers (Netty, Grizzly, et al) for deployment to non-servlet environments. The code does not actually rely on servlet...

Looks like the query works but in the code I'm assuming you'll be returning an entity or a list of entities from searches. It's giving a 404 trying to find a repository for a Long.

I'll get a fix...

I think you just need to define your @Query like you would in normal JPQL queries:


@Query("select count(p) from Person p where p.name = :name")
public Long findByName(@Param("name") Long name);

I think "proper" REST behavior here is a little fuzzy. In the case of the Repository.findOne(id) method, we already return a 404 if no result is found. Search results are a little more difficult,...

I'm pleased to announce that Spring Data REST 1.0.0.RC2 is now available in the SpringSource milestone repositories. This release adds JSONP support, includes important bug fixes, and introduces some...

Spring Data REST 1.0.0.RC2 was released yesterday and includes a number of important bug fixes and changes the way entities are listed. In the latest stuff, entities are paged by default at 20 and...

Oops. I see you've created an issue on Github. That should work fine. Disregard what I said earlier about JIRA. :)

There is already an attribute on the @RestResource annotation to disable a method. In the latest RC, that only affects query methods. If you want to create an issue in JIRA [1] for it, I can extend...

Wow. Thanks for the compliment! :)



The Spring Data REST controller emits ApplicationEvents before and after calling the repository methods. If you want to intercept an object about to be...

Are you aware of the Spring Data REST project, which exposes your JPA Repositories over HTTP for doing CRUD and querying?

http://www.springsource.org/spring-data/rest

Might be easier to...

To be honest, I don't see it happening with the current code. If you're okay with using a snapshot, we could probably get that fix in right away. If not, it looks like you'll have to keep track of...

Looks like we need a JIRA issue. The following code in RedisMessageListenerContainer should be modified as follows.


processMessage(messageListener, message, null);

Should actually be:

...

Looks like like line 724 in RedisMessageListenerContainer is the culprit. It's hard-coded to pass null as the pattern for some reason.

To be honest, I've not tested it with "default-lazy-init='true'". Ideally, it shouldn't make a difference, but I've just not tested it that way, so I can't say that that won't have an effect on the...

Not sure exactly what's going on but the "repositories-export.xml" is unnecessary in your configuration. The Repositories are being loaded into the root ApplicationContext already by...

Looks like this is a bug in the way the Update class creates a DBObject to submit to the database. In the meantime, were you to load the Session object individually and update it directly (rather...

Yikes! :(

I pushed a fix for this and created a test case specifically for non-list, referenced properties.

If you use a snapshot build (after the nightly runs and creates one, that is :)), you...

The M2 mapping support will allow you to put an @Id annotation on any field (or it will look for an ObjectId or String named either "id" or "_id") but that won't put a property into the document...

There are three methods to support links and link walking in the Riak template. I simply forgot to cover them in the reference documentation. But they're pretty easy to understand from the Javadoc:
...

I would call them "constructive criticism" rather than complaints. :)



In a library where others are using your code, I'd say throwing an exception is important. In our own stuff, I can do...

To be honest, I don't see a tradeoff at all. When I need objects that act like immutable ones but need to be config'd via Spring, I simply put:



public void setStuff(String s) {
if(null ==...