[jira] [Commented] (OFBIZ-12039) Flexible reports use an old noNamespaceSchemaLocation

[Nicolas Malin (Jira)]

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

ASF subversion and git services commented on OFBIZ-12039:
---------------------------------------------------------

Commit 128c25294283c93f72c1a2fa8975d369a4fe3db6 in ofbiz-plugins's branch refs/heads/release17.12 from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=128c252 ]

Fixed: Flexible reports use an old noNamespaceSchemaLocation (OFBIZ-12039)

While working on using flexible reports during this discussion
(https://markmail.org/message/qgebmemkqb6ddgzw)
I found this kind of errors in log:

XmlFileLoader: File Internal Content process error. Line: 20. Error message:
TargetNamespace.2: Expecting no namespace, but the schema document has a target
 namespace of 'http://ofbiz.apache.org/Widget-Form'.

Turned out that it was due to an old use of noNamespaceSchemaLocation when
dynamically creating forms.

The fix is to use the same definition than in current forms.

Thanks: Georg Potthast for starting the discussion

# Conflicts handled by hand
# birt/src/main/java/org/apache/ofbiz/birt/BirtWorker.java
# birt/src/main/java/org/apache/ofbiz/birt/flexible/BirtServices.java

> Flexible reports use an old noNamespaceSchemaLocation
> -----------------------------------------------------
>
>                 Key: OFBIZ-12039
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12039
>             Project: OFBiz
>          Issue Type: Bug
>          Components: birt
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Major
>
> While working on using flexible reports during [this discussion|https://markmail.org/message/qgebmemkqb6ddgzw] I found these errors in log:
> {noformat}
> 2020-10-03 19:07:48,924 |jsse-nio-8443-exec-4 |UtilXml                       |E| XmlFileLoader: File Internal Content process error. Line: 20. Error message: TargetNamespace.2: Expecting no namespace, but the schema document has a target
>  namespace of 'http://ofbiz.apache.org/Widget-Form'.
> 2020-10-03 19:07:48,924 |jsse-nio-8443-exec-4 |UtilXml                       |E| XmlFileLoader: File Internal Content process error. Line: 1. Error message: cvc-elt.1.a: Cannot find the declaration of element 'forms'.
> 2020-10-03 19:07:48,926 |jsse-nio-8443-exec-4 |UtilXml                       |E| XmlFileLoader: File Internal Content process error. Line: 20. Error message: TargetNamespace.2: Expecting no namespace, but the schema document has a target
>  namespace of 'http://ofbiz.apache.org/Widget-Form'.
> 2020-10-03 19:07:48,929 |jsse-nio-8443-exec-4 |UtilXml                       |E| XmlFileLoader: File Internal Content process error. Line: 20. Error message: TargetNamespace.2: Expecting no namespace, but the schema document has a target
>  namespace of 'http://ofbiz.apache.org/Widget-Form'.
> 2020-10-03 19:07:48,931 |jsse-nio-8443-exec-4 |UtilXml                       |E| XmlFileLoader: File Internal Content process error. Line: 20. Error message: TargetNamespace.2: Expecting no namespace, but the schema document has a target
>  namespace of 'http://ofbiz.apache.org/Widget-Form'.
> 2020-10-03 19:07:48,933 |jsse-nio-8443-exec-4 |UtilXml                       |E| XmlFileLoader: File Internal Content process error. Line: 20. Error message: TargetNamespace.2: Expecting no namespace, but the schema document has a target
>  namespace of 'http://ofbiz.apache.org/Widget-Form'.
> 2020-10-03 19:07:48,935 |jsse-nio-8443-exec-4 |UtilXml                       |E| XmlFileLoader: File Internal Content process error. Line: 20. Error message: TargetNamespace.2: Expecting no namespace, but the schema document has a target
>  namespace of 'http://ofbiz.apache.org/Widget-Form'.
> {noformat}
> Turned out that it was due to an old use of noNamespaceSchemaLocation when dynamically creating forms. The fix is to use the same definition than in current forms.

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