tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Bucknam <br...@zat.com>
Subject Re: Runtime attribute expressions (was [BUG #40])
Date Wed, 11 Oct 2000 01:54:52 GMT
I agree with Craig's and Pierre's assessments of what to do about the
order-of-evaluation bug: document the problem for 3.2 and fix later.


While the subject is up, I'm building a tag library and had to decide
which tag attributes should be "run-time enabled" and which should not.

I was surprised to see that in the servlet code that JspC generates, the
code for run-time expressions looks more efficient than non-expressions.

That is, run-time exprs generate something like:
   _jspx_th_blah_foo_0.setAttribX(SimpleExpressionResult("splat"));

while non-expressions generate something like:
   JspRuntimeLibrary.introspecthelper(_jspx_th_blah_foo_0,
"AttribX","splat",null,null, false);


So... other than the order-of-evaluation bug, is there any reason not to
make every tag attribute "rtexpr-enabled"?  After all, every attribute
of non-custom tags (eg. <img>, <h1>, <body>, etc.) is fully
rtexpr-enabled, why shouldn't my custom tags be?

Thanks,
Brian
-----------------------------
Brian Bucknam
WebGain, Inc.



Mime
View raw message