My apologize, when I mentioned in my previous email about extension elements not having access to the XSLProcessContext I meant extension functions, which is the one we are using.
PS: I realized that maybe I should have not posted this message in the dev list. Let me know if that is the case. > -----Original Message----- > From: Yuri de Wit [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 03, 2003 11:58 AM > To: '[EMAIL PROTECTED]' > Subject: Passing context information to xalan extensions > > > All, > > What is the best approach to pass context information to > Xalan extensions? > We are looking for a way for the code executing the > transformation (creating > the transformer, sources, result, etc) to pass a reference/context to > extension elements invoked by Xalan. > > Our first thought was to set a parameter on the transformer > and get it in > the extension using the XSLTProcessorContext api. But from > what the doc > says, it is only available for extension functions not for extension > elements. > > Our second thought was to use a thread local to pass the context > information. Is it a safe assumption that the same thread invoking the > transformation will be the one invoking the extension? > > Our third thought was to explicilty set an id as a > transformer parameter and > explicitly pass it to the extension element by passing the > parameter to the > extension element in the stylesheet. (we would like to get > away from this) > > Thanks in advance, > > Yuri >
