> Ebean version 2.0.0 has been released.
> - Added DDL Generation
> - Refactored programmatic configuration via ServerConfig
> - Add enhancement support for PropertyChangeSupport
> - Add query.findRowCount();
> - Refactor for SqlQuery, SqlUpdate and CallableSql... these are now
> interfaces and must all be created using Ebean such as
> Ebean.createSqlQuery(...)
> - Refactoring of Expressions (Expr has been repackaged)
> - Removed some Deprecated methods
> - Added BeanState ... to access internal bean state such as isDirty,
> loadedProperties etc
> *NOTE:* The enhancement has changed so if you are using the eclipse enhancer
> plugin
> please remember to update that once you start using v2.
> Special thanks to Eddie and Mario for their contributions and guidance.
> There has been
> a lot of work gone into this version - thanks and well done.
> This release has what I think are some pretty good improvements. In addition
> there
> has been quite a lot of refactoring of the internals and the ebean-2.0.0.jar
> is actually
> smaller than ebean-1.2.0.jar.
> In terms of building Ebean we are looking to move to maven and there will
> likely be
> some re-organisation in svn to support that.
> *API CHANGES:*
> There have been some API changes which means you code will be broken and
> will have to change. These where good long term changes (to make the API
> more abstract and future proof) so it was decided now was a good time to get
> those changes in (and means a more stable API going forward). Apologies for
> the code breakages...
> SqlQuery, SqlUpdate, CallableSql are now all interfaces and must be created
> via Ebean or EbeanServer.
> So new SqlQuery(...) ... should be converted over to
> Ebean.createSqlQuery(...) etc.
> Similarly with SqlUpdate and CallableSql.
> There are now methods to create named SqlQuery, SqlUpdate and CallableSql
> such as
> Ebean.createNamedSqlQuery(...).
> A number of objects have been re-packaged including Expr.
> BeanPersistController has lost its generics. This was so that a controller
> could listen
> to multiple entity types (e.g. for all entities that implement a "audit"
> interface do some
> pre-insert pre-update processing)
> You can also now register multiple BeanPersistControllers and
> BeanPersistListeners for a single
> bean type.
> Enjoy,
> Cheers, Rob.
