For services that may be created again on each request, Tapestry does a lot of extra work to analyze the class, constructor and fields. It should be able to roll up all this information into a repeatable "plan" that can simply be re-executed on each subsequent instance creation.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|8h 5m||1||Howard M. Lewis Ship||24/Sep/11 04:54|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Fix Version/s||5.3 [ 12316024 ]|
|Resolution||Fixed [ 1 ]|
|Field||Original Value||New Value|
|Assignee||Howard M. Lewis Ship [ hlship ]|