DefaultViewer
with a page generated by a custom JSP file.
step2
directory.GroupWorkListViewer.start
to
GroupWorkListViewer.java
.GroupWorkListViewer.java
and change the base class
from DefaultViewer
to JSPViewer
. Although this
is not necessary for the custom JSP to be displayed, it provides
JSP-based implementations for all of the methods, which are not overridden
by the GroupWorkListViewer
class.queryWorkItemsResponse
method with a call to your own class' method (which is described in the
next step).queryWorkItemsResponse
method. The first statement in
this method is used to store the workListOID
in the
RequestContext
object that is being passed to the JSP. This OID
is the one, which is set in logonResponse
. Here, an instance
variable is used instead of a local variable./forms/GroupWorkList.jsp
.GroupWorkList.start
to
GroupWorkList.jsp
.GroupWorkList.jsp
file and add the import
statement for the Web Client's package.jsp:useBean
statement to access the
RequestContext
object that is necessary to create the response
page. This is the same object, which was passed as a parameter to
the ResponsePage
in the queryWorkItemsResponse
method. Use the following attributes for the useBean
statement:
id="context" scope="request" type="com.ibm.workflow.servlet.client.RequestContext"
workListOID
that has been set in the
queryWorkItemsResponse
method. Use the
RequestContext.getAttribute() call for this.cmdRefresh
for the
queryWorkItems command used by the 'Refresh' button. Set the
useCache
parameter to false
. The SessionContext
class provides
methods to create these command strings.GroupWorkList.jsp
to the
<MQWFDir>/WebClient/webpages/forms
directory.jc step2\GroupWorkListViewer.javato compile your file.
GroupWorkListViewer.sol
and
GroupWorkList.sol
).