llin VanDyck [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 14, 2003 9:59 AM
To: [EMAIL PROTECTED]
Cc: David Cummings
Subject: Re: Pass custom parameters into an XSP
Hi
When I try this out, I get the following message:
org.apache.cocoon.www.tasks.docs.workflow.details_xsp should be declared
a
6:50
PM
Subject: RE: Pass custom parameters into
an XSP
Actually, you don't need to override
setup().
The
base class of the XSP generated class already does that and provides
"protected Parameters parameters;"
You
can use directly in
David
CummingsSubject: Re: Pass custom parameters into an
XSP
Wow. I did not know you could use the XSP to
override the setup method. That is VERY helpful. Thanks!!
- Original Message -
From:
Marco Rolappe
To: [EMAIL
he other nice features of
Parameters such as defaulting and converting to int, boolean, and so
on.
-Original Message-From: Collin VanDyck
[mailto:[EMAIL PROTECTED]]Sent: Donnerstag, 13. Februar 2003
00:04To: [EMAIL PROTECTED]Cc: David
CummingsSubject: Re: Pass custom parameters in
lto:[EMAIL PROTECTED]]Im
Auftrag von Collin VanDyckGesendet: Mittwoch, 12. Februar
2003 22:44An: [EMAIL PROTECTED]Betreff: Pass
custom parameters into an XSP
Hello,
I am trying to figure out how I can pass in
custom parameters into an already existing generator s
r(s)
here
...
super.setup (resolver, objectModel, src,
params);
}
HTH
-Ursprüngliche Nachricht-Von:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Collin VanDyckGesendet: Mittwoch, 12. Februar 2003
22:44An: [EMAIL PROTECTED]Betreff: Pass custom
Hello,
I am trying to figure out how I can pass in custom
parameters into an already existing generator such as the XSP/serverpages
generator. Here's my scenario:
I receive a request for /edit/page
Which matches /edit/*
So from this matcher, I have {1} == "page".. I want
to pass this