iSeries WebFacing
v5.0

com.ibm.etools.iseries.webfacing.tags.impl
Class WFProgDef

java.lang.Object
  |
  +--javax.servlet.jsp.tagext.TagSupport
        |
        +--javax.servlet.jsp.tagext.BodyTagSupport
              |
              +--com.ibm.etools.iseries.webfacing.tags.impl.WFBodyTagSupport
                    |
                    +--com.ibm.etools.iseries.webfacing.tags.impl.WFFieldTagSupport
                          |
                          +--com.ibm.etools.iseries.webfacing.tags.impl.WFProgDef
All Implemented Interfaces:
javax.servlet.jsp.tagext.BodyTag, javax.servlet.jsp.tagext.IterationTag, Serializable, javax.servlet.jsp.tagext.Tag

public class WFProgDef
extends WFFieldTagSupport

See Also:
Serialized Form

Field Summary
static String Copyright
           
 
Fields inherited from class com.ibm.etools.iseries.webfacing.tags.impl.WFBodyTagSupport
context, MT, name, parent, record
 
Fields inherited from class javax.servlet.jsp.tagext.BodyTagSupport
bodyContent
 
Fields inherited from class javax.servlet.jsp.tagext.TagSupport
id, pageContext
 
Fields inherited from interface javax.servlet.jsp.tagext.BodyTag
EVAL_BODY_BUFFERED, EVAL_BODY_TAG
 
Fields inherited from interface javax.servlet.jsp.tagext.IterationTag
EVAL_BODY_AGAIN
 
Fields inherited from interface javax.servlet.jsp.tagext.Tag
EVAL_BODY_INCLUDE, EVAL_PAGE, SKIP_BODY, SKIP_PAGE
 
Constructor Summary
WFProgDef()
           
 
Method Summary
 int doAfterBody()
          Only process the body once so this always returns SKIP_BODY
 int doEndTag()
          For Program Defined content simply have the JSP processor handle any included content
 int doStartTag()
          With Program defined fields there is no content in the JSP, the content will be extracted from the incoming record data buffer.
 
Methods inherited from class com.ibm.etools.iseries.webfacing.tags.impl.WFFieldTagSupport
getclass, getCtrlrcd, getField, getFieldId, getFieldValue, getHtmlafter, getHtmlbefore, getOnblur, getOnclick, getRecord, getSflrow, getStyle, isProtected, isVisible, release, setClass, setCtrlrcd, setField, setHtmlafter, setHtmlbefore, setOnblur, setOnclick, setRecord, setSflrow, setStyle
 
Methods inherited from class com.ibm.etools.iseries.webfacing.tags.impl.WFBodyTagSupport
getLogger, logMsg, setPageContext, setParent
 
Methods inherited from class javax.servlet.jsp.tagext.BodyTagSupport
doInitBody, getBodyContent, getPreviousOut, setBodyContent
 
Methods inherited from class javax.servlet.jsp.tagext.TagSupport
findAncestorWithClass, getId, getParent, getValue, getValues, removeValue, setId, setValue
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 
Methods inherited from interface javax.servlet.jsp.tagext.Tag
getParent
 

Field Detail

Copyright

public static final String Copyright
Constructor Detail

WFProgDef

public WFProgDef()
Method Detail

doStartTag

public int doStartTag()
With Program defined fields there is no content in the JSP, the content will be extracted from the incoming record data buffer. However because the base class is a BodyTag we need to process the body so that the after body and end tag methods will be called. Also make sure that the body contains something (default is one space which will be thrown away).
Overrides:
doStartTag in class javax.servlet.jsp.tagext.BodyTagSupport

doAfterBody

public int doAfterBody()
Only process the body once so this always returns SKIP_BODY
Overrides:
doAfterBody in class javax.servlet.jsp.tagext.BodyTagSupport

doEndTag

public int doEndTag()
For Program Defined content simply have the JSP processor handle any included content
Overrides:
doEndTag in class javax.servlet.jsp.tagext.BodyTagSupport

iSeries WebFacing
v5.0

Copyright © 2003 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.