On Tue, 2003-06-03 at 11:23, Chen, Gin wrote: > <break> could be implemented better if it threw an exception meant to be > caught using JSP 1.2's TryCatchFinally interface, but the implementation > would still not be fully operable when custom tags were involved. In a > situation like > > <forEach> > <custom tag> > <break/> > </custom tag> > </forEach> > > the handler for <custom tag> would, if it implemented TryCatchFinally, > need to know to re-throw the exception that the inner <break> tag throws. > If it didn't, then <break>'s message would be lost and it would have no > effect. A <break> tag that we couldn't guarantee to work wouldn't be much > of a <break> tag!
One way around this might be just to say that if you want your tags to play nice with JSTL tags (break in particular) that it should implement J. Random Interface (or whatever) that deals with this parent tag communication issue. DAve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
