Entries tagged [rad]

Sunday March 26, 2023

Apache Causeway version 2.0.0-RC1 Released

The Apache Causeway team is pleased to announce the release of Apache Causeway 2.0.0-RC1.

The main highlight is the change of name (to the new name 'causeway', from the old name 'isis'), which means that all Maven artifacts as well as package names have changed.  The migration notes [1] explain how to update your code; if you need assistance then reach out through the mailing list [2] or our slack channel [3] because we can explain how to tackle change in stages.

In addition, there are a small number of new features in this release, as well as numerous improvements and bug fixes.  The new features include:

* a new PageRenderSubscriber SPI provides callbacks to track the time taken to render a page (CAUSEWAY-3373)
* a new service to generate HTML documentation based on the domain model (CAUSEWAY-3328)
* the simplification of the view model lifecycle by allowing injected dependencies to be specified as constructor parameters (CAUSEWAY-3293)
* a new BackgroundService that allows actions to be executed via a Quartz job (CAUSEWAY-3267)
* allowing SAFE semantics actions to be invoked with only VIEWING permission (CAUSEWAY-3358)

Full release notes are available on the Apache Causeway website at [4].

You can access this release directly from the Maven central repo [5].
Alternatively, download the release and build it from source [6].


--The Apache Causeway team

[1] https://causeway.apache.org/relnotes/2.0.0-RC1/2023/2.0.0-RC1/mignotes.html

Saturday October 03, 2015

RAD RACE 2015: 7 proprietary CASE tools, and Apache Isis

On Sept 25th and 26th we (Jeroen van der Wal & Dan Haywood) took part in the Original RAD Race competition. This is a competition staged each year, this year (as in previous years) hosted and sponsored by Cap Gemini, and held in their offices in Utrecht, Netherlands. 

The competition consists of teams of exactly two team members; there were eight in total. The competition is held under very strict conditions: 8 hours of development on the first day, and a further 4 hours of coding the next. If you do the maths you’ll work out that means a sum total of 24 hours (2 team members x 12 hours), or 3 person-days.

We asked and were granted permission to develop our application as open source; our entry is in a github repo. If you look through the commit history you’ll see that all the work was done in those 12 hours (8 on 25 Sept 2015, a further 4 on 26 Sept). All the other teams used proprietary tools such as NoutBuilder, ThinkWise, Progress, SalesForce, Uniface and Mendix. We were the only open source entry, using Apache Isis (along with supporting modules in Isis Addons); in fact we think we are the first open source entry in the 17 years history of the competition.

OK, we didn’t win…​ but we got the impression we were mid-table, which we think is pretty good in the face of the competition. But you can judge for yourself; either download and build the code, or simply take a look at the various screenshots/our commentary on the README of the repo.

The README also has some of our "learnings" that we concluded from taking part in the competition.



Hot Blogs (today's hits)

Tag Cloud