Hi Joerg,
hmm... i create the session after a succesfull login, this is based on the session authentication sample.
...
and in the sitemap i pass the session parameter (<map:parameter name="Username" value="{session-attr:Username}"/>) in every <map:transform> to access them in xslt.
so when i call (http://localhost:8888/api/result.xsp) the xsp-file can access the session-attribute... but when i include this xsp-file in xslt (with document() ) i have the problem.
I guess you missed my point. If you access http://localhost:8888/api/result.xsp from browser you have a session (either cookie or URL rewriting). If the XSLT accesses http://localhost:8888/api/result.xsp via document() there is no session (or better said not the session you expect to be there as you can't refer to the cookie). You have created a completely new session object as you will access the page from a completely different browser.
Therefore I suggested you to access the result.xsp not via http (this includes also much more overhead!), but using cocoon: pseudo protocol, which causes just an internal request. So you have still the same request object and also the session object.
Or did I miss your point?
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
