Hi again,

I forgot to cleanup the imports in my example, so I just post a new version to 
avoid any trouble related to this.

Cheers
Mario




On 28 Mar 2020, at 17:08 , Mario Juric 
<[email protected]<mailto:[email protected]>> wrote:

Hi,

Attached is a simple example that works with uimaj-core 2.10.4 and uimaFit 
2.4.0. It fails with uimaj-core 3.1.1 and uimaFit 3.0.0, but you will have to 
comment out the line with the deprecated createExternalResourceDescription and 
then comment in the line with the createSharedResourceDescription to make it 
compile with uimaFit 3.

I can see in 
org.apache.uima.resource.impl.ResourceManager_impl#resolveAndValidateResourceDependencies
 that the mResourceMap keys is different when running with the two version. It 
appears that the map is not constructed with the proper qualified names in 3.0, 
and I am not sure if I am doing anything wrong here, which just previously 
happened to work.

Thanks :)

Cheers
Mario




> On 28 Mar 2020, at 14:20 , Mario Juric 
> <[email protected]<mailto:[email protected]>> wrote:
>
> I’ll try to do it ASAP, but I am not sure when I will be able to. I’ll stay 
> in touch. Thanks :)
>
> Best
> Mario
>
>
> On 28 Mar 2020, at 14:11 , Richard Eckart de Castilho 
> <[email protected]<mailto:[email protected]><mailto:[email protected]>> wrote:
>
>
> On 28. Mar 2020, at 14:07, Mario Juric 
> <[email protected]<mailto:[email protected]><mailto:[email protected]>>
>  wrote:
>
> I am now wondering what to do about this, because this resources is used in 
> many different contexts, and I am not really interested in binding it to all 
> of them individually, since this would make our pipeline more fragile to 
> changes.
>
> Can you produce a small unit test showcasing the problem?
>
> -- Richard
>
>
>




________________________________
Disclaimer:
This email and any files transmitted with it are confidential and directed 
solely for the use of the intended addressee or addressees and may contain 
information that is legally privileged, confidential, and exempt from 
disclosure. If you have received this email in error, please notify the sender 
by telephone, fax, or return email and immediately delete this email and any 
files transmitted along with it. Unintended recipients are not authorized to 
disclose, disseminate, distribute, copy or take any action in reliance on 
information contained in this email and/or any files attached thereto, in any 
manner other than to notify the sender; any unauthorized use is subject to 
legal prosecution.

Reply via email to