Screencasts

We’ve prepared a number of screencasts to help you see what Apache Causeway has to offer.

While these each follow on from each other, you should be able to watch them in any order; the typical duration is 3 minutes. The number of each screencast (eg '001') is a link over to youtube.

Or, if you have a little more time, you can watch the screencasts by playlist. You can either watch ALL of them one after the other, or you can use one of the themed playlists to explore particular aspects of the framework. The table below indicates which screencasts are in which playlist.

These screencasts were recorded using v1.12.x. There have been a number of UI improvements since these releases.

Finally, you can also find some screencasts for earlier versions of the framework here.

Playlists

IDE, layouts

002
Importing the generated app into an IDE

X

X

003
Walking through the main classes that make up the SimpleApp: SimpleObject persistent entity, HomePageViewModel`view model and `SimpleObjects domain service (repository).

X

004
Using the optional Xxx.layout.xml file to provide layout metadata to dynamically render a domain object using the Bootstrap 3 grid system.

X

Fixture scripts, rules, tests

005
Using fixture scripts to initialize the database, eg while prototyping and for demos

X

006
Implementing business rulesfor domain object members, using supporting methods ("see it, use it, do it")

X

007
Writing unit tests for a domain object responsibility

X

008
Writing end-to-end integration tests for a domain object responsibility

X

Swagger UI

009
Using the Swagger UI to access the REST API automatically exposed for domain services, entities, and/or view models

X

Actions

012
Implementing business logic using a (no-arg) action, and associating with a property using either the @MemberOrder annotations or using dynamic (XML) layouts.

X

X

Titles and icons, UI event subscribers

Using the title(), cssClass() so that end-users can distinguish domain objects within the UI.

X

X

X

015
Moving the responsibility to specify the icon for a domain object out and into a subscriber, using the IconUiEvent as per the @DomainObjectLayout#iconUiEvent() annotation

X

Derived collections

016
How to implement a derived collection on a domain object.

X

More on fixture scripts

017
Extending a fixture script to more easily demonstrate new functionality.

X

Page size of collections

018
Using dynamic (XML) layouts to specify the page size for a domain object’s collection.

X

Hints and end-user features

019
Demonstrates how Apache Causeway' Web UI (Wicket viewer) remembers the state of rendered domain objects, and how the end-user of the application can clear these UI hints using the (framework-provided) "clear hints" mixin action.

X

020
Demonstrates how the end-user can copy and share URLs for domain objects - including UI hints - using Apache Causeway' Web UI (Wicket viewer).

X

021
Demonstrates how the end-user can use bookmarks and breadcrumbs within Apache Causeway' Web UI (Wicket viewer), and how the developer can ensure that domain objects and (query-only) actions can be bookmarked.

X

Decoupling (mixins & subscribers)

022
Shows how to refactor a domain object to move an action implementation out of the domain object itself, and instead implement as a mixin (useful for decoupling).

X

X

023
Shows how to refactor a domain object to move (derived) collections out of the domain object and reimplement as a mixin.

X

024
Using a domain event subscriber to decouple and abstract business rules for validation.

X

025
Using a domain event subscriber to hide functionality, in this case the "clear hints" action automatically provided by the framework.

X

Titles using the @Title annotation

026
Using the @Title annotation (instead of the title() reserved method) to obtain the title of a domain object, so that the end-user can distinguish one object from another.

X

X

Integration testing of mixins

027
How to write an integration test for a mixin.

X

Removing boilerplate

028
Using Project Lombok to remove boilerplate from your domain objects (getters and setters).

X

Action validation

030
How to validate action parameters using a supporting validate…() method.

X

X

031
How to validate action parameters using the @Parameter#mustSatisfy() and the Specification interface.

X

Instantiating/Initializing Objects

032
How to instantiate/initialize objects using RepositoryService, ServiceRegistry and/or FactoryService.

X

X

Property and parameter choices

033
How to provide a set of choices (a drop-down list) when editing a property.

X

X

034
How to provide a set of choices (a drop-down list) when invoking an action.

X

035
How to use the choices supporting methods as a source for default values within a fixture script.

X

X

036
How to use an enum for choices (drop down list) for both a property or an action parameter.

X

Hiding columns

037
How to hide properties as columns in tables (parented collections or standalone collections), using the dynamic XML layout (equivalent to @PropertyLayout#hidden()).

X

038
How to hide properties as columns in tables, using CSS.

X

Fixture scripts defaults / fake data

039
Using the FixtureScript defaultParam(…) method to reflectively default parameters to fixture scripts that have not been set by the caller.

X

040
Using the (non-ASF) Incode Platform's fakedata module’s FakeDataService to provide fake (random) names within a fixture script.

X

X

BigDecimals

041
Using BigDecimal as a property within a domain object, also demonstrating the "summary" view within the Web UI (Wicket viewer).

X

X

X

042
How to use the @Digits annotation for action parameters of type java.math.BigDecimal.

X

Action parameters

043
How to use the supporting defaultXxx(…) supporting method to provide a default argument value for action parameters.

X

X

044
How to use @DomainObject#bounding() so that a drop-down list is automatically provided for any parameters to actions that are for (domain entity) reference types.

X

045
How to use the choicesXxx(…) supporting method to provide a drop-down list for parameters to actions that are for reference types (domain entities or view models).

X

046
How to use the autoCompleteXxx(…) supporting method to provide a drop-down list for parameters to actions that are for reference types (domain entities or view models).

X

Excel, Calendars

047
Configuring an Apache Causeway app to allow tables of objects to be downloaded as an Excel spreadsheet, using the (non-ASF) Incode Platform's excel wicket component.

X

048
Configuring an Apache Causeway app to allow tables of domain objects with date information to be rendered on a full-page calendar, using the (non-ASF) Incode Platform's fullcalendar2 wicket component.

X

049
Using the @Programmatic annotation to exclude methods from a domain object (eg implementing methods of an interface as defined by the (non-ASF) Incode Platform's fullcalendar2 wicket component) that would otherwise be part of the Apache Causeway metamodel (and thus show up in the UI).

X

View Models

052
How to write a (JAXB) view model, holding references to two domain objects.

X

X

053
Updating the title, icon and layout of a (JAXB) view model.

X

054
How to expose information from underlying domain entities referenced by a (JAXB) view model using derived properties

X

055
Adding an action to a (JAXB) view model, and adjusting the layout using custom CSS.

X

Renaming

056
The (very simple) steps required to rename a domain entity class.

X

057
How to rename a menu (on the top-level menubar) as rendered in the Web UI (Wicket viewer).

X

058
How to rename various elements (collections, title) of the home page view model, for an improved initial page.

X

059
How to rename the application name as it appears in the header.

X

060
Updating the logo for the application as it appears in the header.

X

Decoupling

061
Refactoring a mixin action, teasing out its separate responsibilities in order to decouple the code and uncover new concepts.

X

062
Separating out the responsibilities of the persistent domain entities from those of view models that act upon those domain entities.

X

(Parented) collections

063
How to implement a bidirectional 1-to-many association between two domain entities.

X

064
How domain entities can be automatically persisted just by being associated with an already persistent entity.

X

065
How bidirectional relationships between domain entities can be automatically maintained.

X

066
How deleting one persistent entity can, if required, automatically delete another associated entity.

X

Metadata fieldset

067
Improving the layout of domain entities by adding a metadata fieldset.

X