DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31804>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31804

setParent() is not called on nested tags in a tag file (.tagx)

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From [EMAIL PROTECTED]  2004-10-20 22:55 -------
I may misunderstand your problem entirely, but I believe the behaviour you are
seeing is expected. 

According to javax.servlet.jsp.tagext.Tag.setParent() javadocs:

     * Set the parent (closest enclosing tag handler) of this tag handler.
     * Invoked by the JSP page implementation object prior to doStartTag().
     *
     * @param t The parent tag, or null.

Since <custom:submit> is not nested inside any custom tag invocation in your
.tagx snippet, NULL is passed to your tag handler's setParent().

Likewise, javax.servlet.jsp.tagext.SimpleTag.setParent() has this:

     * Sets the parent of this tag, for collaboration purposes.
     * <p>
     * The container invokes this method only if this tag invocation is 
     * nested within another tag invocation.
     *
     * @param parent the tag that encloses this tag

Since your SimpleTag isn't nested, the container does not call its setParent()
method at all.

> I would expect a reference to something, representing translated class of Tag 
> File (submit.tagx) is passed.

Your expectation is wrong. You should expect setParent() to be called on your
tag handler, and a non-null argument passed to it, only if your custom tag is
nested inside another custom tag.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to