blocks|key|2818793|text|如果选项2对您来说相对容易(例如，像在后端控制器中添加一行JSON转换)，那么它可能是一项不错的投资，因为JSON在线路上更精简，客户端上的工作要少得多，而且通常是RESTful应用编程接口使用者的首选(以防有其他使用者)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2818794|最近完成了这类工作，我想说下一个最好的方法(如果选项2比较困难)是使用response和request+transformers来执行XML和JavaScript对象之间的转换，这是选项3和选项4之间的一个变体。DOMParser对象是原生代码，所以它解析XML的速度很快。将XML转换为JavaScript对象和从JavaScript对象生成XML都是非常简单的递归算法。这种方法将所有剩余的客户端代码从后端表示中解耦出来，如果您选择了选项1，情况就不同了。如果出现这样的机会，这种解耦将允许您直接使用基于JSON的RESTful接口。|offset|length|2818795|选择涉及JSON/JavaScript对象的任何选项通常涉及处理阻抗不匹配问题，如XML属性、XML集合与JS数组和XML混合内容表示。如果您的数据模型足够简单，或者您不介意接受由XML和JSON之间的开箱即用的转换器提供的解决方案(例如，冗余的对象包含、表示与元素混合的不相交文本的编号文本属性)，那么这对您来说可能不是问题。否则，在请求的两端都有必要定制转换行为的机会(尽管遗憾的是，据我所见，不是以声明的方式)。|2818796|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.angularjs.org/api/ng.$http^0|0|1G|C|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

If option 2 is relatively easy for you (like adding one-line JSON conversions in your back-end controllers, for example), then it's probably a good investment, as the JSON is leaner over the wire, far less work on the client side and generally preferred by RESTful API consumers (in case there are other consumers).

Having recently done this kind of work, I'd say the next best path (if option 2 is difficult) would be to use response and request <a href="http://docs.angularjs.org/api/ng.$http" rel="noreferrer">transformers</a> to perform conversions between your XML and JavaScript objects, which is a variation somewhere between your options 3 and 4. The DOMParser object is native code, so it parses XML plenty fast. Transforming the XML DOM to JavaScript objects and generating XML from JavaScript objects are both fairly straightforward recursive algorithms. This approach decouples all of the rest of your client-side code from the back-end representation, which would not be the case if you went with your option 1. Such decoupling would allow you to make direct use of a JSON-based RESTful interface, should such an opportunity arise.

Selecting any option that involves JSON/JavaScript objects will often involve dealing with impedance mismatch issues like XML attributes, XML collections vs. JS arrays and XML mixed content representation. If your data models are simple enough, or you don't mind living with the solutions provided by out-of-the-box transformers between XML and JSON (e.g., redundant object containment, numbered text properties to represent disjoint text mixed with elements), then this may not be an issue for you. Otherwise, there are opportunities for customizing transformation behavior at either end of the request imperatively (though sadly not declaratively, as far as I've seen).

blocks|key|2818839|text|我建议您使用一个从xml到json的转换器。这里有一个。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2818840|https://code.google.com/p/jquery-xml2json-plugin/|2818841|转换之后，您就拥有了一个普通的JS对象，您可以在其中使用普通的angular指令来解析它们，并根据需要使用它们。|2818842|entityMap|0|LINK|mutability|MUTABLE|url^0|9|8|0|0|1D|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@$9|U|A|V|1|W]]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|G]]]]

I would recommend you to have a xml to json converter. Here is one.

<a href="https://code.google.com/p/jquery-xml2json-plugin/" rel="noreferrer">https://code.google.com/p/jquery-xml2json-plugin/</a>

After the conversion, you have a normal JS object where you can use your normal angular directives to parse through them and use them as you want.

blocks|key|194289|text|我也有同样的问题。最后我做了一个小模块，把我所有的XML响应都转换成一个ng.element对象。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|194290|https://github.com/johngeorgewright/angular-xml|offset|length|194291|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1B|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

I had the same problem. Ended up making a small module to turn all my XML responses in to a ng.element object.

<a href="https://github.com/johngeorgewright/angular-xml">https://github.com/johngeorgewright/angular-xml</a>

blocks|key|196423|text|我发现x2js运行得很好：https://code.google.com/p/x2js/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|196424|客户端接受XML，不需要处理angular服务。一次简单的快速转换，您就拥有了一个mimcs文档的JSON+API。似乎解决了我遇到的所有用例。|196425|entityMap|0|LINK|mutability|MUTABLE|url|https://code.google.com/p/x2js/^0|D|V|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I'm finding x2js is working quite well: <a href="https://code.google.com/p/x2js/">https://code.google.com/p/x2js/</a>

