no, it does not come from a form. users can enter it in a form and it is
stored in a databse via a webservice. then later, some other time, next
day, whenever, the user requests a page and there is a link.
<a href="catalog/update/{name}/light" witch is constructed via xml xsl
and the {name} is coming from the webservice, retreiving teh data from
the databse and giving back a xml. witch is treated with xsl into html to
get the link.
So if i can get the form to replace any special character with teh unicode
value before it is submitted to the webservice, than I would get it back
from the webservice in the correct syntax and then there would be no
problem. afterwards.
Roel Croonenberghs
Sofico Benelux
Technologiepark 1
B-9052 Zwijnaarde
www.sofico.info
Tel +32 (0)9 210 84 40
Fax +32 (0)9 210 80 41
Email [EMAIL PROTECTED]
The information in this email is intended only for the addressee(s) named
above. Access to this email by anyone else is unauthorised. If you are not
the intended recipient of this message any disclosure, copying,
distribution or any action taken in reliance on it is prohibited and may
be unlawful. Email transmission cannot be guaranteed to be secure or error
free as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. Sofico Services Benelux
does not accept liability for any losses resulting from infected email
transmissions. Please note that any views expressed in this email may be
those of the originator and do not necessarily reflect those of this
organisation.
"Jeroen Reijn" <[EMAIL PROTECTED]>
30/11/2006 15:45
Please respond to
[email protected]
To
<[email protected]>
cc
Subject
RE: special characters
Hi Roel,
how does the name get into the uri? Did you define it in the action of
your form? Otherwise it would be there as a request parameter and cocoon
would not match that by using your matcher.
I guess it's best to submit it as a request parameter and request the
parameters from your sitemap.
<map:match pattern="catalog/update">
<map:parameter name="id" value="{request-param:id}"/>
<map:parameter name="version" value="{request-param:version}"/>
Kind regards,
Jeroen Reijn
-----Original Message-----
From: Roel Croonenberghs [mailto:[EMAIL PROTECTED]
Posted At: Thursday, November 30, 2006 2:52 PM
Posted To: Cocoon User List
Conversation: special characters
Subject: Re: special characters
hello
via xml/xsl i get a link using the name files; <a
href="catalog/update/{name}/light"
<map:match pattern="catalog/update/*/**">
<map:parameter name="id" value="{1}"/>
<map:parameter name="version" value="{2}"/>
when name="test" there is no problem.
when name="test/johndoe" there is a problem, because {2} will not be
"version", but {2} will be "johndoe/light"
Roel Croonenberghs
Sofico Benelux
Technologiepark 1
B-9052 Zwijnaarde
www.sofico.info
Tel +32 (0)9 210 84 40
Fax +32 (0)9 210 80 41
Email [EMAIL PROTECTED]
The information in this email is intended only for the addressee(s) named
above. Access to this email by anyone else is unauthorised. If you are not
the intended recipient of this message any disclosure, copying,
distribution or any action taken in reliance on it is prohibited and may
be unlawful. Email transmission cannot be guaranteed to be secure or error
free as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. Sofico Services Benelux
does not accept liability for any losses resulting from infected email
transmissions. Please note that any views expressed in this email may be
those of the originator and do not necessarily reflect those of this
organisation.
Mark Lundquist <[EMAIL PROTECTED]>
30/11/2006 14:33
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: special characters
On Nov 30, 2006, at 5:08 AM, Roel Croonenberghs wrote:
> There's a problem with special characters; If the user enters a /
> in the name field, it messes up the mapping in my sitemap.
How does it do that?
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
