On Mon, 18 Mar 2002, John Baker wrote:
That's a real minus point for JSTL.
In defense of the way JSTL currently works, this isn't really its job.
The design standard for components is JavaBeans, which outlines what's a
property and what's not.
--
Shawn Bayern
Author, JSP Standard Tag
On Tuesday 19 Mar 2002 14H:11 pm, you wrote:
On Mon, 18 Mar 2002, John Baker wrote:
That's a real minus point for JSTL.
In defense of the way JSTL currently works, this isn't really its job.
The design standard for components is JavaBeans, which outlines what's a
property and what's not.
On Tue, 19 Mar 2002, John Baker wrote:
When I was reading the spec, I got the impression this was possible: (section
6.1.5)
c-rt:out value=%= SomeClass.COST %/
So I'm assuming that the c-rt tld will evaluate SomeClass.COST as the
variable COST in the class SomeClass. But that doesn't
On Tuesday 19 Mar 2002 14H:29 pm, you wrote:
On Tue, 19 Mar 2002, John Baker wrote:
When I was reading the spec, I got the impression this was possible:
(section 6.1.5)
c-rt:out value=%= SomeClass.COST %/
So I'm assuming that the c-rt tld will evaluate SomeClass.COST as the
On Tue, 19 Mar 2002, John Baker wrote:
Ok, one more before I shut up.
I'm trying to write this in JSTL:
if (request.getParameter(moo).equals(cows))
and so far I've got:
c:if test=${request.parameter.moo == 'cows'}
but it doesn't work ;-)
Yes, because request.parameter means the
On Tue, 19 Mar 2002, John Baker wrote:
Bah. So how can this be done in JSTL? It's a real shame because that
would be very nice. I'm trying to avoid writing Java ;-) Does this
mean I have to use the -rt stuff and do:
c-rt:if test=${ $=request.getParameter(moo).equals(cows) % }
No. Like I
On Tuesday 19 Mar 2002 14H:47 pm, you wrote:
No. Like I said, you can use an expression starting with 'param':
${param.moo == 'cows'}
Ah ha! That's what I was missing! I didn't realise param.moo is actually
request.getParameter(moo). And I can't see anywhere obvious in the spec
that
On Tuesday 19 Mar 2002 14H:47 pm, you wrote:
I don't mind answering all your questions, but you might want to take an
hour and read through the entire JSTL draft spec! I think it'll answer a
lot of your questions. :-)
For example :-)
Section 6. Iterators.
The first example given:
On Tue, 19 Mar 2002, John Baker wrote:
What the spec fails to tell me is where customers came from. Is it a request
attribute? A session attribute? Does it mean I can do this:
Your questions all seem to concern the expression language. You should
read Appendix A for information on how it
I'm busy digesting the jstl spec now (found an error in it, it says you can
do c:url= and it should be c:url value=... :-), however I'm wondering
if I can put an array of objects into a request and use c:if test= to test
one. Ie:
Blob[] blobs = new Blob[100];
// fill blobs
On Mon, 18 Mar 2002, John Baker wrote:
I'm busy digesting the jstl spec now (found an error in it, it says you can
do c:url= and it should be c:url value=... :-), however I'm wondering
if I can put an array of objects into a request and use c:if test= to test
one. Ie:
Blob[] blobs
On Monday 18 Mar 2002 18H:01 pm, you wrote:
The error message was: Unable to find a value for 0 in object of class
java.lang.String using operator []
Argh...
Spot the difference between:
c:set var=blobs value=whatever.someMethodThatReturnsList/
and
c:set var=blobs
On Monday 18 Mar 2002 18H:07 pm, you wrote:
Current time in milliseconds:
c:out value=${page.dates[1].time}/
This prints out output like:
Current time in milliseconds: 1016474790054
Hope you can use this as a basis to determine what's wrong with your
page. Best,
Yeah, sorry, I
define all the getter methods you need, and off you go!
-Original Message-
From: John Baker [mailto:[EMAIL PROTECTED]]
Sent: Montag, 18. März 2002 19:31
To: Tag Libraries Users List
Subject: Re: My last annoying question of the day, promise.:-)
On Monday 18 Mar 2002 18H:07 pm, you wrote
14 matches
Mail list logo
