I have a question that is the opposite of what is normally asked with regard to ? and & characters in XML documents.
I'm replacing a servlet with an XSP. This servlet generates a link where the URL includes another URL as a parameter. What the browser ends up seeing is something like this: <a href="/xxx/xxx?u=http://yyy/%3fP1=99%26P2=11&b=tt&o=qq";>click me</a> The link thus includes a parameter that is itself a URL with two parameters of it's own (this allows me to do something really cool that I won't go into). What I did was create a sitemep entry that includes the parameters from the 'outer' URL that are static. It has a generate part ike this: <map:generate src="http://xxx/xxx{requestQuery}&b=tt&o=qq"/> {requestQuery} receives the "u=http://...."; generated in my stylesheet and passed through to this sitemap match. The trouble is that the XSL file that generates the link that includes the URL parameter I want to end up in {requestQuery}, ends up "decoding" the %3f and %26 (which someone asks this list how to do almost daily). Thus the link ends up looking like this in the browser: <a href="/xxx/xxx?u=http://yyy/?P1=99&P2=11&b=tt&o=qq";>click me</a> The characters in the inner (paramter) URL are thus transformed and cause the browser to incorrectly break up the 'u' parameter. My question: How can I prevent cocoon from turning %3f into '?' and %26 into '&' ? Ideas? Thanks! Jeff Sexton The ODS Companies [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