The client takes in the XML, no need to mess with the angular services. A simple quick conversion and, voila, you have a JSON API that mimcs the XML document. Seems to take care of all the use cases I've run into.

blocks|key|3031516|text|我创建了一个名为HttpService的服务，它有一个名为getRequestedContent的函数，在这个服务中，我使用angular+http调用我的服务"http://localhost:8080/showserverstartupinfo“，它返回一个xml，如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3031517|<SERVERSTARTUPINFO>
<SERVERNAME>########</SERVERNAME>
<SERVERSTARTUPTIME>##########</SERVERSTARTUPTIME>
</SERVERSTARTUPINFO>|code-block|syntax|javascript|3031518|我解析了上面的...and，并用xml元素的内容填充了我的div。|3031519|HttpService.getRequestedContent('/showserverstartupinfo').then(
++function(content)+{
++++//successCallback
++++var+xml+=+content.data;
++++document.getElementById('serverName').innerHTML+=+
++++++++++xml.getElementsByTagName("SERVERNAME")[0].childNodes[0].nodeValue;
++},+function(data)+{
++++//errorCallback
});|3031520|HttpService(Angularjs)中的getRequestedContent函数如下：|3031521|getRequestedContent+:+function(request)+{
++var+url+=+this.getRootContextPath()+%2B+request;
++return+$http({
++++method+:+'GET',
++++url+:+url,
++++transformResponse+:+function(data)+{
++++++return+$.parseXML(data);
++++}
++});
}|3031522|entityMap|0|LINK|mutability|MUTABLE|url|http://localhost:8080/showserverstartupinfo^0|8|B|T|J|29|17|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|F|3|G|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|19|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|1A|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1B|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1C|8|@]|D|@]|E|$I|J]]|$1|S|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

I created a service named <code>HttpService</code> having a function called <code>getRequestedContent</code> in which I am using angular http call to my service "<a href="http://localhost:8080/showserverstartupinfo" rel="nofollow noreferrer">http://localhost:8080/showserverstartupinfo</a>" which returns a xml as follows:

<pre><code>&lt;SERVERSTARTUPINFO&gt;
&lt;SERVERNAME&gt;########&lt;/SERVERNAME&gt;
&lt;SERVERSTARTUPTIME&gt;##########&lt;/SERVERSTARTUPTIME&gt;
&lt;/SERVERSTARTUPINFO&gt;
</code></pre>

...and I parse the above xml and populate my div with content of xml element.

<pre><code>HttpService.getRequestedContent('/showserverstartupinfo').then(
 function(content) {
 //successCallback
 var xml = content.data;
 document.getElementById('serverName').innerHTML = 
 xml.getElementsByTagName("SERVERNAME")[0].childNodes[0].nodeValue;
 }, function(data) {
 //errorCallback
});
</code></pre>

getRequestedContent function in HttpService(Angularjs) as follows: 

<pre><code>getRequestedContent : function(request) {
 var url = this.getRootContextPath() + request;
 return $http({
 method : 'GET',
 url : url,
 transformResponse : function(data) {
 return $.parseXML(data);
 }
 });
}
</code></pre>

My company has thousands of existing xml web services and is starting to adopt AngularJs for new projects.

The tutorial over at <a href="http://angularjs.org/">http://angularjs.org/</a> uses json services exclusively. It looks like they make a service call in the controller, parse the resulting JSON, and pass the resulting object directly to the view.

What do I do with XML? I see four options:

<ol>
<li>Parse it and pass the DOM object directly to the UI(view).</li>
<li>Put a JSON wrapper around my XML services on the server side.</li>
<li>convert the DOM object to JSON with some library on the client side and convert it back when I make the post/put requests.</li>
<li>Convert the DOM object to a JavaScript object manually on the client side.</li>
</ol>

What the correct approach and why?

How to handle XML services in AngularJS?

服务器

JSON

我的公司有数千个现有的xml服务，并开始在新项目中采用AngularJs。的教程专门使用json服务。看起来它们在控制器中进行服务调用，解析生成的JSON，并将生成的对象直接传递给视图。我该如何处理XML？我看到了四个选择：解析它，并将DOM对象直接传递到UI(视图)。在服务器端对我的服务进行了JSON包装。将DOM对...

问如何在AngularJS中处理XML services？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在AngularJS中处理XML services？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在AngularJS中处理XML services？
EN