[jira] [Commented] (OFBIZ-6807) UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with publicId [null] and the file/resource is [web-app_3_0.xsd]
[
https://issues.apache.org/jira/browse/OFBIZ-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001986#comment-17001986
]
Jacques Le Roux commented on OFBIZ-6807:
This should have been definitively fixed with OFBIZ-6993, please check...
> UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with
> publicId [null] and the file/resource is [web-app_3_0.xsd]
>
>
> Key: OFBIZ-6807
> URL: https://issues.apache.org/jira/browse/OFBIZ-6807
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
>Priority: Trivial
> Fix For: Release Branch 14.12, Release Branch 15.12, Release
> Branch 16.11
>
>
> System throws following exception on server start:
> {code}
> [java] 2016-01-16 15:04:50,942 |catalina-startup-2 |UtilXml
> |W| [UtilXml.LocalResolver.resolveEntity] could not find LOCAL
> DTD/Schema with publicId [null] and the file/resource is [web-app_3_0.xsd]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-6807) UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with publicId [null] and the file/resource is [web-app_3_0.xsd]
[
https://issues.apache.org/jira/browse/OFBIZ-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001970#comment-17001970
]
sdhalex commented on OFBIZ-6807:
Excuse me, has this bug been fixed in the newest version? Or need we still do
the same workaround to avoid this bug now ? I see OFBIZ-10718 has no results
yet. Thx. [~jleroux] [~deepak] [~paulfoxworthy]
> UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with
> publicId [null] and the file/resource is [web-app_3_0.xsd]
>
>
> Key: OFBIZ-6807
> URL: https://issues.apache.org/jira/browse/OFBIZ-6807
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
>Priority: Trivial
> Fix For: Release Branch 14.12, Release Branch 15.12, Release
> Branch 16.11
>
>
> System throws following exception on server start:
> {code}
> [java] 2016-01-16 15:04:50,942 |catalina-startup-2 |UtilXml
> |W| [UtilXml.LocalResolver.resolveEntity] could not find LOCAL
> DTD/Schema with publicId [null] and the file/resource is [web-app_3_0.xsd]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-6807) UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with publicId [null] and the file/resource is [web-app_3_0.xsd]
[
https://issues.apache.org/jira/browse/OFBIZ-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722653#comment-16722653
]
Paul Foxworthy commented on OFBIZ-6807:
---
Hi Jacques,
Yes, I agree proper use of XML namespaces should be a separate issue. The
Eclipse catalogs may not work for other IDEs, so we may need to maintain
several versions. It shouldn't be too hard because we won't be defining new XML
schemas and namespaces very often. Mostly we'd just change details within them,
and that won't affect the catalog or catalogs.
> UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with
> publicId [null] and the file/resource is [web-app_3_0.xsd]
>
>
> Key: OFBIZ-6807
> URL: https://issues.apache.org/jira/browse/OFBIZ-6807
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
>Priority: Trivial
>
> System throws following exception on server start:
> {code}
> [java] 2016-01-16 15:04:50,942 |catalina-startup-2 |UtilXml
> |W| [UtilXml.LocalResolver.resolveEntity] could not find LOCAL
> DTD/Schema with publicId [null] and the file/resource is [web-app_3_0.xsd]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-6807) UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with publicId [null] and the file/resource is [web-app_3_0.xsd]
[
https://issues.apache.org/jira/browse/OFBIZ-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722150#comment-16722150
]
Jacques Le Roux commented on OFBIZ-6807:
Hi Paul,
So we could close this issue and create one based on your comment to cleanup
things with a catalog.xlm file including for webapp.xml files?
Note that we already have
https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk/.xmlcatalog.xml
> UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with
> publicId [null] and the file/resource is [web-app_3_0.xsd]
>
>
> Key: OFBIZ-6807
> URL: https://issues.apache.org/jira/browse/OFBIZ-6807
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
>Priority: Trivial
>
> System throws following exception on server start:
> {code}
> [java] 2016-01-16 15:04:50,942 |catalina-startup-2 |UtilXml
> |W| [UtilXml.LocalResolver.resolveEntity] could not find LOCAL
> DTD/Schema with publicId [null] and the file/resource is [web-app_3_0.xsd]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-6807) UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with publicId [null] and the file/resource is [web-app_3_0.xsd]
[
https://issues.apache.org/jira/browse/OFBIZ-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15688726#comment-15688726
]
Paul Foxworthy commented on OFBIZ-6807:
---
schemaLocation and noNamespaceSchemaLocation are hacks. It is silly to expect
an XML document to know the right place for its schema. So its good that you
removed schemaLocation from the webapp files.
However, there are still thousands of noNamespaceSchemaLocation in other XML
files.
What the XML files *should* have is a namespace. Then external tools can map
from the namespace to a catalogue of schemas to validate elements within those
namespaces.
I suspect the noNamespaceSchemaLocation attributes are there because people
were used to SGML and SGML-like documents (including HTML) having a DOCTYPE
that refers to a location for a DTD. With experience, that has turned out to be
a mistake - note in HTML5 you just say "it's HTML", no mention of a DTD.
So if you're doing anything to improve XML files, I suggest you include a
namespace instead of schemaLocation and noNamespaceSchemaLocation. XML
validators and IDEs like IntelliJ IDEA and Eclipse can find the right schema
based on the namespace.
> UtilXml.LocalResolver.resolveEntity] could not find LOCAL DTD/Schema with
> publicId [null] and the file/resource is [web-app_3_0.xsd]
>
>
> Key: OFBIZ-6807
> URL: https://issues.apache.org/jira/browse/OFBIZ-6807
> Project: OFBiz
> Issue Type: Bug
>Affects Versions: Release Branch 14.12, Trunk, Release Branch 15.12
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
>Priority: Trivial
>
> System throws following exception on server start:
> {code}
> [java] 2016-01-16 15:04:50,942 |catalina-startup-2 |UtilXml
> |W| [UtilXml.LocalResolver.resolveEntity] could not find LOCAL
> DTD/Schema with publicId [null] and the file/resource is [web-app_3_0.xsd]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
