uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Burn Lewis <burnle...@gmail.com>
Subject Re: XmiCasSerializer omits namespace prefixes in XML elements
Date Tue, 29 Nov 2016 14:42:14 GMT
I've also seen what appear to be namespace problems with Saxon8 ...
investigating.  I haven't tried older UIMAs.

On Mon, Nov 28, 2016 at 1:31 PM, Marshall Schor <msa@schor.com> wrote:

> just to note, the Saxon incompatibilities started with Saxon 9; earlier
> versions
> I think work OK.
>
> Might be useful for a "work-around".
>
> -Marshall
>
> On 11/28/2016 10:01 AM, Oliver Ferschke wrote:
> > Hi Mashall,
> > We switched from UIMA 2.6.0 right to 2.9.0 when it came out, but I
> haven't tried this particular scenario with older UIMA versions.
> > Worth to give it a shot.
> > I can confirm that SAXON is on the classpath and it's probably not easy
> to remove since other components require it.
> > But it's good to know what the possible cause of this issue might be.
> >
> > -Oliver
> >
> > -----Original Message-----
> > From: Marshall Schor [mailto:msa@schor.com]
> > Sent: Wednesday, November 23, 2016 4:49 PM
> > To: user@uima.apache.org
> > Subject: Re: XmiCasSerializer omits namespace prefixes in XML elements
> >
> > Do you see failures in UIMA 2.9.0, but no failures for earlier versions
> of UIMA?
> > (in other words, can you tell if this is a 2.9.0 issue, or is more
> general)?
> >
> > -Marshall
> >
> >
> > On 11/23/2016 1:24 PM, Oliver Ferschke 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
> >>
> >>
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message