one of the things I've liked about struts is its ability to filter into legacy code without asking too much...
The issues I presented are of some concern to anyone who is thinking about using the struts-el libraries. I think, unlike the other struts tags, that these libraries are not intended to be used by anyone who wants to 'filter' their struts into old JSP/servlet applications. Unless you are starting an application from scratch (sans scriptlets) and in true MVC style, the struts-el seems not to be appropriate.... Granted, this is because struts-el is faithful to the EL spec. Read the JSTL specification. It should clarify some of these issues. If you write pages that avoid using scriptlets (perhaps by concentrating on the MVC paradigm), you won't have these issues (except for the constants issue). If you have specific questions about the JSTL, it would be better to ask them on the "taglibs-user" list. > -----Original Message----- > From: Dan Eklund [mailto:[EMAIL PROTECTED] > > Hello all, > > I'm a bit concerned (after spending a few days spinning my wheels) on > a few aspects of the EL implementation both with the struts-el libraries > and the JSTL core EL implementation. > The following are a few of my observations. I was wondering if people > here could confirm these as problematic, or tell me I'm smoking crack. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
