> That & does not work is clear, but I don't see any reason why & > shall not work.
No only does it not respond to anything by an actual "&" character, but the parameters are expected in a specific order.
I don't get the first part of the sentence. What I meant when saying the & should work it the fact that & is only the XML escaping for &. This means the generator does indeed send a & to the server.
The other being that the HTML Generator can handle non well formed xml, and fix it. I don't trust these systems to spit out well formed xml all the time, so that's why I'm using that one.
I see.
The Proxy Generator still won't help me get around my ampersand problem.
Which should not exist :)
Is there any way for me to use an actual & character in any block to help me get this external data? Besides making changes to, or rewriting one of those generators? I think something like this would be ideal:
<map:match pattern="hi.html">
<map:generate src="http://DOMINOSERVER/mail/username.nsf";>
<map:parameter name="Login" value=""/>
<map:parameter name="Username" value="me"/>
<map:parameter name="Password" value="Password"/>
<map:parameter name="RedirectTo" value="/mail/username.nsf/($Inbox)?ReadViewEntries"/>
</map:generate>
<map:transform src="style/xsl/process.xsl"/>
<map:serialize type="html"/>
</map:match>
This would avoid misunderstandings about & and & but not solve the problem as written above. The problem must be somewhere else. Do you have an access log for the domino server? Try to look whether the request came in correctly. You can also do debugging to Cocoon and see if the request is fired correctly.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
