[From nobody Tue Sep 7 12:01:35 2004 Return-Path: <mailman-bounces@servlets.com> Received: from servlets.kattare.com (servlets.com [69.59.195.135]) by jhunter.xquery.com (8.12.8/8.12.9) with ESMTP id i87I6Lof022308 for <jhunterp@xquery.com>; Tue, 7 Sep 2004 11:06:21 -0700 Received: from servlets.kattare.com (localhost [127.0.0.1]) by servlets.kattare.com (8.12.10/8.12.11) with ESMTP id i87IBSvf017247; Tue, 7 Sep 2004 11:11:28 -0700 Received: from mclmx2.mail.saic.com (mclmx2.mail.saic.com [149.8.64.32]) by servlets.kattare.com (8.12.10/8.12.11) with ESMTP id i87IBQ5N021499 for <jdom-interest-owner@jdom.org>; Tue, 7 Sep 2004 11:11:27 -0700 Received: from mcl-its-ieg01.mail.saic.com by mclmx2.mail.saic.com for jdom-interest-owner@jdom.org; Tue, 7 Sep 2004 14:11:12 -0400 Received: from mcl-its-exbh01.mail.saic.com ([149.8.64.11]) by mcl-its-ieg01.mail.saic.com (SAVSMTP 3.1.6.45) with SMTP id M2004090714111231212 for <jdom-interest-owner@jdom.org>; Tue, 07 Sep 2004 14:11:12 -0400 Received: by mcl-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2657.72) id <SG0A92SD>; Tue, 7 Sep 2004 14:11:12 -0400 Message-Id: <D24D16A6707B0A4B9EF084299CE99B3913A099BF@mcl-its-exs02.mail.saic.com> From: "Thompson, Bryan B." <BRYAN.B.THOMPSON@saic.com> To: jdom-interest-owner@jdom.org Subject: FW: feedback on jdom-1.0-rc1 Date: Tue, 7 Sep 2004 14:11:11 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C49506.0E1005CB" Sender: mailman-bounces@servlets.com Errors-To: mailman-bounces@servlets.com X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on xquery.xquery.com X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Spam-Level: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C49506.0E1005CB Content-Type: text/plain Hello, I appear to be unable to post, through I recently subscribed. The problem may be with my email address (thompsonbry@saic.com vs bryan.b.thompson@saic.com or some such). In anycase, I would appreciate it if you would forward this message (attached, but also inline below) along to the list. Thanks, -bryan Hello, I wanted to provide some feedback on jdom 1.0 rc1. This is my first experience with jdom. This report is based on an integration effort of an XPointer Framwork processor [1] [2] to use the jdom package. The integration took approximately one day. Outstanding points that I was happy about: - The Attribute.getAttributeType() method correctly reports ID-ness based on an internal or external subset for a validating processor and correctly reports ID-ness based on an internal subset for a non-validating processor. This made my life MUCH easier when integrating jdom into the XPointer Framwork. Things that were not so easy: - It is difficult to serialize a piece of an XML document as XML. Right now this has to be done in "user code" and the code needs to examine the specific type of Object, which may be any of several different root classes. - It is difficult to compare pieces of an XML document - only referential identify comparisons are supported in the API. While there is no cannonical XML (yet!), it would be nice to package up a utility for comparing XML fragments. Other comments: - JDOM does not expose the parsed internal or external subset. The internal subset is only exposed as a String, while the external subset is not exposed at all. It would be nice to see both the internal and external DTD subsets exposed for inspection and modification. - Attributes are not visited by recursive descent iterators, which might be nice. - There is no common base class for all objects in the document model. This means that serialization and equality methods have to be written somewhat piecemeal. I'm sure that you've considered a common root class. I'm curious why you choose to reject it for the API. Thanks, -bryan [1] http://sourceforge.net/projects/cweb [2] http://www.w3.org/TR/xptr-framework/ Bryan Thompson Systems Architect SAIC / Advanced Systems Concepts 3811 N. Fairfax Drive, Suite 850 Arlington, VA 22203 +1 703-469-3400 (office) +1 202-462-9888 (direct) thompsonbry@saic.com -----Original Message----- From: jdom-interest-bounces@servlets.com [mailto:jdom-interest-bounces@servlets.com] On Behalf Of jdom-interest-owner@servlets.com Sent: Tuesday, September 07, 2004 2:03 PM To: bryan.b.thompson@saic.com Subject: feedback on jdom-1.0-rc1 You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at jdom-interest-owner@jdom.org. ------_=_NextPart_000_01C49506.0E1005CB Content-Type: message/rfc822 Message-ID: <D24D16A6707B0A4B9EF084299CE99B3913A0998B@mcl-its-exs02.mail.saic.com> From: "Thompson, Bryan B." <BRYAN.B.THOMPSON@saic.com> To: jdom-interest@jdom.org Subject: feedback on jdom-1.0-rc1 Date: Tue, 7 Sep 2004 14:02:22 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01C49506.0E1005CB" ------_=_NextPart_002_01C49506.0E1005CB Content-Type: text/plain Hello, I wanted to provide some feedback on jdom 1.0 rc1. This is my first experience with jdom. This report is based on an integration effort of an XPointer Framwork processor [1] [2] to use the jdom package. The integration took approximately one day. Outstanding points that I was happy about: - The Attribute.getAttributeType() method correctly reports ID-ness based on an internal or external subset for a validating processor and correctly reports ID-ness based on an internal subset for a non-validating processor. This made my life MUCH easier when integrating jdom into the XPointer Framwork. Things that were not so easy: - It is difficult to serialize a piece of an XML document as XML. Right now this has to be done in "user code" and the code needs to examine the specific type of Object, which may be any of several different root classes. - It is difficult to compare pieces of an XML document - only referential identify comparisons are supported in the API. While there is no cannonical XML (yet!), it would be nice to package up a utility for comparing XML fragments. Other comments: - JDOM does not expose the parsed internal or external subset. The internal subset is only exposed as a String, while the external subset is not exposed at all. It would be nice to see both the internal and external DTD subsets exposed for inspection and modification. - Attributes are not visited by recursive descent iterators, which might be nice. - There is no common base class for all objects in the document model. This means that serialization and equality methods have to be written somewhat piecemeal. I'm sure that you've considered a common root class. I'm curious why you choose to reject it for the API. Thanks, -bryan [1] <http://sourceforge.net/projects/cweb> http://sourceforge.net/projects/cweb [2] <http://www.w3.org/TR/xptr-framework/> http://www.w3.org/TR/xptr-framework/ Bryan Thompson Systems Architect SAIC / Advanced Systems Concepts 3811 N. Fairfax Drive, Suite 850 Arlington, VA 22203 +1 703-469-3400 (office) +1 202-462-9888 (direct) <mailto:thompsonbry@saic.com> thompsonbry@saic.com ------_=_NextPart_002_01C49506.0E1005CB-- ------_=_NextPart_000_01C49506.0E1005CB-- ]