> -----Original Message----- > From: Henri Yandell [mailto:bayard@;generationjava.com] > Sent: Friday, November 01, 2002 11:21 AM > > On Fri, 1 Nov 2002, Karr, David wrote: > > > If there's interest in "EL-izing" certain non-ELed tag libraries, > > without changing the library (so the original library can > still work in > > Servlet 2.2 environments), and you don't want to wait for > JSP 2.0, you > > might consider using the strategy I used in building the > Struts-EL tag > > library. > > I was thinking of a strategy that basically did a: Is this class > [ExpressionEvaluator or whatever it is] in the classpath. If so, then > cache this result statically [in my StringTagSupport] and > make sure that > ELizing happens. > > Any reason this would fail? > > String taglib has a pretty simple design, there's only one > actual taglib > class, all the rest just do String transformations and not > tag stuff, so > it can be nice and easy to upgrade :)
You're intending to store the class name as a string somewhere, determine whether you can load it, and then call the methods of the class through Reflection? I suppose that would work. You'll have to rip out that code when you move to JSP 2.0. If you used a subclass, you would just remove the subclass. -- To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
