[
https://issues.apache.org/jira/browse/UIMA-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179080#comment-13179080
]
Marshall Schor commented on UIMA-239:
-------------------------------------
The code for xml parsing and generation hints at maybe switching to JAXB at
some point. I did some internet resarch and found: JAXB is alive and well.
The APIs (but not the implementation) are in Java 5, and Java 6 includes
version 2 of the *implementation*, as well. For Jafa 5, other Apache projects
(e.g., Geronimo, and maybe Axis and CXF) have versions of the reference
implementation (under the CDDL license, I think).
So, now that JAXB implementations have reached some maturity (by being now
included in the base Java, as of Java 6, and there's a similar solution for
Java 5), I'm going to take a serious look at what this might mean. In the best
case, we would reduce our UIMA impl code base by adopting this standard, and
perhaps also get some improvements, including the handling of comments and
whitespace :-).
> Tools like the CDE which use XML parsing should preserve XML comments;
> parsers should provide access to XML comments.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-239
> URL: https://issues.apache.org/jira/browse/UIMA-239
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework, Tools
> Reporter: Marshall Schor
>
> An example of a problem which happens if this is not done: the descriptors
> that come with the UIMA toolkit have a comment that specifies the license
> information for that file. If you edit a descriptor containing such a comment
> with the CDE, it strips out all comments.
> An alternative for license info: add a new, optional element to the
> descriptor for specifying the license (but this might be ambigious as to
> what is being licensed - the descriptor file or what it refers to or ??? )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
