> -----Original Message----- > From: Derek Scherger [mailto:[EMAIL PROTECTED] > > Karr, David wrote: > > The reason I implemented it this way is because in many > cases, the JSP > > attribute type in the base class was not String. However > in JSP 1.2, > > the EL expressions are Strings, so the BeanInfo for the JSP > tag class > > has to associate the attributes with String properties. I > then made > > the setter method for the String property convert the value to the > > correct type and then call the base class setter method. > > Hmm... I guess that kinda makes overriding things rather hard > doesn't it! Is it likely > that all of the attributes will eventually become strings on > the base classes at some > point in the future?
No, there's no reason for the base library to change for this, and there's no reason to put huge effort into optimizing Struts-EL, as it's only a transitional strategy. When you move your Struts application (using Struts-EL) to a JSP 2.0 container, you just remove Struts-EL and it works just as it did before (well, some of it at least :) ). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
