Wayback implements its own web application framework, and it is heavily dependent on JSP as view templates: It doesn't offer good support beans for other template frameworks. JSP paths are specified directly in bean properties, and scattered around the code. Renderer concept is inconsistent among different types of view.
Possible redesign idea:
Converge on single interface for view rendering. Spring's View appears to be a good candidate
Redesign UIResults to support other template frameworks. Pass model objects through View interface, instead of UIResults.extract* methods.
Add more support methods and beans, fix method signatures for easier access from templates (ex. UIResults.getCount instead of UIResults.count.)
Wayback implements its own web application framework, and it is heavily dependent on JSP as view templates: It doesn't offer good support beans for other template frameworks. JSP paths are specified directly in bean properties, and scattered around the code. Renderer concept is inconsistent among different types of view.
Possible redesign idea:
View
appears to be a good candidateUIResults
to support other template frameworks. Pass model objects through View interface, instead of UIResults.extract* methods.UIResults.getCount
instead ofUIResults.count
.)