Hi Kevin:
The observed behavior is what the specification requests. The behavior
you are expecting has a significant implementation and performance cost
in a compiled-based implementation of JSP. Although there are some
interpreted-based JSP implementations, we want to enable compiled-based
implementations.
If you really want to be this dynamic you could either generate a new
JSP page and then include it dynamically (this gets into the fuzzy area
of the spec/implementation for JSP 1.1), or generate a class file
dynamically (ditto).
A future spec could include a translation-time tag description
mechanism. At that time it is easy to define the semantics of a tag in
terms of JSP/html. But that is not a request-time dynamic semantics.
This type of approach tends to also be difficult to maintain. Can you
give us more details about why you are doing it that way?
Hope this helps,
- eduard/o
=================
Date: Thu, 6 Jan 2000 13:49:45 -0800
From: Kevin Unger <[EMAIL PROTECTED]>
Subject: BodyTag re-evaluation
We are trying to use a tag extension with a body. Our tag handler needs
to replace the body and have the
replacement text
evaluated as JSP. When we return EVAL_BODY_TAG from the doAfterBody()
method, the behavior is not what we expected.
In
doAfterBody(), we load the bodyContent object with JSP/HTML text, then
return with EVAL_BODY_TAG. But the text we
put in the
bodyContent object is not evaluated, rather the original text of the
body of our tag is re-evaluated.
We are convinced that we must be missing something. Can anybody help?
--
Kevin Unger
Senior Developer
______________ ____________
/
MULTIMEDIA ((o)) L I V E
___________ /_______________
625 Second Street, Suite 100
Petaluma, CA 94549
[EMAIL PROTECTED]
www.mmlive.com
707-773-4222
707-773-3592 (fax)
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
