Subject: [xsl] RE: Java-based XPath tool From: Dimitre Novatchev <dnovatchev@xxxxxxxxx> Date: Thu, 24 May 2001 05:26:53 -0700 (PDT) |
Try the same with the XPath Visualiser: > //operation matched both <operation> and <soap:operation> tags, when it should > only have matched the first. //operation will not match anything because of the default namespace definition -- this is exactly the same result that you'll get if you use the same XPath expression from a stylesheet. When an additional (non-nul) prefix is associated with the same namespace-uri, let's say xmlns:z="http://schemas.xmlsoap.org/wsdl/" then //z:operation returns 2 matches -- exactly as it should > //soap:operation generates an error to the effect that soap: is not a valid > namespace, even though it is correctly defined. This is processed fine by the XPath Visualiser -- one node is highlighted. The Xpath visualiser offers also a number of other features: collapsible/expandable non-leaf element nodes caching of used XPath expressions on a per file basis. User-defined xsl:variable-s cached per file User-defined xsl:key-s cached per file Distinctive hi-lighting of default/implied attribute values as inherited from a DTD (in the newest version 1.4) I welcome the arrival of a Java-based product in the XPath Visualiser category -- it certainly fills a gap -- the non-MS/IE platforms were not covered by the XPath Visualiser. Cheers, Dimitre Novatchev. __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Re:Re:How tocreate variable e, Dimitre Novatchev | Thread | [xsl] transform mixing up namespace, Huebel, David |
RE: [xsl] Java-based XPath tool, Iain W Fergusson | Date | [xsl] transform mixing up namespace, Huebel, David |
Month |