Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: <Armin.Wegner@bka.bund.de>
To: <user@uima.apache.org>
Subject: AW: DKpro StanfordNamedEntityRecognizer ClassCastException
Thread-Topic: DKpro StanfordNamedEntityRecognizer ClassCastException
Thread-Index: AQHPp0d1k+Xp6l1D70mujIw7X4/BUJuvToiA
Date: Thu, 24 Jul 2014 15:05:28 +0000
Message-ID: <A734E21E566ADB40A70F2EBC5D3C2EB01581C3BA@SWMMBX12.bk.bka.bund.de>
References: 
 <CAMofaGRah06oWUSzP-EvGtTVoAvK8qgUKnGSoB+j5CVrZHiZVg@mail.gmail.com>
 <2E3B4359-39E8-48A2-A97F-9372EAA8641F@apache.org>
 <A734E21E566ADB40A70F2EBC5D3C2EB01581C38A@SWMMBX12.bk.bka.bund.de>
 <3639B29C-9D66-436B-B7D5-6A34B6D2A852@apache.org>
In-Reply-To: <3639B29C-9D66-436B-B7D5-6A34B6D2A852@apache.org>
Accept-Language: de-DE, en-US
MIME-Version: 1.0
Content-Type: multipart/signed;
 boundary="barc11c6655cfc19c39eaf5de8fb5c8bcb5"; micalg=pgp-sha1;
 protocol="application/pgp-signature"

--barc11c6655cfc19c39eaf5de8fb5c8bcb5
Content-Language: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Richard!

It looks like your absolutely right. I have changed all JCas stuff in the c=
onsumer's resource to pure CAS and it works.

But why is JCas support not initialized? The reader calls an annotator for =
document meta data that uses JCas. It says "new DocumentMetaData(cas.getJCa=
s())" and actually is annotated in the CAS.

All annotator's descriptions are build with AnalysisEngineFactory.createEng=
ineDescription or read from an XML file. They are added to an AggregateBuil=
der. The aggregate description is given as second argument to SimplePipelin=
e.runPipeline(). The first argument is the reader's descriptions. One of th=
e ae's is the cas.getJCas() one you mentioned earlier. What am I missing? H=
as anything changed from uimaFit 2.0.0 to 2.1.0?

Cheers
Armin


-----Urspr=FCngliche Nachricht-----
Von: Richard Eckart de Castilho [mailto:rec@apache.org]=20
Gesendet: Donnerstag, 24. Juli 2014 15:59
An: user@uima.apache.org
Betreff: Re: DKpro StanfordNamedEntityRecognizer ClassCastException

Hi Armin,

the underlying problem is that you get a simple org.apache.uima.cas.impl.An=
notationImpl instead of a JCas class like de.tudarmstadt.ukp.dkpro.core.api=
.ner.type.NamedEntity. Normally a CAS that has its JCas support initialized=
 always returns JCas classes. But is is possible to work entirely without J=
Cas classes and without initializing JCas support. In such a case, all Anno=
tationFS feature structures are returned as AnnotationImpl.

I don't think this has anything to do with chaining resources. I'm pretty s=
ure it is related to how CASes are created, (de)serialized, and/or passed t=
hrough your pipeline (possibly through multipliers).

If you find out that this is not related to CAS creation/propagation, I'll =
be very curious to hear about it!

Cheers,

-- Richard

On 24.07.2014, at 15:27, Armin.Wegner@bka.bund.de wrote:

> Hello Richard!
>=20
> Your fix doesn't change anything. So I tried to narrow down the problem. =
At least, I can tell that it is not a problem specific to DKPro. I have the=
 same kind of exception when not using DKPro at all. My guess now is that i=
t maybe has something to do with chaining resources. I tried some simple ae=
s. They run fine. When I try to run components with resources of resources,=
 they fail. That's all for now. I will try to find out more and report agai=
n.
>=20
> Cheers,
> Armin


--barc11c6655cfc19c39eaf5de8fb5c8bcb5
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAABAgAGBQJT0SDFAAoJEAk50sqYef+/oNgH/RtFsUxwt1GicuWw4Aav58VC
K3eV4araBmjPHoszOtN2sZrxT4jveqXPuWNjEcBG0ykJNzMPjZKgbRwxynRLkZcB
ENyP8IimEQMZxYiD09Ecu71f3NT+9muxaRXblJsSI0ThGIWVZdwFKJ5x4FTapsjB
AgEvBkxLg0kyzERDgZf0o45iAyE3qc4g+MXF7OXA8kVOUko+4/Q8DT4EODD5phfz
Nx6YKxdghi2sJ1FY9PRrU3HbYsas7kzDa5OeGtoPZXbWFlddioBm1cNLGN9nsHQi
STssiYRfnfx+zQhcg6Rv1Kt2rthuWzg2fulaFQvlVU30i2+Fs3m+X7ICvRPOEDc=
=GrD4
-----END PGP SIGNATURE-----
--barc11c6655cfc19c39eaf5de8fb5c8bcb5--