All geek questions in one place

API, should I return XPathNavigator or XmlDocument

I am creating a new API for an existing service. The methods in it will be called from c in XSLT as a .net extension, but I see that I need to use the same API to execute jQuery XML.net.

I was committed to writing all night best. To make it XSLT friendly, I will return the XML to the XPathNavigator object so that XSLT can work with it immediately (instead of converting it to a node installed in XSLT. But XPathNavigators make me tremble if you use them from within .net, and I would rather use an XmlDocument (or XDocument) any day over XPathNavigator.

So, choice, choice, what to return?

My current thought is to write all this to use XmlDocuments, and then write a Wrapper that XSLT will use, it will just call the main API and then generate XPathNavigator from the returned XmlDocument. Its a few more hoops to slip through, but would be the most flexible.

Any thoughts on my reasoning or if you have any better suggestions.

Greetings

Pete

+3
source share
2 answers

, XML, XmlReader XPathNavigator, XML , XmlDocument.

: XML .NET Framework (§ , XML- XML )

+4

API, XmlDocument : XmlNode : IXPathNavigable

, XslTransform , IXPathNavigable.

, , , , IXPathNavigable .

XDocument XSLT.

+2

Source: https://habr.com/ru/post/1768140/

More articles:


All Articles