Re: EL expressions not being evaluated..

2006-09-13 Thread maya 
oh brother.. this means I would have to upgrade to sdk 1.5 from 1.4 
(Tomcat 5.5 requires 1.5..  it might not be a bad idea, though, b/c I 
also want to start playing with NetBeans..  but have been reluctant to 
upgrade everything...:)


ok, many thanks to everyone for your help..



Rashmi Rubdi wrote:
Set up a fresh install of the latest Tomcat on the side with the correct web.xml entry, and put a test jsp page in it with a simple EL expression and see if it evaluates. 
   
  I have apache-tomcat-5.5.12
   
  and a different set of jar files under apache-tomcat-5.5.12\common\lib : 
   
  commons-el.jar

jasper-compiler-jdt.jar
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
jstl.jar
naming-factory-dbcp.jar
naming-factory.jar
naming-resources.jar
serializer.jar
servlet-api.jar
standard.jar
xalan.jar

maya [EMAIL PROTECTED] wrote:
  Kris Schneider wrote:

maya wrote:
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?
Don't worry about that stuff, focus on your app. The first thing to do 
is to make sure you're using a Servlet 2.4 web.xml. It should look 
something like this:




xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee 
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;

version=2.4

...



If you're using a Servlet 2.3 web.xml, then EL will be ignored by default.



