Marshall Schor wrote:
I applied this patch, and committed the changes except for 2 files
which I think are not needed:
build.xml
preferences.ini
If these should be checked in, please explain the reason. I think
they're either built by the mvn eclipse:eclipse operation or are
particular to
On 2/21/07, Michael Baessler [EMAIL PROTECTED] wrote:
Marshall Schor wrote:
In order to get this to compile properly, I had to make some import
changes, in particular, there were imports:
import com.sun.org.apache.xml.internal.serialize.OutputFormat;
import
OK. When I change to use the uima.util.XMLSerializer, this breaks the
constructors, and there are several methods that are also wrong.
Adam - I think you're the most familiar with this - could you fix up
these two classes (change the import and then fix the resulting issues):
I am working on some modifications to the XMI deserializer that will
allow the following scenario:
1) A CAS is serialized to XMI.
2) Copies of the XMI documents are sent to multiple remote services
3) Each remote service appends to the CAS (does not delete or modify
existing stuff) and responds
OK, I made the necessary changes to get it to compile. I haven't
tested it, but I believe it should work.
I does not work, the element names are not written.
The output looks in the case of the DotCorpusSerializer like
this:
?xml version=1.0 encoding=UTF-8?
=corpus/
=TypeSystem.xml/
/
I
[
https://issues.apache.org/jira/browse/UIMA-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474856
]
Eddie Epstein commented on UIMA-322:
There are two XCAS formats for the v1.x XCAS. There is the original XCAS
On 2/21/07, Jörn Kottmann [EMAIL PROTECTED] wrote:
OK, I made the necessary changes to get it to compile. I haven't
tested it, but I believe it should work.
I does not work, the element names are not written.
The output looks in the case of the DotCorpusSerializer like
this:
?xml
