Sorry, it is not my intention to split hairs here. I am just saying that if you want to support the same syntax as the JSTL-EL you will nto be able to do it with JEXL. You are however more likely to be able to continue to support a JSTL syntax, as it evolves, by using the taglibs project. JEXL will not accomplish this. The original posters requirement was to cater to users who were familiar with the JSTL syntax.
Your point about JSTL-EL not existing outside the Servlet container is well taken, and it deserves to be made clear. So thank you. Michael On 6/30/05, Tim O'Brien <[EMAIL PROTECTED]> wrote: > > -----Original Message----- > > From: Michael Rasmussen [mailto:[EMAIL PROTECTED] > > Sent: Thursday, June 30, 2005 3:13 PM > > To: [email protected] > > Subject: RE: [EL] Docs ? > > > > >So, in other words, you couldn't claim to support "EL" outside of a = > > >servlet environment, but you could claim to support > > something similar to = > > >"EL", and that would be JEXL. > > > > That's not really true. I use the JSTL EL outside of servlets all the > > time. If you get the standard.jar from the jakarta-taglibs project > > you will find the ELEvaluator which uses JSTL style expressions. > > > > the fully qualified name in the jar is > > org.apache.taglibs.standard.lang.jstl.ELEvaluator > > > > If you want to claim to support "EL" you should get that jar. It may > > use commons EL as its underlying implementation, but i don't have a > > commons-el jar on my classpath, so I don't think it has any > > dependencies. Some of the taglibs guys could answer that better than > > I could. > > Yes, but more word mincing, you can't claim to support "EL" outside of a > JSTL or JSP context because it is an intimate part of those two > specifications. As of standard-1.1 I believe reliance of PageContext > was removed from ELEvaluator so you can include a JSP taglibrary in your > path if you want to provide support for "EL". (But, really you are just > providing support for "EL-like" syntax.) > > BTW, this is another one of those terrible situations where one codebase > seems to have been split long ago, one incarnation lives in commons-el > and another in standard. > > Tim > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
