Re: EL expressions not being evaluated..
maya <[email protected]>
| Newsgroups | gmane.comp.jakarta.taglibs.user |
|---|---|
| Message-ID | <[email protected]> |
again, thank you all very much.. as mentioned, I have Tomcat 5.0.27, which comes with the following (as specified in release-notes.txt that comes with it): * commons-collections*.jar (Commons Collections 2.1 or later) * commons-dbcp.jar (Commons DBCP 1.1 or later) * commons-el.jar (Commons Expression Language 1.0) * commons-logging-api.jar (Commons Logging API 1.0.3 or later) * commons-pool.jar (Commons Pool 1.1 or later) * jasper-compiler.jar (Jasper 2 Compiler) * jasper-runtime.jar (Jasper 2 Runtime) * jsp-api.jar (JSP 2.0 API) * commons-el.jar (JSP 2.0 Expression Language) * naming-common.jar (JNDI Context implementation) * naming-factory.jar (JNDI object factories for J2EE ENC support) * naming-resources.jar (JNDI DirContext implementations) * servlet-api.jar (Servlet 2.4 API) this means my EL expressions should evaluate, right? thank you again.. Andrés Florit wrote: > With JSP 2.0 you can use EL in all the page because it is part of the > specification. Whit JSP 1.2 you can only use it with JSTL tags and customs > tags (this last one I'm not very sure). EL is evaluated before the JSP > is converted to a servlet, so I don't think you can use it in a servlet. > Here's a good link about the differences between JSP 1.2 and 2.0. > > http://www.onjava.com/pub/a/onjava/2003/11/05/jsp.html > > Andrés > > > > > On 9/12/06, maya <[email protected]> wrote: >> >> thank you all very much for your responses.. will have to check >> everything you guys say tonight at home (off the top of my head, I know >> I have Tomcat 5.0.27 and, as far as I know, JSP 2.0; Servlet 2.4 specif >> (this I know for sure, I looked it up when downloaded JSTL..) >> >> one of the respondents seemed to be implying you can only use EL with >> JSTL, I don't suppose I understood right, since I assume it can also be >> used with custom tags and beans.. >> >> again, thank you very much.. >> >> -m >> >> >> Rashmi Rubdi wrote: >> > Behind the scenes JSPs are Servlets . >> > >> > I had the same problem as maya is facing and after following the >> instructions here: >> http://wiki.apache.org/jakarta-taglibs/FrequentlyAskedQuestions , and >> making sure that there was no version mismatch between the .tld files and >> the URIs and getting the correct versions of the JAR files solved the >> problem. >> > >> > -Rashmi >> > >> > Andrés Florit <[email protected]> wrote: >> > Expression Language (EL) is part of the JSP 2.0 specification. If I'm >> not >> > wrong it has anything to do with servlets. If you use JSP 1.2 you have >> to >> > import the JSTL libraries. I think that Tomcat 5 implemnts JSP 2.0. >> > Sorry my english. >> > >> > Andrés >> > >> > >> > On 9/12/06, Rahul Akolkar wrote: >> >> On 9/11/06, maya wrote: >> >>> I can't get my EL expressions to evaluate to what they're supposed >> to... >> >>> they print verbatim, in both IE and FF, like for example: >> >>> >> >>> Server Name: ${pageContext.request.serverName} >> >>> Server Port: ${pageContext.request.serverPort} >> >>> Remote Address: ${pageContext.request.remoteAddr} >> >>> Remote Host: ${pageContext.request.remoteHost} >> >>> >> >>> or this in a bean: >> >>> >> >>> Name retrieved from JavaBean has the value of: ${param.name}. >> >>> >> >>> anything else I've tried to do w/EL it always prints like this in >> >>> browser.. why is this.. (running on Tomcat 5, everything pretty >> >>> standard..) thank you.. >> >>> >> >> >> >> http://wiki.apache.org/jakarta-taglibs/FrequentlyAskedQuestions >> >> >> >> -Rahul >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> > >> > >> > >> > --------------------------------- >> > Stay in the know. Pulse on the new Yahoo.com. Check it out. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >