small nit, but are you really setting up a form or are you rendering a profile?
The previous profile auto made a form, the function name lingered through, I've now modified to setUpPersonProfile
Why not use addAttributesToModel helper?
The helper additionally contains the referring_page_id. I felt for querying people, the entry point would either be manually modifying the URL, a link, or a search. In some of these cases you would not have a referring page id to pass, and not including a referring page id appears to 404 the page in the current set up. Perhaps we need to look into a new way to handle saving the tab a person was using while entering menus (The current phonebook does it well)
I think we should either re-examine the current approach for tracking a users visited page or make it so this method follows the current convention. If you want to make it an optional parameter use @RequestParameter(optional=true)
Why do we have to similar tests that output the same result?
The idea was to include the profile page view of any users along side the exists self view page, at least for the time being. This led me to create a second set of constants in the message.properties, requiring the second (nearly identical) test. We could choose use the same constants for both pages. But the initial plan was do do it entirely along side until the point where we can phase out the current self-only profile page in favor of one that can view any user