Over on Apache Isis, we’ve just released a new version, 1.3.0, of the framework (core plus supporting components).
There are some major new features in this release; indeed this is probably the most significant release of Isis as a TLP. Just to highlight some of the main features…
In core, the new features include:
- contributed collections and properties
- view model support (across both Wicket and RO viewers)
- UI layouts defined in JSON files
- better integration and BDD testing support, including Cucumber-JVM integration
- domain services for handling application and user settings service
- domain service providing various developer utilities (eg downloading metamodel)
- domain service incorporating Guava’s EventBus service);
- context-specific autoComplete
- conditional choices
- new annotations: @SortedBy; @CssClass; @PostsPropertyChangedEvent
- helpers for writing contract unit tests and for writing comparable entities
- optimistic locking improvements
In the Wicket viewer, new features include:
- default dashboard
- more sophisticated layouts, with multiple columns
- dynamic reloading of layouts
- sortable table columns
- BlobPanel displaying images
- bookmarkable actions
- upgrade to wicket 6.11.0
In JDO objectstore, new features include:
- better integration/validation between Isis and JDO metamodels
- upgrade to DataNucleus 3.2.7
- better Google App Engine compatibility
- expose JDO PersistenceManager via domain service for more sophisticated use cases
The Restful Objects viewer also had several bug fixes vis-a-vis the RO spec v1.0 (thanks to our GSOC students for highlighting these).
In addition to all that, there is a new “simple” archetype, making it easier to get started.
As ever, feedback welcome
I’m delighted to announce that Oscar Bou has been voted in as a committer on Apache Isis, and also to as a member of the Isis PMC. The first gives Oscar the right to commit changes directly to Isis’ codebase, the second gives him the right to be involved in future votes.
If you’ve been following the Isis users and dev lists over the last few months, you can’t fail to have seen Oscar’s energetic involvement. Oscar came across Isis while building a similar framework in-house, and has since worked with his team to port much of their application – still in development – over to Isis. In so doing, Oscar has provided invaluable early testing and feedback for new features being implemented.
Oscar has ticked the boxes in terms of being a committer: using the mailing lists appropriately, raising JIRA tickets, provided patches to address specific issues, providing help to others in the community. But he’s gone beyond that in raising a number of insightful – sometimes challenging – questions regarding Isis’ design/responsibilities as a framework, and shown that he’s keen to address these issues and thus improve Isis as a product.
I’m looking forward to working with Oscar in the future; another great addition to Isis’ committers.
As a bit of tidying up, we have also voted for Jeroen van der Wal, and Maurizio Taverna, to be members of the Isis PMC. In fact, in many/most Apache projects, all committers are also PMC members, so it was something of an anomaly that we originally voted Jeroen and Maurizio as just committers.
A few days ago we (that is to say, the Apache Isis team) pushed out a new point release of Apache Isis Core (v1.1.0), along with two of its components Isis Shiro Security (v1.1.0) and the Isis Wicket Viewer (v1.1.0). The Quickstart Archetype that combines Wicket, Shiro, Restful and JDO also got an update (v1.0.2).
New and notable features in this release are: Read the rest of this entry
Following on from recent graduation as an Apache top level project and the work we’ve done since (new website, moving to git, semantic versioning), I’m proud to announce that Isis 1.0.0 has been released.
Somewhat delayed news, but just to say that a couple of months ago (Oct 17 2012, to be precise), the Apache board approved the resolution to establish Isis as a top-level project.
This is a big deal. The Apache Software Foundation is all about establishing viable open source communities with software developed “out in the open”, and with squeaky clean intellectual property. The reason Apache has an incubator is to ensure that these principles are followed.
So, after a couple of years in the incubator Read the rest of this entry