No, I can't share those because they are highly proprietary. But, they are actually irrelevant to conceptual work to be done. Which I can discuss.
I have distributed servers which pass XML strings as their messages. The servers are mostly stateless and transform an input XML into an output XML based on XSLT-scripted "business logic". The transformer is humming along fine. However, occassionally, a server needs to peek into an incoming XML request or an outgoing XML reply in order to do content-specific processing above and beyond what the XSLT can do (such as determining destinations and session management). So, rather than code up a mess of DOM traversal code, I need/want to ask an XPathEvaluator to evaluate some "peeks" into the source and output XML documents. Therefore, a string of XML arrives on a socket, I parse the XML into a XalanDocument, I (try to) peek into the request with XPathEvaluator, I get any state I need, I set XSLT stylesheet parameters, I let XalanTransformer do its transformation, I (try to) peek into reply with XPathEvaluator, I get any state I need, and I send off the reply XML to the proper socket. I have two wishes: 1. That XPath::executeMore not return a null nodeset() or, at least, that XPathEvaluator::selectNodeList not try to nodeset() on a *XObjectPtr which isn't actually a NodeRefList. 2. To have the XalanTransformer use its parseSource method to parse the input XML once for both the XPath query and then for the transform() method (rather than constructing a separate XalanDocument with the parserLiaison just for the XPath evaluator) and then use the XalanTransformer to parse the reply XML so that the post-transform XPath query can use that without having to construct a new XalanDocument for the output string. Makes sense? On Thursday 16 June 2005 10:53 am, Axel Weiß wrote: > Lonnie VanZandt wrote: > > On a related note, I see that a XalanTransformer has a method to parse > > - but not transform - an XML input into a XalanDocument. If so, and I > > don't need a mutable DOM, and I already have a XalanTransformer > > instance, then can't I use the "simpler" XalanTransformer::parseSource > > method instead of the parserLiaison technique in the SimpleXPathAPI > > and SerializeNodeSet sample examples? > > What is the intention of your doing? What are you trying to transform? > Would you allow us to see your xsl and xml files? > > Axel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
