The JSP 1.2 spec also says that the <mytag></mytag> is valid.  But, I'd
still like to know when Tomcat added support for this variant of the empty
tag.  I'm assume that all versions of Tomcat 4 support this syntax for empty
tags -- is this correct?

Thanks,
Steve

> -----Original Message-----
> From: Steve Bang [mailto:SBang@;alphablox.com]
> Sent: Thursday, October 17, 2002 2:50 PM
> To: [EMAIL PROTECTED]
> Subject: Empty custom action tags
> 
> 
> According to the JSP 1.1 spec:
> 
>   Action elements follow the syntax of XML elements, i.e. have a 
>   start tag, a body and an end tag:
> 
>     <mytag attr1="attribute value" ...>
>     body
>     </mytag>
> 
>   or an empty tag
> 
>     <mytag attr1="attribute value" .../>
> 
> But, the JSP 1.1 spec doesn't seem to explicitly state that 
> 
>   <mytag attr1="attribute value" ...></mytag>
> 
> should be treated as an empty tag.
> 
> On the other hand, the JSP 2.0 draft spec clearly shows this 
> as a valid
> empty tag.
> 
> When using Tomcat 3.2.3, a tag library that I'm using has the 
> <bodycontent>
> tag in the TLD set to "empty" throws an exception stating 
> that the body is
> supposed to be empty when the tag is in the following format:
> <mytag></mytag>.
> I presume that Tomcat was developed to support the empty tag 
> as explicitly
> stated in the JSP 1.1 spec, although based on the JSP 2.0 
> draft it looks
> like the intent (or clarification) is that an opening and 
> closing tag with
> no content (not even a space; e.g, <mytag></mytag>) is to be 
> treated as an
> empty tag.  Does anyone know if this behavior has changed in 
> more recent
> versions of Tomcat, and if so, when this change occurred?
> 
> Thanks,
> Steve
> 
> --
> To unsubscribe, e-mail:   
> <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:tomcat-user-help@;jakarta.apache.org>
> 

--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>

Reply via email to