Richard, There is an API in UIMA for generating Analysis Engine Descriptors as well as Aggregates and Type System descriptions. I use that API to generate the xml descriptor at runtime after the configuration has been completed. I wrote my own logic to track the delegates of an Aggregate descriptor in order to propagate updates to/from delegates to allow the user to dynamically specify Analysis Engine parameters. I also merged the scale out parameters for UIMA-AS into the Analysis Engine object for ease of configuration.
In addition I wrote my own code to generate the deployment descriptor from the programmatic parameters provided. The resulting XML is what the framework uses to generate the Spring Bean file you mentioned. That being said the existing API definitely has a learning curve which was part of the motivation for creating Leo. Thanks, Thomas Ginter 801-448-7676 thomas.gin...@utah.edu > On Jul 16, 2015, at 1:51 PM, Richard Eckart de Castilho <r...@apache.org> > wrote: > > Hi Thomas, > > On 16.07.2015, at 21:42, Thomas Ginter <thomas.gin...@utah.edu> wrote: > >> Have you looked into using Leo? It allows you to programmatically create >> Analysis Engines, Aggregates, the type system, and launch everything in >> UIMA-AS without having to manage any XML descriptors at all. Furthermore it >> is available via Maven so your code can compile an run. > > Did you find an API in UIMA AS to handle the programmatic generation of > descriptors, or did you implement that yourself in Leo (as I had tried to in > DKPro Lab)? > > If I remember correctly, then UIMA AS loaded plain XML descriptor files, > transforms them to a Spring Bean file using XSLT and then used Spring to > instantiate it. But I may have missed something. > > Cheers, > > -- Richard
