Thanks for the response! I thought about that sort of approach, but wasn't sure it'd be much different from simply generating an xml, i.e. I'd still have to provide nodes for every conceivable permutation of data that might be requested. DOM, and especially SAX have no random-request interface whereby a requester (here, the style sheet) can ask for element X, and have it dynamically generated at that time. However it appears to me that this is exactly what XPath is designed to allow, I just can't seem to figure out how to use this mechanism to completely replace an actual source XML.
johan Tatu Saloranta wrote: > > > As far as I know, most xslt processors expect input to be accessed as an > xml tree, dom (not necessarily "the" DOM, but something similar enough). > This is generally built using a streaming interface like SAX. > So perhaps you could just implement standard DOM API? > > Or alternatively, if it's easier, SAX interface using which processors > build internal trees. > > -+ Tatu +- > -- View this message in context: http://www.nabble.com/Usage-model---no-source-XML%2C-just-api-calls-tp22264025p22270237.html Sent from the Xalan - J - Users mailing list archive at Nabble.com.
