This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
i have a question would it make any sense to have a <body-content>tagdependent</body-content> and ur tag handler class extending TagSupport . since there is now way to access the BodyContent of the tag .. and assuming u include EVAL_BODY_INCLUDE in doAfterBody, will the body show up as is(assuming its not a valid jsp code> ?. or is it a error to specify "tagdependent" as a value for a class which extendes TagSupport or implements InterationTag ? could some please clarify ?
Hi, I read the specification completely and I don't remember that there exists something telling that "tagdependent" and extending TagSupport (or impementing IterationTag) will cause some error. I dont't think containers will check fot that. Anyway, you are right, in general, if you are using "tagdependent" you are probably going to manipulate the content of the body. But you can only do that if you implements the BodyTag interface. BTW, let me correct something, EVAL_BODY_INCLUDE is not an option for doAfterBody(), it is only for doStartTag(). Dani