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: =?windows-1252?Q?Erik_F=E4=DFler?= <erik.faessler@uni-jena.de>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: FeaturePath with FSArray
Message-Id: <30B8B0B6-3FB5-4A44-B873-21279B940D5B@uni-jena.de>
Date: Tue, 8 Apr 2014 17:17:49 +0200
To: user@uima.apache.org
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))

Hi all,

I have a component where a parameter is supposed to be a FeaturePath =
string, e.g.

/address/streetname

Another parameter would be the type name, e.g. =93person=94.

The component would now get an iterator over all =93person=94 instances =
in the CAS and from each person geht the name of the street he or she is =
living in.

The problem is that =93address=94 is actually an FSArray of type =
=93Address=94, i.e. one person can have multiple addresses. Each address =
has then a feature =93streetname=94
I am easily able to get feature values when there is no array involved =
or when I use built-in functions. But I can not manage to get back all =
my street names.
The code:

TypeSystem ts =3D aJCas.getTypeSystem();
Type entityType =3D ts.getType(entityTypeString);
FeaturePath fp =3D aJCas.createFeaturePath();
	=09

try {
	fp.initialize(=93/address/streetname");
	=09
	FSIterator<Annotation> entityIterator =3D =
aJCas.getAnnotationIndex(entityType).iterator();
	while (entityIterator.hasNext()) {
		Annotation entity =3D entityIterator.next();
		String streetname =3D fp.getValueAsString(entity);
		System.out.println(streetname);
	}
} catch (CASException e) {
	e.printStackTrace();
}

I get an exception saying the feature =93address=94 would be primitive. =
Isn=92t there a way to involve arrays in feature paths? I saw the =
FeatureValuePath interface in the JavaDocs and it looks like it could =
handle arrays, but it is marked deprecated and I don=92t want to write a =
component that could be non-functional in the future when the UIMA =
version is updated.

Some advice? Thank!

Regards,

Erik=