You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2021/07/06 18:59:00 UTC

[jira] [Commented] (DAFFODIL-1927) Ability to add new layering transformers on the fly

    [ https://issues.apache.org/jira/browse/DAFFODIL-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17375947#comment-17375947 ] 

Mike Beckerle commented on DAFFODIL-1927:
-----------------------------------------

Breakdown of this ticket to more granular work items:
 |Design| |
| |Design note (wiki) including test plan (discuss on dev mailing list)|
| |Review cycle on design and examples (which are existing layer transformers)|
|Implement & Test feature| |
| |Primary coding, PR, review, debug|
| |Convert existing layer implementations into “built-in plug-ins”|
| |Create github example showing plug-in use by a schema outside of the context of Daffodil code tree.|
|Documentation| |
| |Update design asciidoc to reflect final decisions (with review cycle)|
| |Create end-user feature documentation (with review cycle - asciidoc or wiki)|

> Ability to add new layering transformers on the fly
> ---------------------------------------------------
>
>                 Key: DAFFODIL-1927
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1927
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Back End
>    Affects Versions: 2.2.0
>            Reporter: Mike Beckerle
>            Priority: Critical
>             Fix For: 3.2.0
>
>
> Pluggable layering transforms, rather than registering them in a singleton object.
> We might want to use the java Services API for this kindof thing. Would prevent users from having to call the register function--just need to put a special file in the META-INF directory in the jar file.
> See the file LayerTransformer.scala.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)