I've seen JUnit tests failing in this way when Saxon9 is in the classpath. Saxon and UIMA don't appear to work together.
~Burn On Wed, Nov 23, 2016 at 1:24 PM, Oliver Ferschke <[email protected] > wrote: > Hi all, > I'm experiencing some odd behavior of the XmiCasSerializer (UIMA 2.9.0). > When I pass a CAS to the static "serialize(CAS aCAS, java.io.OutputStream > aStream)" method within our runtime environment, it produces an XMI with > XML-Elements without namespace prefixes, > e.g. > <SectionAnnotation id="124" sofa="17" begin="0" end="200" hidden="false" > ...... > instead of > <cda:SectionAnnotation xmi:id="124" sofa="17" begin="0" end="200" > hidden="false" > > This also happens if I use the non-static methods. > In a minimal example that doesn't use our pipeline deployment environment, > this does not happen. > It seems like there is something in the classpath that changes the > behavior of the serializer but I haven't been able to pinpoint what this > could be. > > Has anyone ever experienced a behavior like this or knows what else I > could look into? > > Thanks a lot. > Oliver > >
