Issue Details (XML | Word | Printable)

Key: XERCESJ-1044
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Michael Glavassevich
Reporter: Eric Isakson
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Xerces2-J

Scoped namespace bindings not looked up properly

Created: 15/Feb/05 02:47 AM   Updated: 17/Feb/05 03:12 PM
Return to search
Component/s: XInclude 1.0
Affects Version/s: 2.6.2
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments:
  Size
File Licensed for inclusion in ASF works multipleScopeNamespaceProblemFix.patch.diff 2005-02-15 02:50 AM Eric Isakson 0.9 kB
File Licensed for inclusion in ASF works multipleScopeNamespaceProblemTest.patch.diff 2005-02-15 02:50 AM Eric Isakson 3 kB

Resolution Date: 17/Feb/05 03:12 PM


 Description  « Hide
When processing nested xincluded content which has some context other 0, namepace lookup is incorrect which results in fatal errors during a parse like:

The prefix "xi" for element "xi:include" is not bound.

I'm attaching a patch for a new test case of xinclude.Test which demonstrates this problem and another patch which fixes it.


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Eric Isakson added a comment - 15/Feb/05 02:50 AM
patch to the tests directory with a new test which demonstrates the reported problem.

Eric Isakson added a comment - 15/Feb/05 02:50 AM
patch against src which fixes the reported problem

Eric Isakson added a comment - 15/Feb/05 03:01 AM
as a work around in 2.6.2 and earlier versions, you can just declare the xinclude namespace on your root element.

Michael Glavassevich added a comment - 16/Feb/05 04:56 AM
Hello Eric, I could not find a Contributor License Agreement (CLA) on file [1] for you. Could you please answer the contributor questions as defined by section 7.3 of the Xerces Charter, available here [2]. We require this information to accept bug fixes from individuals who have not signed a CLA.

Sorry for the hassle. The questions/answers can just be added to this bug report.

[1] http://www.apache.org/~jim/committers.html
[2] http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=xerces-j-dev@xml.apache.org&msgNo=4770

Eric Isakson added a comment - 17/Feb/05 03:39 AM
a) Name and employer
Eric Isakson
SAS Institute Inc., Cary, NC 27513
b) Are you the author of the code being conributed?
Yes
c) Do you have the right to grant the copyright and patent
   licenses for the contribution that are set forth in the ASF v.2.0
   license (http://www.apache.org/licenses/LICENSE-2.0)?
Yes
d) Does your employer have any rights to code that you have
   written, for example, through your contract for employment? If
   so, has your employer given you permission to contribute the code
   on its behalf or waived its rights in the code?
Yes and Yes
e) Are you aware of any third-party licenses or other
   restrictions (such as related patents or trademarks) that could
   apply to your contribution? If so, what are they?
No

Michael Glavassevich added a comment - 17/Feb/05 03:12 PM
Thanks Eric. I've committed your fix to CVS. There were similar problems with three other methods. I've fixed those as well.