[
https://issues.apache.org/jira/browse/NIFI-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945184#comment-15945184
]
Mark Payne commented on NIFI-2907:
----------------------------------
Also of note - a quick glance at the PR looks fine. It does a good job of
getting rid of the ERROR logs in bootstrap.log and moves them into WARN logs in
nifi-app. The thing that we need to give consideration to is if the schema
accurately represents what we serialize. So we need to look through the
StandardFlowSerializer class and compare that with FlowConfiguration.xsd and
make sure that they align for all cases.
> Schema for flow.xml outdated
> ----------------------------
>
> Key: NIFI-2907
> URL: https://issues.apache.org/jira/browse/NIFI-2907
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: James Wing
> Priority: Minor
> Fix For: 1.2.0
>
>
> The schema that the framework uses to validate the flow.xml file is outdated.
> It does not account for the the 'template' element in the flow. As a result,
> it logs the following error on startup, within the bootstrap.log file:
> 2016-10-17 09:45:12,784 ERROR [NiFi logging handler] org.apache.nifi.StdErr
> [Error] :10:38: cvc-complex-type.2.4.a: Invalid content was found starting
> with element 'template'. One of '{processor, inputPort, outputPort, label,
> funnel, processGroup, remoteProcessGroup, connection, controllerService}' is
> expected.
> We should add the 'template' element to the schema and ensure that all other
> elements are accounted for
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
