Bugs item #898545, was opened at 2004-02-17 03:23
Message generated for change (Comment added) made by thompsonbry
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116035&aid=898545&group_id=16035

Category: None
Group: None
Status: Open
Resolution: None
Priority: 7
Submitted By: Bryan Thompson (thompsonbry)
Assigned to: Maarten Coene (maartenc)
Summary: elementByID does not use DTD-determined ID

Initial Comment:
The current elementByID implementation (dom4j-1.4) 
does not use information from the grammar to identify 
attributes of type "ID".  Instead, based on an 
examination of the unit test, it appears that it looks up 
an element having an attribute named "ID".  If you look 
at the test case document, you will see that it does not 
even include a DOCTYPE or XML Schema, so there is no 
way to identify which attributes are of type "ID".  
Therefore the method should fail to return an element 
for the current unit test.

----------------------------------------------------------------------

>Comment By: Bryan Thompson (thompsonbry)
Date: 2004-09-02 10:03

Message:
Logged In: YES 
user_id=916039

Hello,

I just downloaded dom4j-1.5-rc1 in order to test the 
elementByID() support.  Unfortunately, this feature is still 
broken.  Examination of the testing harness and the XML test 
document reveals that the tests do NOT test correctly for 
this feature.

ID-ness is conveyed by a DTD that identifies an attribute as 
having type "ID".  The XML test document and the test 
harness are assuming that the name of the ID-type attribute 
is "ID".  This test should be corrected so that elementByID() 
will correctly show up as a broken feature in the dom4j test 
suite.

Thanks,

-bryan

----------------------------------------------------------------------

Comment By: Bryan Thompson (thompsonbry)
Date: 2004-02-19 06:44

Message:
Logged In: YES 
user_id=916039

The attached code provided a workaround for our application 
(an XPointer Framework implementation).  Note that this code 
MUST provide caching for the AttributeDecls in order to have 
any decent response time for multiple queries.  Also, if the 
Document is not read-only, then you have to worry about 
updates made to the DocType through the dom4j interface.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116035&aid=898545&group_id=16035


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
dom4j-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-dev

Reply via email to