Announcement Announcement Module
No announcement yet.
Spring Data MongoDB 1.0.0.M5 Released Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Spring Data MongoDB 1.0.0.M5 Released

    Dear Spring Community,

    I am pleased to announce that the Spring Data MongoDB 1.0 Milestone 5 release is now available!

    The primary goal of the <b>Spring Data</B> project is to make it easier to build Spring-powered applications that use new data access technologies such as non-relational databases, map-reduce frameworks, and cloud based data services.

    The MongoDB module provides integration with the MongoDB document database.

    Downloads | JavaDocs | Reference Documentation | Changelog

    To learn more about the project, visit the Spring Data MongoDB Page.

    There are a number of bug fixes and minor changes to the way certain features work. See the changelog for more details.

    Looking forward to your feedback on the forum or in the issue tracker.

  • #2
    Following exception occured while pointing to 1.0.0.M5 version.

    The POM for is missing, no dependency information available



    • #3
      Ooops, forgot to update the spring-data-commons dependecy to 1.2.0.M2 - it should be fixed by now. Please let us know if this is still a problem.

      Thanks for the alert.


      • #4
        I have exception in maven dependency. Version 1.0.0.M5 is unknown, jaust as 1.0.0.M4 etc.



        • #5
          help?spring mongodb why not filter charater &quot;$&quot; and &quot;^&quot; and &quot;?&quot;

          code example:
          if(criteria == "$"){
          criteria = "\\u0024";
          if(criteria == "^"){
          criteria = "\\u005E";
          query.addCriteria(Criteria.where("tagName").regex( criteria, QueryOperators.IN));


          • #6

            spring-data-mongodb does not actually create the index until the first time you pro grammatically access the collection that will contain the index. I believe that if you poke around their documentation, there is a way to get it to index auto-magically. As for my post, it is a bit out-dated now. Since they have released the official 1.0.0 release of spring-data-mongodb, you can set the write concern directly in your application Context using the
            mongo:mongo element:

            <mongo:mongo write-concern="SAFE"/>

            <mongo:db-factory id="databaseFactory" .... mongo-ref="mongo" />

            MySQL Interview Questions And Answers


            • #7
              Good job, but ...

              I have been evaluating various frameworks for MongoDB, so far mongo-jackson-mapper and Kundera has fallen short. Sadly it seems so does Spring:
              Ideally persistence framework for mongo should support maintaining relationships.
              Not supported it seems.
              Map POJOs without limiting developer.
              If a field named ' id' id field is not declared as a String, BigInteger, or ObjectID in the Java class then you should assign it a value in your application so it can be stored 'as-is' in the document's _id field.
              What does this even mean? This seems like an unbearable constraint. Why can't an @Id annotated field be a bean? I happen to like composite Id's since they provide clarity about lifecycle of objects.
              Could spring evolve to support something like this?:
              public class Subscriber {
                UUID uuid;
                String name;
                List<Subscription> subscriptions = new ArrayList<Subscription>();
                Address address; // Embedded
              @Index(properties = {"product", "subscriber"})
              //@Index(properties = {"subscriber","product"}) // Implied
              public class Subscription {
                Key key;
                public static class Key {
                  @ManyToOne(mappedBy = "subscriptions")
                  Subscriber subscriber;
                  @ManyToOne(mappedBy = "subscriptions")
                  Product product;
              I am reluctant to write my own persistence framework for mongo, but the more frameworks I evaluate the more likely it seems that none meet my requirements. Are my requirements unreasonable?