I was looking through the log output for my new <@ISINT> custom tag.
I was quite surprised by a few things.
1. The server looks for the class on each use, which is HIGHLY
inefficient. I would have thought that a Custom Tag would get
loaded in system scope and be optimized in various ways. (Always
loaded for example). Can this be adjusted with the tag definition
xml? I notice that the object definition provided by the custom tag
generator specifies local scope. If I changed this to system scope,
would the tag then be always loaded and persistent?
2. I'm still quite surprised to see that TCFs can only be specified
relative to an appfile (or its containing directory). I naively
assumed that a Custom Tag could be saved in /usr/local/witango so it
could be available to all appfiles.
Anyway, if a custom tag is slower and can't be globally available, it
looks like it might be more trouble than just including the method in
one of my persistent class files. Any thoughts or suggestions?
Bill
William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
