I have to say that I personally think whomever made this decision made a
poor decision. I do not, of course, have all the facts and the reasons why
such a decision was made, but it would seem to be too drastic to be
justfied.
The use of templating in tag libraries centers around this sort of code. I
don't have a vote or anything, of course, but, if I did, I certainly would
vote against this. Doesn't this break Struts templating? I don't use
Struts, but do follow that sort of architectural premise.
-----Original Message-----
From: Rickard �berg <[EMAIL PROTECTED]>
To: Tomcat Developers List <[EMAIL PROTECTED]>
Date: Sunday, October 28, 2001 12:15 AM
Subject: Re: Tomcat4, taglibs, and pageContext.include
>Micael Padraig Og mac Grene wrote:
>
>> Would you please expand on the ramifications?
>>
>> Surely this does not mean that we won't be able to use <jsp: include
[etc]>
>> tags? Does this mean that we won't be able to use code like:
>>
>> try {
>> pageContext.include(content.toString());
>> } catch(Exception e) {
>> throw new JspException(e.getMessage());
>> }
>>
>> In our tag classes?
>
>
>That is precisely what it means. :-(
>
>/Rickard
>
>
>
>--
>To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
