Jeffrey Bonevich wrote:
> Hello all! A question in search of an answer...
>
> I am developing a tag library, and for one particular tag I want to
> prevent the body content from being processed as JSP. I know I can
> prevent this by declaring <body-centent>TAGDEPENDENT</body-content> in
> the descriptor file for the library. (I am aware that TAGDEPENDENT has
> not been implemented in tomcat yet, 3 or 4, but I found a patch and
> fixed it up on my own. Tomcat-dev mailing list response to questions on
> this was nil, so I may have to make a bigger stink to get the actual
> patch put into the code base.)
>
The best way to "make a bigger stink" about this, or any other such issue,
is to submit a bug report:
http://nagoya.apache.org/bugzilla/
under the appropriate "Tomcat 3" and/or "Tomcat 4" product categories and
versions.
By the way, have you tried "tagdependent" instead of "TAGDEPENDENT"? These
values are case sensitive.
>
> However, once I have obtained the un-processed body content in
> doAfterBody() and have done the post-processing of that content that I
> want to do, I am at a complete loss as to how to turn around and have
> the "new" body content processed as JSP. JSP 1.2 spec/Tomcat appear to
> lack any clear hook to let you manually process a string/stream as JSP.
> Any ideas?
>
JSP doesn't support this concept of trying to generate JSP content on the
fly, and then process it. The reason is that all the compile processing
happens only at compile time, whereas you are trying to do so at runtime.
>
> Thanx!
>
> jeff
>
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
