,
reflection should NOT be needed. So, it's just like doing something
extra for no reason.
-Original Message-
From: Kris Schneider [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 4:51 PM
To: Tag Libraries Users List
Subject: Re: c:set and runtime expressions
Tarek Nabil wrote
Users List
Subject: Re: c:set and runtime expressions
only marginally relevant to this thread, I recently read arguments
against using Singletons in web apps:
http://wiki.apache.org/tomcat/OutOfMemory
Luca
Tarek Nabil wrote:
Thanks a lot Kris for the explanation.
Actually, I'm starting
this supported by default? I believe this is a question
for the JSR experts to answer.
-Original Message-
From: Kris Schneider [mailto:[EMAIL PROTECTED]
Sent: Monday, April 03, 2006 5:57 PM
To: Tag Libraries Users List
Subject: Re: c:set and runtime expressions
Tarek Nabil wrote:
So that means if I
Hi everyone,
I was using JSTL 1.1 in my application, and then unfortunately, I had to
downgrade to 1.0. Now, my IDE is complaining about this line in my JSP
c:set var=config value=%= Config.getInstance() %/
It says Attribute value does not accept runtime expressions.
This used
Hi everyone,
I'm moving from the Struts tag libraries to JSTL and I'm having a bit of
a hard time. Things don't work as I thought they would. For example, I'm
not able to use constants defined in classes for comparison, which is
something I used to do easily with Struts tags. Here's an
):
un:useConstants var=ct
className=com.mycom.app.SomeClassOrInterface /
c:forEach var=item items=${list}
c:choose
c:when test=${item.type == ct.EMPLOYEE}
bla bla relevant to employee
/c:when
Let me know if this helps
Luca
Tarek Nabil wrote:
Hi everyone,
I'm moving from
