Thanks Richard,
No hurry, I have a temporary workaround for it but I probably need to look into
this soon. I’ll keep you posted when I dig up some new findings.
Cheers
Mario
> On 24 Jun 2015, at 09:29 , Richard Eckart de Castilho wrote:
>
> Hi Mario,
>
> I'm not sure if the resource injectio
Hi Mario,
I'm not sure if the resource injection has a proper two-phase initialization
(first instantiation, then injection) or if it behaves more like a constructor
injection (injection during instantiation). I think it is the latter which
requires that there is no circular injection - but that n
Hi Richard,
Seems something still spooky with my nested resources. This time I added an
additional resource, which depends on the same shared resource as another. I
now have two different resources dependent on the same external resource but
during initialisation I get the error shown below. I
I'd say it depends on demand/pressure. Basically, we have no blockers
for a release as the uimaFIT development process is very incremental
at this time. I have gone through the issues yesterday and weeded out
what would be nice to still get in. But if somebody "urgently" needs
a release, it could p
Works nicely now, Richard. Thanks a lot :)
I will run with the 2.2.0 branch from the Git repository in the coming period
and I will report back if I stumble upon any issues.
Is there some time horizon for the final release?
Cheers
Mario
> On 24 May 2015, at 02:26 , Richard Eckart de Castilho
Ok, so for what it's worth - bindExternalResource() should also have worked
in the way that you used it and it was a bug that it didn't.
So both of these issues are sorted out now:
- https://issues.apache.org/jira/browse/UIMA-4425
- https://issues.apache.org/jira/browse/UIMA-4426
I can now run y
On 23.05.2015, at 22:45, Mario Gazzo wrote:
> Thank you, Richard. The reason I use bindExternalResource is because I have a
> light DSL layer on top where everything get’s wired together from different
> aggregate modules. This way the modules don’t need to be that tightly coupled
> up front b
Thank you, Richard. The reason I use bindExternalResource is because I have a
light DSL layer on top where everything get’s wired together from different
aggregate modules. This way the modules don’t need to be that tightly coupled
up front but I just do the binding generically right before the
Ok, so here is the analysis. There are two independent reasons why the code does
not work.
== Unexpected used of "bindExternalResource" ==
I did not foresee using "bindExternalResource" for binding
a nested resource to a resource. So instead of
resourceA =
createExternalResourceDescription(Res
Here it is once again:
import org.apache.uima.UIMAException;
import org.apache.uima.analysis_engine.AnalysisEngineDescription;
import org.apache.uima.analysis_engine.AnalysisEngineProcessException;
import org.apache.uima.analysis_engine.metadata.FixedFlow;
import org.apache.uima.analysis_engine.me
Mario, it appears as if the attachment didn't make it through. No idea
if the list filters it. I expect the code snippet is not too long,
so maybe you can paste it directly to the mail?
-- Richard
On 23.05.2015, at 11:53, Mario Gazzo wrote:
> I attached a small Java example program that reprodu
I attached a small Java example program that reproduces the problem using the
simple pipeline but the error is the same with CPE. We are still using UIMA 2.6
with uimaFIT 2.1.0 but I could reproduce it with UIMA 2.7.
You can vary the binding sequence to see how the error differs depending on
wh
Yes, I am using the uimaFIT base classes but I will try to reproduce it in a
micro sample application as soon as possible and post it here.
> On 22 May 2015, at 17:04 , Richard Eckart de Castilho wrote:
>
> I am not sure that I have ever tested nested resources on readers;
> certainly, I have n
I am not sure that I have ever tested nested resources on readers;
certainly, I have never tested them on flow controllers - only on AEs.
Anyway - are you using the uimaFIT base-classes for readers and flow
controllers - those that call ExternalResourceInitializer.initialize(...)
in their initiali
14 matches
Mail list logo