thank you very much.. I put what you posted in my web.xml (in lieu of
what I had there previously (and what I have in all web.xml's in 
Tomcat), namely



PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;




I put the code you posted in both the web.xml for the particular webapp
and in conf/web.xml.. but EL expressions are still not evaluating..
this is how a JSP with EL prints in the browser (IE  FF..)

Request Method: ${pageContext.request.method}
Request Protocol: ${pageContext.request.protocol}
Context Path: ${pageContext.request.contextPath}

Remote Host: ${pageContext.request.remoteHost}
Secure: ${pageContext.request.secure}
Cookies: ${c.name}: ${c.value}
Headers: ${h.key}: ${value}


thanks again



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates 
starting at 1¢/min.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: EL expressions not being evaluated..

2006-09-13 Thread Kris Schneider 

maya wrote:
oh brother.. this means I would have to upgrade to sdk 1.5 from 1.4 
(Tomcat 5.5 requires 1.5..  it might not be a bad idea, though, b/c I 
also want to start playing with NetBeans..  but have been reluctant to 
upgrade everything...:)


TC 5.5 should work just fine with JDK 1.4. Make sure to download the 
apache-tomcat-[version]-compat.zip file and install it after the base distro.



ok, many thanks to everyone for your help..



Rashmi Rubdi wrote:

Set up a fresh install of the latest Tomcat on the side with the 
correct web.xml entry, and put a test jsp page in it with a simple EL 
expression and see if it evaluates.  I have apache-tomcat-5.5.12
 and a different set of jar files under 
apache-tomcat-5.5.12\common\lib :  commons-el.jar

jasper-compiler-jdt.jar
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
jstl.jar
naming-factory-dbcp.jar
naming-factory.jar
naming-resources.jar
serializer.jar
servlet-api.jar
standard.jar
xalan.jar

maya [EMAIL PROTECTED] wrote:
  Kris Schneider wrote:


maya wrote:

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?


Don't worry about that stuff, focus on your app. The first thing to 
do is to make sure you're using a Servlet 2.4 web.xml. It should look 
something like this:




xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;


xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee 
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;

version=2.4

...



If you're using a Servlet 2.3 web.xml, then EL will be ignored by 
default.




thank you very much.. I put what you posted in my web.xml (in lieu of
what I had there previously (and what I have in all web.xml's in 
Tomcat), namely



PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;




I put the code you posted in both the web.xml for the particular webapp
and in conf/web.xml.. but EL expressions are still not evaluating..
this is how a JSP with EL prints in the browser (IE  FF..)

Request Method: ${pageContext.request.method}
Request Protocol: ${pageContext.request.protocol}
Context Path: ${pageContext.request.contextPath}

Remote Host: ${pageContext.request.remoteHost}
Secure: ${pageContext.request.secure}
Cookies: ${c.name}: ${c.value}
Headers: ${h.key}: ${value}


thanks again


--
Kris Schneider mailto:[EMAIL PROTECTED]
D.O.Tech   http://www.dotech.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: EL expressions not being evaluated..

2006-09-13 Thread maya 


interesting.. I didn't know they had a 1.4-compatible package for 5.5.. 
 again, many thanks to all..




Kris Schneider wrote:

maya wrote:
oh brother.. this means I would have to upgrade to sdk 1.5 from 1.4 
(Tomcat 5.5 requires 1.5..  it might not be a bad idea, though, b/c I 
also want to start playing with NetBeans..  but have been reluctant to 
upgrade everything...:)


TC 5.5 should work just fine with JDK 1.4. Make sure to download the 
apache-tomcat-[version]-compat.zip file and install it after the base 
distro.



ok, many thanks to everyone for your help..



Rashmi Rubdi wrote:

Set up a fresh install of the latest Tomcat on the side with the 
correct web.xml entry, and put a test jsp page in it with a simple EL 
expression and see if it evaluates.  I have apache-tomcat-5.5.12
 and a different set of jar files under 
apache-tomcat-5.5.12\common\lib :  commons-el.jar

jasper-compiler-jdt.jar
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
jstl.jar
naming-factory-dbcp.jar
naming-factory.jar
naming-resources.jar
serializer.jar
servlet-api.jar
standard.jar
xalan.jar

maya [EMAIL PROTECTED] wrote:
  Kris Schneider wrote:


maya wrote:

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?


Don't worry about that stuff, focus on your app. The first thing to 
do is to make sure you're using a Servlet 2.4 web.xml. It should 
look something like this:




xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;


xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee 
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;

version=2.4

...



If you're using a Servlet 2.3 web.xml, then EL will be ignored by 
default.




thank you very much.. I put what you posted in my web.xml (in lieu of
what I had there previously (and what I have in all web.xml's in 
Tomcat), namely



PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;




I put the code you posted in both the web.xml for the particular webapp
and in conf/web.xml.. but EL expressions are still not evaluating..
this is how a JSP with EL prints in the browser (IE  FF..)

Request Method: ${pageContext.request.method}
Request Protocol: ${pageContext.request.protocol}
Context Path: ${pageContext.request.contextPath}

Remote Host: ${pageContext.request.remoteHost}
Secure: ${pageContext.request.secure}
Cookies: ${c.name}: ${c.value}
Headers: ${h.key}: ${value}


thanks again





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: EL expressions not being evaluated..

2006-09-12 Thread Andrés Florit 

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 [EMAIL PROTECTED] wrote:


On 9/11/06, maya [EMAIL PROTECTED] 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..

snip/

http://wiki.apache.org/jakarta-taglibs/FrequentlyAskedQuestions

-Rahul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: EL expressions not being evaluated..

2006-09-12 Thread Rashmi Rubdi 
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.

Re: EL expressions not being evaluated..

2006-09-12 Thread maya 
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]

Re: EL expressions not being evaluated..

2006-09-12 Thread Andrés Florit 

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]

Re: EL expressions not being evaluated..

2006-09-12 Thread maya 
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]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: EL expressions not being evaluated..

2006-09-12 Thread Kris Schneider 

maya wrote:
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?


Don't worry about that stuff, focus on your app. The first thing to do is 
to make sure you're using a Servlet 2.4 web.xml. It should look something 
like this:


?xml version=1.0 encoding=UTF-8?
web-app xmlns=http://java.sun.com/xml/ns/j2ee;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee 
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;

 version=2.4

  ...

/web-app

If you're using a Servlet 2.3 web.xml, then EL will be ignored by default.


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


