Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 44350 invoked from network); 10 Nov 2005 11:41:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Nov 2005 11:41:28 -0000 Received: (qmail 36822 invoked by uid 500); 10 Nov 2005 11:41:26 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 36811 invoked by uid 99); 10 Nov 2005 11:41:26 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Nov 2005 03:41:24 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 8F4AE21E for ; Thu, 10 Nov 2005 12:41:03 +0100 (CET) Message-ID: <1804215529.1131622863584.JavaMail.jira@ajax.apache.org> Date: Thu, 10 Nov 2005 12:41:03 +0100 (CET) From: "angela (JIRA)" To: jackrabbit-dev@incubator.apache.org Subject: [jira] Commented: (JCR-258) Jcr-Server Contrib: Remove JDOM dependencies In-Reply-To: <1863796984.1129814033823.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JCR-258?page=comments#action_12357213 ] angela commented on JCR-258: ---------------------------- i would like to suggest the following steps: 1) consolidate the xml serialization (e.g. by defining a common interface). currently this is not handled consistently throughout the dav-library. 2) improve distinction between objects that are created on the client side and read from the xml on the server and vice versa. currently the classes focus on the server-side only. i think this would improve the classes and make it easier to complete the original task, that originates from jdom not being backwards compatible between the final release and 0,x-beta versions. 3) replace jdom. i might be mistaken, but i got the impression that in contrast to jdom, the standard w3c-dom is not very comfortable in terms of usage. currently i'm thinking of rather using sax-events in order to write the xml to the request/response body. this would also require that no exhaustive dom-tree is created in advance (e.g. deep PROPFIND), but the multistatus xml is built but when writing the response. > Jcr-Server Contrib: Remove JDOM dependencies > -------------------------------------------- > > Key: JCR-258 > URL: http://issues.apache.org/jira/browse/JCR-258 > Project: Jackrabbit > Type: Improvement > Reporter: angela > Assignee: angela > Priority: Minor > > JDOM has been replace throught the jackrabbit project except the jcr-server contrib. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira