如何使ActiveResource XML解析更加一致?

时间:2011-01-27 17:55:38

标签: ruby-on-rails xml activeresource

我正在使用ActiveResource来使用Redmine提供的REST Web服务(一种错误跟踪工具)。该Web服务生成如下XML:

<custom_field name="Issue Owner" id="15">Fred Fake</custom_field> 
<custom_field name="Needs Printing" id="16">0</custom_field> 
<custom_field name="Review Assignee" id="17">Fran Fraud</custom_field> 
<custom_field name="Released On" id="20"></custom_field> 
<custom_field name="Client Facing" id="21">0</custom_field> 
<custom_field name="Type" id="22">Bug</custom_field> 
<custom_field name="QA Assignee" id="23"></custom_field> 
<custom_field name="Company Name" id="26"></custom_field> 
<custom_field name="QA Notes" id="27"></custom_field> 
<custom_field name="Failed QA Attempts" id="28">2</custom_field> 

然而,当ActiveResource解析那个,并且我遍历结果打印出来时,我得到:

Fred Fake
0
Fran Fraud
#<Redmine::Issue::CustomFields::CustomField:0x5704e95d>
0
Bug
#<Redmine::Issue::CustomFields::CustomField:0x32fd963>
#<Redmine::Issue::CustomFields::CustomField:0x3a68f437>
#<Redmine::Issue::CustomFields::CustomField:0x407964d6>
2

这是正确的,它会从带有值的任何内容中抛出所有属性信息,但保留属性信息来自空元素。

毋庸置疑,当你试图找到id 15(或其他)的值时,这会让事情变得相当困难。现在我可以通过他们的位置来引用事物,但这非常脆弱,因为这些元素将来可能会发生变化。我假设必须有一些方法让ActiveResource保留属性信息,但因为我没有做任何特别的事情。

(我的ActiveResource扩展只有五行:它扩展了ActiveResource,定义了服务的URL,用户名和密码,就是这样)。

那么,有没有人知道如何让ActiveResource不会如此奇怪地解析这个XML?

1 个答案:

答案 0 :(得分:1)

这显然是ActiveResource的一个已知问题:

https://github.com/rails/rails/issues/588

不幸的是,似乎没有任何关于它的事情。问题已经结束。如果您对此感到满意,那么用于更新ActiveResource和Hash.from_xml以保留所有属性的Rails 3代码都在下面的要点中,您可以在Redmine模块中创建一个定制版本来修复它:

https://gist.github.com/971598

<强>更新

另一种选择,因为它显示ActiveResource will not be part of Rails 4 core并将作为单独的gem分离出来,将使用替代ORM for REST API,如Her

允许您为XML使用自定义解析器。这是一个名为Redmine :: ParseXML的示例自定义解析器:

https://gist.github.com/3879418

那么你需要做的就是创建一个像config / initializers / her.rb这样的文件:

Her::API.setup :url => "https://api.xxxxx.org" do |connection|
  connection.use Faraday::Request::UrlEncoded
  connection.use Redmine::ParseXML
  connection.use Faraday::Adapter::NetHttp
end

你会得到如下的哈希:

#<Redmine::Issue(issues) issues={:attributes=>{:type=>"array", :count=>1640}, 
:issue=>{:id=>4326, 
    :project=>{:attributes=>{:name=>"Redmine", :id=>1}}, 
    :tracker=>{:attributes=>{:name=>"Feature", :id=>2}}, 
    :status=>{:attributes=>{:name=>"New", :id=>1}}, 
    :priority=>{:attributes=>{:name=>"Normal", :id=>4}}, 
    :author=>{:attributes=>{:name=>"John Smith", :id=>10106}}, 
    :category=>{:attributes=>{:name=>"Email notifications", :id=>9}}, 
    :subject=>"\n      Aggregate Multiple Issue Changes for Email Notifications\n    ",
    :description=>"\n      This is not to be confused with another useful proposed feature that\n      would do digest emails for notifications.\n    ", 
    :start_date=>"2009-12-03", 
    :due_date=>{}, 
    :done_ratio=>0, 
    :estimated_hours=>{}, 
    :custom_fields=>{
       :custom_field=>[
          {:attributes=>{:name=>"Issue Owner", :id=>15}, "value"=>"Fred Fake"},
          {:attributes=>{:name=>"Needs Printing", :id=>16}, "value"=>0}, 
          {:attributes=>{:name=>"Review Assignee", :id=>17}, "value"=>"Fran Fraud"},
          {:attributes=>{:name=>"Released On", :id=>20}}, 
          {:attributes=>{:name=>"Client Facing", :id=>21}, "value"=>0}, 
          {:attributes=>{:name=>"Type", :id=>22}, "value"=>"Bug"}, 
          {:attributes=>{:name=>"QA Assignee", :id=>23}}, 
          {:attributes=>{:name=>"Company Name", :id=>26}}, 
          {:attributes=>{:name=>"QA Notes", :id=>27}}, 
          {:attributes=>{:name=>"Failed QA Attempts", :id=>28}, "value"=>2}]},
    :created_on=>"Thu Dec 03 15:02:12 +0100 2009", 
    :updated_on=>"Sun Jan 03 12:08:41 +0100 2010"}}>
相关问题