re-motion supports passing the IDs of domain objects in URLs, so that you can send around pages like these as links and have the recipient see exactly what you see:
FIXME ILLU
Sending around pages associated with a particular object can be very practical, and many content management systems support this. For example, if I share my PhoneBook application with other people, I can send my fried Josh Szygyäivsük (Polish mother, Finnish father) a link to his EditPersonForm and ask him to correct the spelling of his last-name if I got it wrong and to supplement his address, something like:
...
Let's talk about the resulting URL first. If you run this code and click on New location..., you will note that the URL for invoking the EditLocationForm has become much longer:
FIXME ILLU
Now being invoked with a perma-url
FIXME ILLU
... and here it is
...
Your project should compile and link (but again: you have to build it twice to get rid of the errors). If you stimulate your PhoneBook web app into displaying the EditLocationForm, you will see the foo-parameter in the URL. You can either click on New Location... (EditPersonForm) or Edit (SearchResultLocationForm) (see screenshots).
FIXME ILLU
FIXME ILLU
Either way, your URL will display the utterly redundant (but instructive) foo=42.
FIXME ILLU
Domain objects in the perma-URL
...