--
Kris Schneider mailto:[EMAIL PROTECTED]
D.O.Tech   http://www.dotech.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: EL expressions not being evaluated..

2006-09-12 Thread maya 

Kris Schneider wrote:

maya wrote:
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?


Don't worry about that stuff, focus on your app. The first thing to do 
is to make sure you're using a Servlet 2.4 web.xml. It should look 
something like this:


?xml version=1.0 encoding=UTF-8?
web-app xmlns=http://java.sun.com/xml/ns/j2ee;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee 
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;

 version=2.4

  ...

/web-app

If you're using a Servlet 2.3 web.xml, then EL will be ignored by default.



thank you very much.. I put what you posted in my web.xml (in lieu of
what I had there previously (and what I have in all web.xml's in 
Tomcat), namely


?xml version=1.0 encoding=ISO-8859-1?
!DOCTYPE web-app
 PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;

web-app
   

I put the code you posted in both the web.xml for the particular webapp
and in conf/web.xml..  but EL expressions are still not evaluating..
this is how a JSP with EL prints in the browser (IE  FF..)

Request Method: ${pageContext.request.method}
Request Protocol: ${pageContext.request.protocol}
Context Path: ${pageContext.request.contextPath}
  
Remote Host: ${pageContext.request.remoteHost}
Secure: ${pageContext.request.secure}
Cookies: ${c.name}: ${c.value}
Headers: ${h.key}: ${value}


thanks again



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: EL expressions not being evaluated..

2006-09-12 Thread Rashmi Rubdi 
Set up a fresh install of the latest Tomcat on the side with the correct 
web.xml entry, and put a test jsp page in it with a simple EL expression and 
see if it evaluates. 
   
  I have apache-tomcat-5.5.12
   
  and a different set of jar files under apache-tomcat-5.5.12\common\lib : 
   
  commons-el.jar
jasper-compiler-jdt.jar
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
jstl.jar
naming-factory-dbcp.jar
naming-factory.jar
naming-resources.jar
serializer.jar
servlet-api.jar
standard.jar
xalan.jar

maya [EMAIL PROTECTED] wrote:
  Kris Schneider wrote:
 maya wrote:
 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?
 
 Don't worry about that stuff, focus on your app. The first thing to do 
 is to make sure you're using a Servlet 2.4 web.xml. It should look 
 something like this:
 
 
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee 
 http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;
 version=2.4
 
 ...
 
 
 
 If you're using a Servlet 2.3 web.xml, then EL will be ignored by default.
 

thank you very much.. I put what you posted in my web.xml (in lieu of
what I had there previously (and what I have in all web.xml's in 
Tomcat), namely


PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;




I put the code you posted in both the web.xml for the particular webapp
and in conf/web.xml.. but EL expressions are still not evaluating..
this is how a JSP with EL prints in the browser (IE  FF..)

Request Method: ${pageContext.request.method}
Request Protocol: ${pageContext.request.protocol}
Context Path: ${pageContext.request.contextPath}

Remote Host: ${pageContext.request.remoteHost}
Secure: ${pageContext.request.secure}
Cookies: ${c.name}: ${c.value}
Headers: ${h.key}: ${value}


thanks again



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates 
starting at 1¢/min.

EL expressions not being evaluated..

2006-09-11 Thread maya 
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..









-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: EL expressions not being evaluated..

2006-09-11 Thread chuanjiang lo 

i think it is the servlet specifications

if i am not wrong servlet 2.3 specifications does not evaluate the EL
expressions..

On 9/12/06, maya [EMAIL PROTECTED] 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..








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: EL expressions not being evaluated..

2006-09-11 Thread Rahul Akolkar 

On 9/11/06, maya [EMAIL PROTECTED] 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..


snip/

http://wiki.apache.org/jakarta-taglibs/FrequentlyAskedQuestions

-Rahul

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]