Following on from my posts earlier (sorry it ended up going twice or
whatever, sendmail was lieing to me), I'm wondering if I can do:
c:set var=searchType value=${Integer.class scope=session/
c:if test=${session.searchType == Integer.class
/c:if
but I'm rather thinking I can't. Can anyone
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 Tue, 19 Mar 2002, John Baker wrote:
Following on from my posts earlier (sorry it ended up going twice or
whatever, sendmail was lieing to me), I'm wondering if I can do:
c:set var=searchType value=${Integer.class scope=session/
c:if test=${session.searchType == Integer.class
/c:if
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
has anyone tried the nightly 3-18 xml tags in jstl? I'm experiencing a
problem accessing request parameters and http headers. Here is the test
page I used.
%@ taglib prefix=x uri=http://java.sun.com/jstl/ea/xml; %
br$header:host = x:out select=$header:host/br
brS param = x:out
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
reading over my last paragraph, it's not clear what I meant, so here's a
second attempt. The current 3-19 nightly of XPathUtil.valueOf is below:
public String valueOf(Node n, String xpath) throws SAXPathException
{
staticInit();
XPath xp = new XPath(xpath);
return
Peter,
Thanks for the bug report. There's actually no problem with the plumbing
of the XPathUtil class itself. It's correctly establishing the context
and passes it to our XPath engine. The problem was just that this XPath
engine wasn't resolving namespaces correctly.
I've fixed the problem
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:
Shawn Bayern wrote:
On Mon, 18 Mar 2002, Dave Newton wrote:
On Monday 18 March 2002 02:43 pm, you wrote:
c:if test=${securityBean.check(request, response) }
The JSTL expression language does not support method invocations on
objects. You'll currently need to use a custom tag library or
Sorry, the last response was an error. -M.
Mark Diggory wrote:
Shawn Bayern wrote:
On Mon, 18 Mar 2002, Dave Newton wrote:
On Monday 18 March 2002 02:43 pm, you wrote:
c:if test=${securityBean.check(request, response) }
The JSTL expression language does not support method
/ShowSource.jsp(10): Could not parse deployment descriptor:
org.xml.sax.SAXParseException: Could not parse taglib, starting at line 3
probably occurred due to an error in /ShowSource.jsp line 10:
%@ taglib prefix=c uri=http://java.sun.com/jstl/ea/core; %
thanks jens
Virengeprüft vom G DATA
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
On Tue, 19 Mar 2002, Jens Gersonde wrote:
/ShowSource.jsp(10): Could not parse deployment descriptor:
org.xml.sax.SAXParseException: Could not parse taglib, starting at
line 3 probably occurred due to an error in /ShowSource.jsp line 10:
%@ taglib prefix=c
18 matches
Mail list logo
