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" uri="http://java.sun.com/jstl
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 w
/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
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:
>>>
>
>
The JSTL expression language does not support method invocations on
objects.
Shawn Bayern wrote:
> On Mon, 18 Mar 2002, Dave Newton wrote:
>
>
>>On Monday 18 March 2002 02:43 pm, you wrote:
>>
>>>The JSTL expression language does not support method invocations on
>>>objects. You'll currently need to use a custom tag library or scriptlet
>>>code (with the fo
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:
Wh
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 b
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 xp.
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
tha
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:
>
> }"
No. Like I said, you can use an expression starting with 'param'
On Tuesday 19 Mar 2002 14H:38 pm, you wrote:
> 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:
> >
> >
> >
> > but it doesn't work ;-)
>
> Yes,
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"; %>
$header:host =
S param =
<%
java.util.Enumeration enum = request
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:
>
>
>
> but it doesn't work ;-)
Yes, because "request.parameter" means "the request-scoped variable na
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)
> >
> >
> >
> > So I'm assuming that the c-rt tld will evaluate SomeClass.COST as "the
> > variable COST in the class
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)
>
>
>
> 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 seem to work
> either :-)
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
On Tuesday 19 Mar 2002 14H:17 pm, you wrote:
> 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:
> >
> >
> >
> >
> >
> > but I'm rather thinking I can't. Can anyone
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:
>
>
>
>
>
> but I'm rather thinking I can't. Can anyone confirm this, and suggest
> another way?
I'm not sure what
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 Libr
On Tue, 19 Mar 2002, RAYMOND Romain wrote:
>
> in the source examples given I don't understand the easy way to map a
> request with a particular ressource bundle which will permit to use
> ... based on user's language preference. A
> solution coulb be to use a ruser session parameter but is the
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:
but I'm rather thinking I can't. Can anyone confirm this, and suggest another
way?
Cheers
John
--
John Baker, BSc CS.
Java Developer, TEAM/Slb. http://
Hello,
I'm writing a presentation of the latest JSTL, but I have a problem with one
example.
In JSP, I need something like
but it doesn't work. How can I pass parameters? All examples use only simple
getters. If someone knows the answer please reply ASAP because I have a
presentation in two d
Apologies if I've sent this already, but I didn't get a mail back so I'm
assuming it never got there ;-)
-- Forwarded Message --
Subject: Re: My last annoying question of the day, promise.:-)
Date: Mon, 18 Mar 2002 20:29:02 +
From: John Baker <[EMAIL PROTECTED]>
To: "Tag L
On Monday 18 Mar 2002 18:41 pm, you wrote:
> Just don't... ;-)
>
> Good Java style dictates that you keep everything as private as possible,
> certainly class variables and then use methods to get and set them, like
> getY and setY.
Yes, I understand good Java style (having done it for so long),
24 matches
Mail list logo
