{5} Assigned, Active Tickets by Owner (Full Description) (8 matches)

I was working in a project using web service on rails. I had a problem with a client of this web service because It was getting the a wrong result add the application crashes.

Searching the problem I found a bug in REXML on file:

/usr/lib/ruby/1.8/rexml/encoding.rb

On line 31 with the content bellow.

raise ArgumentError?, "Bad encoding name #@encoding" unless @encoding =~ /^[\w-]+$/

My app always raise the error but when I look into the encoding variable I saw the string. "\"UTF-8\"", so the string never match with the regular expression /^[\w-]+$/

I suggest replace this line with the code:

raise ArgumentError?, "Bad encoding name #@encoding" unless @encoding.gsub('"',) =~ /^[\w-]+$/

This will enhance the XPath interpreter such that it can operate on streams.

There are, currently, the following stream parsers:

• lightparser
• pullparser
• sax2parser
• streamparser
• ultralightparser

The use case for the PullParser?, StreamParser?, and LightParser? are similar, so only the PullParser? is described.

Sample input

input = "<a><b><c id='1'/><c>x</c></b></a>"

SAX2Parser Use Case

p = SAX2Parser.new(input)
found = false
p.listen( "//c[@id='1']" ) { |uri, local, qname, attrs|
  if attrs['id'] == '1'
    found = true
  else 
    raise "Found wrong c"
  end 
}
raise "c not found" unless found

PullParser?

p = PullParser.new(input)
found = false
for event in p
  if event.matches("//c[text() == 'x']")
    if event[1]['id'].nil?
      found = true
    else
      raise "Found wrong c"
    end
  end
end
raise "c not found" unless found

Note, this was tested with Ruby 1.8.4 besides 1.8.2 but it was not a choice when I submitted this ticket.

With irb, do the following test.

% irb
irb(main):001:0> require 'rexml/document'
=> true
irb(main):002:0> REXML::Text.new("&", false, false).to_s
=> "&"
irb(main):003:0> REXML::Text.new("&notanxmlentityref;", false, false).to_s
=> "&notanxmlentityref;"

This behavior is incorrect. Since raw=false the '&' in each of these strings should be escaped but it is not in either case. The correct output should be the following.

% irb
irb(main):001:0> require 'rexml/document'
=> true
irb(main):002:0> REXML::Text.new("&", false, false).to_s
=> "&"
irb(main):003:0> REXML::Text.new("&notanxmlentityref;", false, false).to_s
=> "&notanxmlentityref;"

That way the original string is recovered (unescaped) like this: "&" -> "&" rather than this: "&" -> "&" !!! Not the original string.

If you are interested in how this problem came up I was trying to escape some C++ code that looked like this:

int *intp = &aninteger;

This should've been escaped as int *intp = &aninteger; but instead was escaped as int *intp = &aninteger; When mozilla firefox went to parse this text node produced by REXML it complained that aninteger was an undefined entity reference (the right thing for it to do in this case)

http://www.germane-software.com/software/rexml/docs/tutorial.html says: One other note: the method entity() is called when an &entity; is encountered in text, and only then..

While that behavior would be quite useful, it doesn't seem to be true. See attached example code.

As a sidenote: The PullParser? documentation refers a method called next, which should be pull.