@@ -211,7 +211,8 @@ <h3>Properties</h3>
211211occurrences must not be reset. If an attribute value is set as a
212212request-time attribute value (using a scripting or an EL expression),
213213the container must reset the attribute between all reuses of the tag
214- handler instance.
214+ handler instance. To prevent confusion, a tag handler with an empty body
215+ must not reuse any previous tag handler with a non-empty body.
215216
216217< p > User code can access property information and access and modify
217218tag handler internal state starting with the first action method (doStartTag)
@@ -908,10 +909,10 @@ <h3>Invocation of a JSP Fragment</h3>
908909 scoped attribute exists with the provided name in the tag file, the
909910 JSP container must generate code to create/update the page scoped
910911 attribute of the provided name in the calling page/tag. If a page
911- scoped attribute with the provided name does not exist in the calling
912- page , and a page scoped attribute of the provided name is present in
913- the tag file , the scoped attribute is removed from the tag
914- file 's page scope. See the chapter on Tag Files for details.</ li >
912+ scoped attribute with the provided name does not exist in the tag
913+ file , and a page scoped attribute of the provided name is present in
914+ the calling page , the scoped attribute is removed from the calling
915+ page 's page scope. See the chapter on Tag Files for details.</ li >
915916
916917 < li > If <jsp:invoke> or <jsp:doBody> is being used to
917918 invoke a fragment, if the < code > var</ code > attribute is specified,
0 commit comments