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):
casEditor/core/model/dotcorpus/DotCorpusSerializer.java
casEditor/core/uima/DocumentUimaImpl.java
thanks. -M
Adam Lally wrote:
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 com.sun.org.apache.xml.internal.serialize.XMLSerializer;
>
> which I changed to
>
> import org.apache.xml.serialize.OutputFormat;
> import org.apache.xml.serialize.XMLSerializer;
>
>
> Is this correct? The other imports seem to be particular to the sun
> jvm and not part of other jvms. They're also marked "internal" which
> makes me think they can't be safely used here.
I think using
import org.apache.xml.serialize.OutputFormat;
import org.apache.xml.serialize.XMLSerializer;
so not OK. When I remember correctly, these classes are not available
when using a plain SUN JVM. Is that possible?
Yes, that's correct, this would not work on the Sun JVM without a
separately installed Xerces.
I think we changed in the past the whole UIMA code, that we don't have
to use these classes. Is it possible to use the
org.apache.uima.util.XMLSerializer that can also write formatted output
using javax.xml.transform.Transformer with
javax.xml.transform.OutputKeys?
Yes, I think that's the right thing to do. The
org.apache.uima.util.XMLSerializer uses standard XSLT support that's
included in every JVM as part of the javax.xml.transform package, so
it is portable.
-Adam
