On Wed, Oct 28, 2009 at 6:31 AM, Daniel Trümper <[email protected]> wrote: > Hi again, > > after some days of testing and debugging I finally came up with the reason > for my problem. > > This is the setup I have: > > 1. A simple Analysis Engine importing a typedescriptor > 2. A Flow controller importing another typedescriptor. > 3. An Aggregate AE importing both. > > You will notice, that there now is no AE using the flow controller's types. > This is due to the fact that the aggregate in its original shape is more > complex and I only used this setup to test the AS stuff. This again is the > origin of my problem, that the type defined by the flow controller is absent > if I am deploying the aggregate asynchronously. If I deploy the aggregate > synchronously the CAS contains the flow controller's type. > > So the solution simply was to import the type in the AE descriptor. One > remark or open question at this point is if it is intentional that in the > async=false case the flow controller's type is imported in the CAS and in the > async=true case it is not? > > Anyways, problem solved. Thanks for the feedback.
You found a workaround, but I wonder if there is still a bug in UIMA-AS here. Did your Flow Controller descriptor import the types that it needed, yet the Flow Controller still got an exception trying to access them? That shouldn't be the case. It sounds like UIMA-AS is failing to add Flow Controllers' type definitions to the aggregate AE's CAS definition. Jerry, do you think that is possible? -Adam
