https://issues.apache.org/bugzilla/show_bug.cgi?id=46339
Kin-Man Chung <kin-man.ch...@sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
--- Comment #10 from Kin-Man Chung <kin-man.ch...@sun.com> 2009-01-12 11:05:39
PST ---
I reread the spec on this issue carefully, and after some consideration, I've
come to the conclusion that it is best that we don't "fix" the spec and the
implementation now.
The original intend of the spec is to set the variables in the calling page/tag
before the invocation of the fragment. This is problematic, since that means
that fragments passed from one tag file to another cannot communicate with the
original caller using variables, as demonstrated in the case here. From the
paragraphs on page 2-78, the original spec author seemed to know this.
The way the variables are synchronized between the calling page and the tag
files is reminiscent of passing information in global variables and we all
know that global variables are evil. Any attempt for a simple fix to one
problem will cause problems in another area. My proposed fix for this problem
will cause problems with the save and restore operations at the tag entry and
exit. What is needed is a complete redesign of the way calling page and tag
files communicate. The is of course impractical or impossible at this time.
Therefore I am withdrawing my patch. Mark, please revert your changes. Sorry
for the inconvenience.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
