Correcting the Task Input Data Display

In order to customize the display of the task input data field, you need to perform the following steps:

1. Create the JSP file that will display the input data field and place it in the /web/WEB-INF/handlers/input/ directory.

2. Edit the /web/WEB-INF/includes/input-handler.jsp file. The if-else statement needs to be updated to make sure the newly created JSP file is included if the current task (represented by the iha_task variable) has the desired type (the iha_task.getTaskDefId() method).

In the actual JSP file that will render the task input data field, the following context is available via request attributes. Following are the attribute names, their types, and their meaning:

• com.sun.glassfishesb.wlm.console.locale also defined as LOCALE_ATTRIBUTE in Constants.java.

  A java.util.Locale class representing the current locale of the user's browser.

• com.sun.glassfishesb.wlm.console.task-id also defined as TASK_ID_ATTRIBUTE in Constants.java.

  A java.lang.Long representing the numerical ID of the current task.

• com.sun.glassfishesb.wlm.console.user-id also defined as USER_ID_ATTRIBUTE in Constants.java.

  A java.lang.String representing the username of the current user.

• com.sun.glassfishesb.wlm.console.task also defined as TASK_ATTRIBUTE in Constants.java.

  A TaskType class (automatically generated from the WLM SE's WSDL file) representing the current task.

• com.sun.glassfishesb.wlm.console.task-input-data also defined as TASK_INPUT_DATA_ATTRIBUTE in Constants.java.

  An org.w3c.dom.Element and the XML representation of the task's input data.

The handler JSP file is expected to output the HTML code suitable for display in the web browser.

You can also consult these files to get a better understanding of the processing logic that needs to be defined:

• /web/WEB-INF/handlers/input/default.jsp

• /web/WEB-INF/handlers/input/purchase-order-sample.jsp