Home

News: Hibernate Shards, Hibernate Search, and Hibernate Validator releases

  1. Three new top level Hibernate projects include: Hibernate Shards, Hibernate Validator and Hibernate Search. Hibernate Shards 3.0.0 Beta1 Contributed by Google, Hibernate Shards is a horizontal partitioning solution built on top of Hibernate Core. When you need to distribute (shard) your data across multiple databases, Hibernate Shards is for you (too much data for a single database instance, regional deployment requirements, etc.) Like all Hibernate projects, Hibernate Shards is released under the LGPL license. Check the documentation for more information. Hibernate Search 3.0.0.Beta1 Hibernate Search is now a top level project independent of Hibernate Annotations. New in this release:
    • out of the box index clustering through JMS - master/slaves model -(maximizing throughput)
    • asynchronous indexing (maximizing application response time)
    • indexing of embedded/associated objects and correlated queries (semantically similar to a SQL JOIN)
    • use of Apache Lucene(tm) 2.1.0 (lots of performance and scalability improvements)
    While marked as Beta because its scope is rapidly growing and some APIs are still subject to change, Hibernate Search is already used by quite a few people, check it out. Hibernate Validator 3.0.0.GA Hibernate Validator is also a new top level project independent of Hibernate Annotations. New in this release:
    • run with pure Java Persistence Provider (entity listener provided)
    • more business oriented validators
    Check the website and the change log for more information. Hibernate Annotations and Hibernate EntityManager 3.3.0.GA A few minor configuration changes (necessary to introduce the previous projects). This version is mostly backward compatible with 3.2.x. Some of the new features are listed:
    • transparent event wiring for Hibernate Validator and Hibernate Search
    • performance improvements during cascading in Hibernate EntityManager
    • more SQL customizations as well as fetching and lazy configurations
    • the usual bunch of bug fixes

    Threaded Messages (11)

  2. Thanks, Google[ Go to top ]

    I'd like to give a great big thanks to the folks at Google - Max Ross, Tomislav Nad and Maulik Shah - for their great work on Shards. This is really exciting for the top end of sites who need to scale to huge datasets, but still need the advantages of ORM. It's also great to see Google making some really useful and serious releases in open source recently. Also congrats to Emmanuel for Hibernate Search, this is going to be really useful for a lot of people, especially people in the Seam community.
  3. You are very welcome[ Go to top ]

    Our pleasure Gavin, we're happy we were able to contribute.
  4. These all look like very interesting projects. Are there any plans to merge Validator with the base JPA specs? Looks like it would plug a major hole in them?
  5. These all look like very interesting projects.

    Are there any plans to merge Validator with the base JPA specs? Looks like it would plug a major hole in them?
    There's a separate spec forming for this such that it can be used with any framework: http://www.jcp.org/en/jsr/detail?id=303
  6. These all look like very interesting projects.

    Are there any plans to merge Validator with the base JPA specs? Looks like it would plug a major hole in them?


    There's a separate spec forming for this such that it can be used with any framework: http://www.jcp.org/en/jsr/detail?id=303
    And the coming JPA, JSF, and Web Beans specs are all committed to integrating this unified validation API OOTB. Presumably other frameworks such as Struts2 will also support it.
  7. JPA and Validation[ Go to top ]

    First of all, you can use Hibernate Validator with any JPA provider :-) (No DDL update though) Second, as Jacob said, JSR-303 will define a set of standard API and metadata for JavaBean validation in the same spirit of Hibernate Validator. This standard API will then be usable by Java Persistence and/or the Web Beans specification (the same way Hiberate Validator is used by JBoss Seam). I'll give a session at JavaOne on the subject if you're interested and here :-)
  8. Re: JPA and Validation[ Go to top ]

    JSR-303 will define a set of standard API and metadata for JavaBean validation in the same spirit of Hibernate Validator.
    ... as well as other validation frameworks out there. We all have pretty much the same feature set. We just need standardization around them to leverage the feature to the platform. That's why Jason proposed the JSR to the JCP.
  9. Re: JPA and Validation[ Go to top ]

    First of all, you can use Hibernate Validator with any JPA provider :-)
    Yes, we really should emphasize this point! It used to be that if you used Hibernate Validator with Seam and some other JPA provider than Hibernate, you would get validation in the UI, but not in the persistence layer. With the latest release, this is no longer the case. No matter what JPA backend you are using, you get the benefits of multilayer validation of the model-based constraints.
  10. Audit Logging[ Go to top ]

    The "transparent event wiring for Hibernate Validator and Hibernate Search" of EntityManager 3.3.0.GA could serve as a source for audit logging also, right? Holger
  11. Re: Audit Logging[ Go to top ]

    The event system can definitely be used to audit changes. The event listener(s) will have to be added to the configuration though (this is not the case for Hibernate Validator and Hibernate Search where the listeners are automatically added). We are thinking about simplifying the event configuration for a future revision of Hibernate, creating a notion of event profile to make the registration more modular.
  12. Hibernat Sharts?[ Go to top ]

    This could be a really cool project. But I was a little surprised by the name. It reminded me of the scene in "Along Came Polly" in which they define the term "shart" to the combination of "f*rt" and "sh*t". Yikes.