[
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
