Right. It's easy to forget (or to never have looked), but Properties extends
Hashtable which implements Map...
Quoting "K.C. Baltz" <[EMAIL PROTECTED]>:
> I'm not sure if EL handles properties, but if it's going to work like a
> HashMap, it'll look like this:
>
> ${applicationScope.props["viewe
I'm not sure if EL handles properties, but if it's going to work like a
HashMap, it'll look like this:
${applicationScope.props["viewer.tool.useZoomIn"]}
That should get around the problem of the "."s in the name.
K.C.
John C Cartwright wrote:
Hello All,
I'm trying to use the value of a pro
Hello All,
I'm trying to use the value of a property in a element.
I have the Properties object in application scope, but I can't seem to
figure out how (of if) I can address the individual property value of a
given key. Something like props.get("viewer.tool.useZoomIn") in a
scriptlet.
I th
try using fmt:setLocale and scope="session"
it will break and give you a really helpful error report.
http://www.mail-archive.com/[EMAIL PROTECTED]/
msg03702.html
c
On Thursday 20 November 2003 14:49, Morrow, Steve D. wrote:
> Really? I haven't had any trouble with the fmt tags.
> Double-check
Really? I haven't had any trouble with the fmt tags. Double-check to be sure
you've got the fmt.tld and the jars in the right place, and the URI correct.
Also, you may want to verify that you're using the correct TLD version.
/WEB-INF/lib/standard.jar
/WEB-INF/fmt.tld
<%@ taglib prefix="fmt" uri="
hehe, that's what I do at the moment. apparently it doesn't
work for fmt tags though. :-(.
c
On Thursday 20 November 2003 14:35, Morrow, Steve D. wrote:
> If you put the standard.jar and jstl.jar files in your
> /WEB-INF/lib directory of your webapp, and the
> corresponding TLD files in /WEB-IN
No, really, just use "http://java.sun.com/jstl/core";. It's essentially just a
namespace identifier, the container's not going to make a connection.
Quoting "Morrow, Steve D." <[EMAIL PROTECTED]>:
> If you put the standard.jar and jstl.jar files in your /WEB-INF/lib
> directory of your webapp, an
If you put the standard.jar and jstl.jar files in your /WEB-INF/lib
directory of your webapp, and the corresponding TLD files in /WEB-INF, you
can use <%@ taglib prefix="c" uri="/WEB-INF/c.tld"%>, for example. No
connectivity problems... :o)
> -Original Message-
> From: Caoilte O'Connor [m
will that work testing a container not connected to the
internet though? I'd hate to be sitting on the train with
my laptop getting "cannot download taglib" type errors.
c
On Thursday 20 November 2003 14:11, Kris Schneider wrote:
> As of JSP 1.2, there's really no need for separate tld
> files
As of JSP 1.2, there's really no need for separate tld files and
entries in web.xml - at least for packaged taglibs like Struts and JSTL. Just
use the following directive in your JSP:
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core"; %>
Quoting Caoilte O'Connor <[EMAIL PROTECTED]>:
> a
aaah. many thanks. that looks exactly like what i want.
should i replace my c taglibs (and others), presently URI="/
WEB-INF/c.tld" with "http://java.sun.com/jstl/c"; too?
c
On Thursday 20 November 2003 13:39, Kris Schneider wrote:
> You might try using a servlet filter to keep the locales
> in
You might try using a servlet filter to keep the locales in sync:
import javax.servlet.jsp.jstl.core.Config;
...
HttpSession session = request.getSession(true);
Locale locale = (Locale)session.getAttribute(Globals.LOCALE_KEY);
if (locale == null) {
locale = request.getLocale();
}
Config.set(sess
hey all,
I'm playing around and trying to get the jstl
internationalization tags working with struts. It's proving
a bit more of a headache than I'd like.
I made the usual changes and eventually figured out that the
1.0.0 release (included in the struts 1.1 contrib dir) is
seriously broken.
N
13 matches
Mail list logo
