apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex McCullough (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-528) Output Ports Not Optional by Default During Validation
Date Thu, 22 Sep 2016 14:59:20 GMT

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

Alex McCullough commented on APEXCORE-528:
------------------------------------------

Because when no annotations are added the OutputPortMeta.portAnnotation is null, it can't
find the defaults to populate. 

Is there any issue with using reflection to populate defaults when no explicit annotation
value is provided? Then you can just have standard logic and not worry about null objects
and such.

> Output Ports Not Optional by Default During Validation
> ------------------------------------------------------
>
>                 Key: APEXCORE-528
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-528
>             Project: Apache Apex Core
>          Issue Type: Bug
>    Affects Versions: 3.4.0
>            Reporter: Alex McCullough
>            Assignee: Alex McCullough
>            Priority: Minor
>
> The 'optional' OutputPortFieldAnnotation states that the default value is true. When
you build a DAG with multiple output ports the validator throws an error telling you at least
one must be connected. To fix, you must explicitly add the annotation to all output ports
and set the value to True, which is supposed to already be the default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message