On 5 Feb., 16:58, Bjoern Hoehrmann <bjo...@hoehrmann.de> wrote:

> A way around this would be to process
> the query string on the server and include its data in the XML document,
> another would be to write an extension function that returns the base-
> URI attribute value of a Node where that is supported. If you transform
> to HTML it would also be possible to generate a script element that then
> queries the location attribute of the document and either implements
> whatever the XSLT is supposed to do, or retransforms the document while
> setting the desired parameters, where that is possible.
> --

Thanks for your ideas ... I am a little frustrated here - thought it
would be a peace of cake.

About your workarounds:

1) Including the data in the XML document.

The document is supposed to be something like a small search engine
for the data that is in the xml-file. Writing the search-string into
an xml-file wouldn't work because multiple user are accessing the
file. So they would get search-results they haven't been looking for,
right?

2) write an extension function that returns the base-URI attribute
value of a Node where that is supported:

Wow .. I don't get that one.

3) retransform:

Maybe that is a way ... is it possible to retransform a file in a
browser? Mhm ... still it would need to pass a parameter, won't it?

I read about a way to use ActiveX for transforming the php but I can't
use that because of security reasons. (ActiveX will be disabled)