hi derek,
could you tell me please how the XSP is accessed? the problem might be that
your XSP is dealing with a different session (XSPs default to creating a new
session).
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Derek Hohls
I am not sure by what you mean "How is it accessed";
it is called by the sitemap as a generator at the start
of a match entry... in fact, the same XSP may be called
from more than one match; with different processing
and transformation taking place thereafter.
How can I avoid each XSP
