You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2017/07/19 17:40:00 UTC

[jira] [Created] (UIMA-5500) UIMA-AS V3: Replace dd2spring with java based DD processing

Jerry Cwiklik created UIMA-5500:
-----------------------------------

             Summary: UIMA-AS V3: Replace dd2spring with java based DD processing
                 Key: UIMA-5500
                 URL: https://issues.apache.org/jira/browse/UIMA-5500
             Project: UIMA
          Issue Type: Sub-task
          Components: Async Scaleout
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
             Fix For: 3.0.0AS


Current UIMA-AS uses dd2spring to parse DD into intermediate format (Spring Context) which is than fed into Spring Framework to instantiate components of the UIMA-AS at runtime. The dd2spring uses saxon and custom xslt stylesheet to process a DD. The xslt is quite complex and difficult to maintain. The saxon library requires that the DD is provided as a fully qualified file  preventing from loading it from a classpath or datapath. 
Instead of dd2spring, the UIMA-AS can use xmlbeans to parse the DD and instantiate on object model representing it. There already exists a schema for the DD in UIMA-AS from which an object model can be generated. 
New java only code can than use the model to create components necessary to deploy UIMA-AS service. The wiring of components will be done in java instead of relying on Spring which hides much of this process. 
The removal of dd2spring is largely an internal UIMA-AS concern and user code impact of this change should be minimal. The user no longer will have to specify Saxon nor the dd2springXsltFilePath when launching or deploying a service. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)