Expresso 5.0 a major new release with more than 50 new features is now
available for download. Expresso is an open source architectural J2EE
framework comprising application development components which extends
Struts for developing database-driven web applications. Download freely
from:
On Thu, 17 Oct 2002, peter lin wrote:
we did verify acookie exists. I should have been more clear in my
original email.
That's not really the issue; the question is what's causing the error
logs that you're suggesting are indicative of a bug. Since the Standard
Taglib simply results
I will dig deeper and post my findings.
thanks
peter
Shawn Bayern wrote:
On Thu, 17 Oct 2002, peter lin wrote:
we did verify acookie exists. I should have been more clear in my
original email.
That's not really the issue; the question is what's causing the error
logs that you're
Hi all,
Is there a way to print out the items of a collection (e.x an array) in
reverse order using c:forEach or some other JSTL core tags?
Thanks
Hao
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail:
I wrote a basic test page and this is the result I get.
output
print out the classname
java.util.HashMap$Entry
java.util.HashMap$Entry
java.util.HashMap$Entry
print out the cookie
id1=value_for_id1
JSESSIONID=1B6A8CE1F51A31E335719420A239BEB2
On Thu, 17 Oct 2002, peter lin wrote:
It looks like using c:out value=${acookie.name}/ won't retrieve
the value, since acookie is a hashentry, it can't do
acookie.getName().toString(). I'm guessing that is correct
functionality right?
Right, for ${cookie} is a Map of all cookie names to
On Fri, 18 Oct 2002, Hao Ding wrote:
Is there a way to print out the items of a collection (e.x an array)
in reverse order using c:forEach or some other JSTL core tags?
Not as such. But since you ask, one solution does occur to me:
You can loop through the collection with c:forEach the first
It causes tomcat 4.1.12 to generate logs continuously. If I don't hit
stop in the browser, it will continue to generate logs. After a couple
of minutes, the log is tens of megs.
I don't know if it's the responsibility of the EL to throw an exception
or if jasper should be responsible. with is
I have worked out about this issue and I believe I have got an idea of
betterment to the jakarta standard taglibs1.0.x and possibly to the JSTL
specification.
Here I refrain the initial issue I raised just to remind it. I coded the
following JSP page
without EL it works fine. I've tried with scriplet code and it works
fine. I've tried it with the correct syntax and it works fine.
it's only when the syntax is incorrect that it doesn't throw an
exception like symbol cannot be resolved, clascastexception or some
other exception. Right or
On Fri, 18 Oct 2002 [EMAIL PROTECTED] wrote:
I have worked out about this issue and I believe I have got an idea of
betterment to the jakarta standard taglibs1.0.x and possibly to the JSTL
specification.
Here I refrain the initial issue I raised just to remind it. I coded the
following JSP
On Fri, 18 Oct 2002, peter lin wrote:
it's only when the syntax is incorrect that it doesn't throw an
exception like symbol cannot be resolved, clascastexception or
some other exception. Right or wrong, I expect the EL to realize
duh, that's the wrong syntax silly pete. I'm throwing an
I'm glad your just as confused as I am, since I honestly don't know
either :)
I was hoping you'd have the magic answer, but looks like I'll have to
dig around this weekend to figure what the exact cause is. thanks for
responding to my obtuse questions, since I'm confused as to why this
behavior
Shawn Bayern wrote :
In XPath, n:a is not a valid step; it
does not refer, as you seem to be expecting, to the node named 'a' in the
namespace identified by prefix 'n'. If you want to refer to this node,
you'll probably want to use the name() and namespace-uri() functions in
XPath.
Yes, I
additive:
-
x:out select=$foo/Envelope[namespace-uri()
='http://schemas.xmlsoap.org/soap/envelope']/Body[namespace-uri()
='http://schemas.xmlsoap.org/soap/envelope']/getPitchingResult[namespace-uri
On Fri, 18 Oct 2002 [EMAIL PROTECTED] wrote:
This long line could be shorten by the way I suggested as follows :
-
c:set target=ns property=s value=
http://schemas.xmlsoap.org/soap/envelope/
c:set target=ns
Does JSTL EL support creating objects?
for example the following sniplet:
center%= new java.util.Date() %/center
can i do this using jstl tags without first having to set up a bean?
in particular. I want to use the fmt tag to format this date.
Thanks,
-Tim
--
To unsubscribe, e-mail:
Chen, Gin wrote:
Does JSTL EL support creating objects?
for example the following sniplet:
center%= new java.util.Date() %/center
can i do this using jstl tags without first having to set up a bean?
in particular. I want to use the fmt tag to format this date.
No, but you can use the
Thanks Hans! :)
I was just trying to be lazy and do the creation of the bean in the fmt tag.
:-P
-Tim
-Original Message-
From: Hans Bergsten [mailto:hans;gefionsoftware.com]
Sent: Friday, October 18, 2002 1:44 PM
To: Tag Libraries Users List
Subject: Re: JSTL on the fly
Chen, Gin wrote:
I am trying to convert from Tomcat 3.2.1 to 4.0.4. I get invalid xml
parsing errors on app startup. When I remove the taglib elements from my
web.xml file, the app has no startup problems. These tags work fine with
3.2.1. Is this caused by improper installation of the JSTL?
Error:
PARSE error at
This seems confusing, but I think the specification is reasonably clear on
this. I believe you need ${pageContext.request.contextPath} instead.
-Original Message-
From: Chen, Gin [mailto:Gin_Chen;tvratings.com]
Sent: Friday, October 18, 2002 2:48 PM
To: 'Tag Libraries Users List'
Why is this not returning the same thing as the scriplet version?
c:out value=${request.contextPath}/
%= request.getContextPath() %
Thanks,
-Tim
--
To unsubscribe, e-mail: mailto:taglibs-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail:
David,
Thanks for answering. I feel pretty stupid. I made 2 changes at the
same time and incorrectly thought that removing the taglibs eliminated
the problem.
No so...
Sorry for the spam.
Rob Swan
Director of Operations
Object Publishing Software
Phone: 206-545-6851 ext 128
Email: [EMAIL
On Fri, 18 Oct 2002, Karr, David wrote:
This seems confusing, but I think the specification is reasonably
clear on this. I believe you need
${pageContext.request.contextPath} instead.
Right. There isn't any implicit 'request' object. It's named
'requestScope' to emphasize that it's used to
Section A.3.4 of the specification talks about using the [] operator to
access maps. From this, you can see that your EL expression would be
${preferredNames[staffMember]}. If you're using Struts-EL, you can just
use that as your value value on your html-el:text element.
-Original
-Original Message-
From: Wendy Smoak [mailto:Wendy.Smoak;asu.edu]
Sent: Friday, October 18, 2002 4:56 PM
Section A.3.4 of the specification talks about using the
[] operator to
access maps. From this, you can see that your EL
expression would be
26 matches
Mail list logo
