[
https://issues.apache.org/jira/browse/ARTEMIS-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387672#comment-16387672
]
ASF GitHub Bot commented on ARTEMIS-1731:
-----------------------------------------
Github user obfischer commented on the issue:
https://github.com/apache/activemq-artemis/pull/1933
I wouldn't change the `schemaLocation` directly as it is actual a bad
practice. Dependending on the XML processor catalog files should be used. In
most cases the API of the XML processor allows you to handle such things in a
cleaner way.
> Startup fails when XSD validation cannot access Internet
> --------------------------------------------------------
>
> Key: ARTEMIS-1731
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1731
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.5.0
> Reporter: Ilkka Virolainen
> Priority: Major
>
> After a recent change allowing splitting up the broker configuration across
> multiple files, starting Artemis fails when the server running broker has no
> Internet access. xml:specialAttrs references in artemis-configuration.xsd
> fail because the schema location http://www.w3.org/2005/08/xml.xsd is
> inaccessible. To reproduce, pull the latest master for 2.5.0-SNAPSHOT, block
> www.w3.org and try to run a broker. Including the schema in the build would
> resolve this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
