Mittwoch, 2. Juli 2014

BARACUS Release 0.8


Today I am glad to announce that BARACUS framework version 0.8 has been released.
 It can be included using the coordinates

<dependency>
<groupid>org.baracus</groupid>
<artifactid>baracus-framework</artifactid>
<version>0.8</version>
<type>apklib</type>
</dependency>

You also can download the sourcecode from github

A couple of features have been added:


VERSION 0.8

- added the getIdField function in order to make overriding the id column naming possible
- added the getLoadAllCursor in order to make linking to a data DataBoundAdapter possible
- to be better able to work with persistence interfaces the LazyMorphicCollection has been
  introduced in order to be able to return a List<Type> from a Dao<SpecialType>

- interface registration now possible in order to extend code reuseability
  additional to applicationContainer.registerBeanClass(aClass) you now can
  call registerBeanClass(InterfaceType, BeanClass);

  This is a powerful feature since it makes in-app testing much more easy.

- also : replace bean implementations in the running application and context hot reinit

- bugfix for NullPointerException in Android preview in IntelliJ

- added support for automatic selection of modified entities (BaseDao.getAllItemsModifiedAfter)
  .. simply extend your rowmapper to implement TimestampSupportingRowmapper and return
     the timestamp fields

- added an after-context-init hook to enable application post-construct
- added a function deleteById carrying a Long parameter to the DAOs
- added an constructor based "transient" determination to ModelBase
- added some utils for basic date calculation

- added queryByExample function in order to do QBE :)
- modified DataSetChangeAware interface, now passes the emitted class in order to be able to
  create aggregator-alike DataSetChangeAware components handling multiple entity types



--- DEPRECATION NOTICE ---
- don't inherit AbstractModelBase any more! The "id" column clashes
  with the android convention of carrying an "_id" column, so I added
  a boolean parameter to force You making a review on Your model classes.
  You can either inherit LegacyModelBase (same behaviour like before) or
  - and this is recommended - rebuild Your tables by renaming the "id" column
  to an "_id" column. This restrict impacts when You try to fill view withs
  data using a cursor. So either You must consider using the LegacyBean
  or You should modify Your code.

Regards,
mnt

Keine Kommentare:

Kommentar veröffentlichen