When you use an invalid name, such as a misspelling of a component type, Tapestry is great about listing out the possible names you could have used. However, when there's a lot of those (such as a service id, or a component type, or page name in a large application), the format is hard to parse: long, long, long comma-separated list.
A better approach would be to use two or three columns of <ul> and <li> elements to present the options in a useful order.
|Field||Original Value||New Value|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||Closed [ 6 ]|
|Fix Version/s||5.2.0 [ 12314122 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|3m 33s||1||Howard M. Lewis Ship||27/Feb/10 02:10|
|76d 15h 30m||1||Howard M. Lewis Ship||14/May/10 18:40|