Craig -
Thank you for the quick response! more below...
"Craig R. McClanahan" wrote:
>
> 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.
Thank you for the directions - I will do so shortly!
>
> By the way, have you tried "tagdependent" instead of "TAGDEPENDENT"? These
> values are case sensitive.
Actually, in the tomcat code they are case-insensitive. I am fairly
certain that the spec does not require it to be sensitive either. In
any case, the code that is supposed to branch on TAGDEPENDENT vs. JSP
vs. EMPTY makes no distinction between the first two - simply processes
it as JSP anyway!
>
> >
> > 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.
>
Now that you point it out, that makes a helluva lotta sense! That is
almost exactly what I am trying to do, alter the runtime processing.
Sounds like I want to be doing taglibs for directives, but unfortunately
there is no way to do this in JSP AFAIK. Yerch! I can think of some
other work-arounds to the issue, requiring the use of nested tags for
doing the right kind of short-circuiting I want (I am trying to port an
XML-based templating system I use at work to JSP to do performance
comparisons), but it would be nice if I could to it The Right Way(TM).
Sigh...
> >
> > Thanx!
> >
> > jeff
> >
>
> Craig McClanahan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
--
Jeffrey & Nikole Bonevich
Maxmillian Bonevich
Ann Arbor, Michigan
[EMAIL PROTECTED]
http://www.bonevich.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
