Wicket Objects pages are built from multiple Wicket Components. For example, the application service menu bar has its own Component:

Likewise, there's a Component to render an entire entity:

And there's a Component to display the properties of an entity:

And in turn there's a Component for every entity property:

There are Components such as these for every class member, including collections, actions and, indeed, action parameters. In fact, you can think of Wicket Objects as basically a collection of pre-canned Components that know how to render the Naked Objects metamodel.

Note, by the way, the CSS classes. Each HTML element can be targetted either by its type (a string scalar), or by its class member (the Claim's description property), or both. Wicket Objects makes it easy to contribute custom CSS that applies to every page.