Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: uima-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of kottmann@gmail.com designates
 72.14.220.156 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=DP93jhVN5C7ZRKpRF5kq+A9jQ+SEr4xoJszzjlxQE0Gn6Svxs7RZmi4DL/pfR2wK+f
         aNcWpa95x1GyKiDvgGh4NOjYmul0tyl3DtjvhaXw5lqQb80adf2kSAEt5qpcMzjpFUQx
         /GAQxXDpHBSSjYG1NBYvr9+41ha4TF1NK5/4I=
Message-ID: <4AA66984.4080306@gmail.com>
Date: Tue, 08 Sep 2009 16:26:12 +0200
From: =?ISO-8859-1?Q?J=F6rn_Kottmann?= <kottmann@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: uima-user@incubator.apache.org
Subject: Re: Passing java references to a UIMAJ component
References: <6dfceae40908110721w1c746b38tad4ef2f25c58322e@mail.gmail.com>
	 <4A86B834.6000000@schor.com> <4AA6369D.1010102@gmail.com>
 <2787e08a0909080644g1b98b68cxe39790eb9c83ec89@mail.gmail.com>
In-Reply-To: <2787e08a0909080644g1b98b68cxe39790eb9c83ec89@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Adam Lally wrote:
> On Tue, Sep 8, 2009 at 6:49 AM, J�rn Kottmann<kottmann@gmail.com> wrote:
>   
>> Marshall Schor wrote:
>>     
>>> Fabio Mancinelli wrote:
>>>
>>>       
>>>> Hi everybody,
>>>>
>>>> I have a quick question about UIMAJ component initialization.
>>>>
>>>> What I would like to do is to pass a Java reference to an object that
>>>> will be used by the "business logic" of a collection reader in the
>>>> context of a CPE. Since I cannot control the instantiation of the
>>>> collection reader, I was wondering if there is a quick and clean way
>>>> to pass that object reference or if this is not impossible at all
>>>> (like I am suspecting).
>>>>
>>>>         
>>> There is no clean way to do this in general.  This is because the
>>> components in general could be running in other contexts, for instance,
>>> in a remote machine, not the same JVM, etc.
>>>
>>> There is a way to share Java objects among annotators running in the
>>> same machine, using external resources; see
>>>
>>> http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/tutorials_and_users_guides/tutorials_and_users_guides.html#ugr.tug.aae.accessing_external_resource_files
>>>
>>> While that specifically addresses creating a Java object and then
>>> "loading" it from an external file, the loading part is optional.
>>>
>>>       
>> What must be done to make the loading part optional ?
>>
>> If a resource is described without the fileResourceSpecifier element,
>> then the framework throws a NullPointerException.
>>
>> For example:
>> <externalResourceDependency>
>>  <key>searchQueryProvider</key>
>>  <interfaceName>org.apache.uima.lucas.SearchQueryProvider</interfaceName>
>> </externalResourceDependency>
>> ...
>> <externalResource>
>>  <name>SampleSearchQueryProvider</name>
>>  <implementationName>org.apache.uima.lucas.SampleSearchQueryProvider
>>  </implementationName>
>> </externalResource>
>>
>>     
>
>
> Instead of a fileResourceSpecifier you can use a customResourceSpecifier. See:
> http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.xml.component_descriptor.custom_resource_specifiers
>   

The externalResource definition now looks like this

<externalResource>
  <name>SampleSearchQueryProvider</name>
  <customResourceSpecifier>
    
<resourceClassName>org.apache.uima.lucas.SampleSearchQueryProvider</resourceClassName>
   </customResourceSpecifier>
</externalResource>

and the SampleSearchQueryProvider instance can be accessed by an 
AnalysisEngine.

Thanks for your help,
J�rn