Hi again, Here is an update on my resource binding issue:
It seems that Resource_ImplBase adds a qualified context name to the qname that is used to lookup the resource in a resource map, but the resource is registered without the context name in the key, so it isn’t found. This is a dependent inside a named aggregate, and the name of this aggregate seems to be used to form the qname, and I wonder if this also happened in UIMA 2.x. The fallback tries then to resolve the resource from a file URL, which expectedly fails in my case, so the whole resource resolution throws an exception. 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. Best, Mario On 28 Mar 2020, at 13:45 , Mario Juric <[email protected]<mailto:[email protected]>> wrote: Thanks for the quick response, Richard. I managed to build everything now, but I now seem to get resource binding failures in my pipeline. I haven’t figured what this is all about yet, but please let me know if there is something I need to know about changes in the way resource bindings works. Cheers Mario On 28 Mar 2020, at 12:41 , Richard Eckart de Castilho <[email protected]<mailto:[email protected]>> wrote: External email – Do not click links or open attachments unless you recognize the sender and know that the content is safe. On 28. Mar 2020, at 08:49, Mario Juric <[email protected]<mailto:[email protected]>> wrote: I think I figured it out. I need to use createSharedResourceDescription instead, correct? If you used public static ExternalResourceDescription createExternalResourceDescription(final String aName, Class<? extends SharedResourceObject> aInterface, String aUrl, Object... aParams) { in uimaFIT v2, then the replacement in uimaFIT v3 should be public static ExternalResourceDescription createSharedResourceDescription( String aUrl, Class<? extends SharedResourceObject> aInterface, Object... aParams) { The URI parameter has moved to the front instead. That method seems to have been there previously, but I never used it. The second signature is only present in uimaFIT v3, not in v2. The signatures and naming were changed from v2 to v3 to avoid ambiguities. Cf. https://issues.apache.org/jira/browse/UIMA-3928 Cheers, -- 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. ________________________________ 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.
