You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2011/07/11 17:11:59 UTC
[jira] [Commented] (UIMA-2163) Extend UIMA AS to provide Deployment
Descriptor Factory
[ https://issues.apache.org/jira/browse/UIMA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063384#comment-13063384 ]
Richard Eckart de Castilho commented on UIMA-2163:
--------------------------------------------------
Is there any way uimaFIT can contribute?
> Extend UIMA AS to provide Deployment Descriptor Factory
> -------------------------------------------------------
>
> Key: UIMA-2163
> URL: https://issues.apache.org/jira/browse/UIMA-2163
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3.2AS
>
>
> UIMA AS needs a factory for creating Deployment Descriptors at runtime. This would be very useful in UIMA AS extended test suite. Currently there are 100's of static xml deployment descriptors and many of them are clones with just a few changes. Having ability to create a DD for each test will greatly reduce (if not eliminate all) xml dd's. Additional benefit can be realized by applications using UIMA AS. Such applications would be able to compose deployment descriptors (and pipelines) dynamically based on current context instead of relying on statically defined xml dd's.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (UIMA-2163) Extend UIMA AS to provide Deployment
Descriptor Factory
Posted by Jörn Kottmann <ko...@gmail.com>.
On 7/11/11 6:03 PM, Jörn Kottmann wrote:
> The configuration parameter part can done better if the code
> is part of the core framework. So working together here, would
> be a win for UIMA and uimaFIT.
Over at OpenNLP we have a lot of code which just deals with that,
I believe such a configuration framework needs to solve three issues:
- Defining the mandatory parameters, which are currently specified
in the descriptor.
This will greatly reduce the risk of running an AE with a non-compatible
descriptor. The mandatory parameter checks can do their work more
reliable.
In the current implementation an AE might need to declare a new
mandatory parameter,
but a user runs it with an old descriptor (where it is not declared),
in this case
the built-in checks cannot detect that a parameter is missing.
But when the class itself defines the mandatory parameters it will.
- It should be able to inject parameter values into instance variables.
- Type system mapping should be supported by the framework itself,
e.g. declaring new value types, which is a type system Type and Feature.
OpenNLP also needs to load resources, but this cannot be improved by
annotations,
because the initialize method needs to create a "wrapper" object per
loaded resource,
the loaded resource is hidden behind the wrapper.
For example, it declares a NameFinderModelResource, which has a method
getModel(),
this model is then used to instantiated a NameFinderME object, which is
written into
an instance field and then called from the process method.
Jörn
Re: [jira] [Commented] (UIMA-2163) Extend UIMA AS to provide Deployment
Descriptor Factory
Posted by Jörn Kottmann <ko...@gmail.com>.
On 7/11/11 5:31 PM, Thilo Götz wrote:
> +1, seems to me we already have a solution for this that has
> seen quite a bit of adoption in the community. This might be
> a good time to bring uimaFIT into the fold (if that is what
> Richard wants, that is).
If I am not mistaken uimaFIT consists basically of two parts, right?
One to create descriptors of all kinds, and one to inject
configuration parameters.
As far as I know we could take the first part and just include
it more or less.
The configuration parameter part can done better if the code
is part of the core framework. So working together here, would
be a win for UIMA and uimaFIT.
Jörn
Re: [jira] [Commented] (UIMA-2163) Extend UIMA AS to provide Deployment
Descriptor Factory
Posted by Thilo Götz <tw...@gmx.de>.
+1, seems to me we already have a solution for this that has
seen quite a bit of adoption in the community. This might be
a good time to bring uimaFIT into the fold (if that is what
Richard wants, that is).
--Thilo
On 11/07/11 17:11, Richard Eckart de Castilho (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/UIMA-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063384#comment-13063384 ]
>
> Richard Eckart de Castilho commented on UIMA-2163:
> --------------------------------------------------
>
> Is there any way uimaFIT can contribute?
>
>> Extend UIMA AS to provide Deployment Descriptor Factory
>> -------------------------------------------------------
>>
>> Key: UIMA-2163
>> URL: https://issues.apache.org/jira/browse/UIMA-2163
>> Project: UIMA
>> Issue Type: Improvement
>> Components: Async Scaleout
>> Reporter: Jerry Cwiklik
>> Assignee: Jerry Cwiklik
>> Fix For: 2.3.2AS
>>
>>
>> UIMA AS needs a factory for creating Deployment Descriptors at runtime. This would be very useful in UIMA AS extended test suite. Currently there are 100's of static xml deployment descriptors and many of them are clones with just a few changes. Having ability to create a DD for each test will greatly reduce (if not eliminate all) xml dd's. Additional benefit can be realized by applications using UIMA AS. Such applications would be able to compose deployment descriptors (and pipelines) dynamically based on current context instead of relying on statically defined xml dd's.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>