You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by taftster <gi...@git.apache.org> on 2016/06/16 03:51:39 UTC

[GitHub] nifi pull request #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP pro...

Github user taftster commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/272#discussion_r67283832
  
    --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java ---
    @@ -215,14 +215,23 @@
                 .build();
     
         public static final PropertyDescriptor PROP_CONTENT_TYPE = new PropertyDescriptor.Builder()
    -        .name("Content-Type")
    -        .description("The Content-Type to specify for when content is being transmitted through a PUT or POST. "
    -            + "In the case of an empty value after evaluating an expression language expression, Content-Type defaults to " + DEFAULT_CONTENT_TYPE)
    -        .required(true)
    -        .expressionLanguageSupported(true)
    -        .defaultValue("${" + CoreAttributes.MIME_TYPE.key() + "}")
    -        .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
    -        .build();
    +            .name("Content-Type")
    +            .description("The Content-Type to specify for when content is being transmitted through a PUT or POST. "
    +                    + "In the case of an empty value after evaluating an expression language expression, Content-Type defaults to " + DEFAULT_CONTENT_TYPE)
    +            .required(true)
    +            .expressionLanguageSupported(true)
    +            .defaultValue("${" + CoreAttributes.MIME_TYPE.key() + "}")
    +            .addValidator(StandardValidators.createAttributeExpressionLanguageValidator(AttributeExpression.ResultType.STRING))
    +            .build();
    +
    --- End diff --
    
    The changes on lines 218-226 are just whitespace changes.  Can this be reverted back to the original?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---