We're working with the sample UIMA-AS material with the following objective:
(1) Define an Aggregate with 4 stages ('A', 'B', 'C', 'D')
(2) Remote stage 'B' via use of the RemoteAnalysisEngine element of the
deployment descriptor, with name/key of 'B'.
We have put timing messages on stdout in stage B, so we can see that it is
running on each CAS.
We are running the sample AS application with the Aggregate (1) deployed with
the -d flag.
We are running the remote 'B' in it's own cmd session on the same computer;
broker in another cmd session.
When we run this setup we see the stdout timing messages for each CAS displayed
in BOTH the main AS application's window and in remote 'B's window. This
implies/indicates that 'B' is running twice, once in the aggregate and once in
the remote.
Our interpretation of the RemoteAnalysisEngine element of the deployment
descriptor is that it should override the aggregate's in-line definition of 'B'
with the definition in the deployment descriptor and send all CAS's to remotes.
Are we understanding the architecture correctly?
Why are we seeing 'B' run twice on each CAS (embedded and remote)?
Thanks,
- Charles
_________________________________________________________________
Get more out of the Web. Learn 10 hidden secrets of Windows Live.
http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008
