Unsupported tagsAdded by IBM on October 1, 2012 | Version 1 (Original)
|There are tags that were a part of the originalStruts HTML tag library but not included in the Struts XDIME tag library.
The HTML tags are unsupported and not included in the Struts XDIME tag library for one of the following reasons:
- The tag is specific to HTML and does not have an equivalent in XDIME.
- The equivalent function can be achieved in XDIME, but doing so would require functionality that is outside the scope of this tag library.
The following table lists these unsupported HTML tags.
Parent topic: Struts XDIME tags
|base||In HTML, the base element is used inside a head element and identifies the base URI used to resolve relative URIs within a document. There is not a similar concept in XDIME, so this tag is not needed.|
|body||In HTML, the body element is used to identify the body content of the web page. WebSphere® Portal Server has added a body tag to the Portal Struts HTML tag library. In WebSphere Portal, the body element should not be used. The purpose of this tag, therefore, is to check whether the tag is being used in a Portal environment and, if so, not include the body element. XDIME does not have a body element, so this tag is not needed in the Struts XDIME tag library.|
|button||In HTML, the button tag generates an input element with the type parameter equal to button. The input element is supported both within and outside of forms, but the struts button tag is supported only within a form element. There is a similar function in XDIME. The <xfaction> element with the type parameter equal to "perform" is used to create a button that drives a specific action by associating an action with the onclick event. However, to call the <xfaction> element with type of perform, the <xfaction> element must not be inside an <xfform> element. Without the form support, this function cannot be supported in the Struts XDIME tag library.|
|file||In HTML, the <input> element can take a type parameter equal to file, which is a form control that enables user to upload files from their local computers. This functionality is not supported in XDIME.|
|frame||In HTML, the frame element defines a rectangular subspace that exists with a frameset element. The frame element has a src attribute that provides the URI of the frame content. This functionality is not supported in XDIME.|
|head||In HTML, the head element contains header information about the document. It includes values such as the title element, base element, meta element, and others. There is not a similar concept in XDIME, therefore this tag is not needed.|
|html||The html tag is used to insert an html element which identifies the document as an HTML document. XDIME does not support this tag. There is no equivalent tag in XDIME to identify the markup type.|
|image||The image tag renders an HTML <input> element of type image. This results in a graphical submit button. In XDIME, a similar function can be achieved using the <xfaction>.element with a Form Action Style of "image". Because the style cannot be enforced, the image to display is specified in the style rule and not in the XDIME markup, and the desired outcome can be achieved without implementing this tag. An XDIME programmer can use the submit tag with a supplied styleClass attribute that specifies the correct Form Action Style and a Form Action Image that points to the desired image.|
|options||The options tag is very similar to the optionsCollection tag and is used to generate a group of option elements. The optionsCollection tag is simpler to use and performs the same function as the options tag.|
|script||The Struts XDIME tag library does not support scripts, so this tag is not needed.|
|xhtml||The xhtml tag tells all the other html taglib tags to render themselves as XHTML 1.0 instead of HTML. This function is not needed in the Struts XDIME tag library.|