,
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
Tarek Nabil wrote:
Thanks a lot Luca for pointing this out. I must say it's completely new
information to me. I wonder if it's really accurate and relevant to all
containers.
For example, in Oracle Containers for Java (OC4J), when you redeploy an
application, the OC4J instance is restarted.
The implication that the example singleton class causes a memory leak just
because ...it creates a hard reference to a class instance into the class
itself is hard to believe. There are plenty of other ways to pin classes
loaded by the web app's class loader, but the singleton pattern isn't one
-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 use the RT-based version, then I won't be able to
use
EL? That's quite strange
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 to feel that moving to JSTL 1.0 was not such a
wise
that support EL evaluation
have attributes with rtexprvalue = false.
-Original Message-
From: Kris Schneider [mailto:[EMAIL PROTECTED]
Sent: Monday, April 03, 2006 6:26 AM
To: Tag Libraries Users List
Subject: Re: c:set and runtime expressions
If you need to run JSTL 1.0 and want
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
If you need to run JSTL 1.0 and want to use JSP expressions as attribute
values, you need to use the RT-based versions. For JSTL, there are
basically two distinct versions of each taglib:
%@ taglib prefix=curi=http://java.sun.com/jstl/core; %
%@ taglib prefix=c_rt
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
10 matches
Mail list logo
