[AGILA-44] Option to use JSP Includes for rendering forms for Task nodes.

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: BPM Console
• Assignee: Christopher Giles A. Lim
• Reporter: Geoff Howard
• Created: 27/Mar/06 22:20
• Updated: 03/Apr/06 02:43

Description

The existing HTTPRenderer used in the sample webapp only supports returning the html of the form as a String. This leads to an ugly StringBuffer exercise in the sample LeaveApplication process as noted in the code.

The first patch provides an alternate renderer and adjusts the existing rendering mechanism to account for the new option.

The second patch takes a different approach and can replace the first. It uses RequestDispatcher.include in the task's render method to accomplish the same goal, and also allows fall back behavior for tasks that wish to generate the form html as a string using some other method. It uses less overall code, but does rely on servlet spec 2.4 (agila bpm seems to already depend on 2.4 anyway).