[
https://issues.apache.org/activemq/browse/SM-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61174#action_61174
]
Geert Schuring commented on SM-1970:
------------------------------------
But that means the XML can only be validated by ServiceMix, which means that
there is no way of knowing whether a config is correct until servicemix logs
errors on deploy-time, or works without logging any errors. You can't be
serious that I should manually extract all servicemix component XSD's and load
them into my IDE. That was never the intention of the spring.schemas mechanism.
See
http://static.springsource.org/spring/docs/2.0.x/reference/extensible-xml.html#extensible-xml-registration-spring-schemas
"The properties file called 'spring.schemas' contains a mapping of XML Schema
locations (referred to along with the schema declaration in XML files that use
the schema as part of the 'xsi:schemaLocation' attribute) to classpath
resources. This file is needed to prevent Spring from absolutely having to use
a default EntityResolver that requires Internet access to retrieve the schema
file."
> Schema location is incorrect for servicemix-quartz-2010.01.0-fuse-02-00.xsd
> in servicemix-quartz archetype
> ----------------------------------------------------------------------------------------------------------
>
> Key: SM-1970
> URL: https://issues.apache.org/activemq/browse/SM-1970
> Project: ServiceMix
> Issue Type: Bug
> Components: archetypes
> Affects Versions: archetypes-2010.01
> Reporter: Geert Schuring
> Assignee: Freeman Fang
>
> after project generation using the archetype, the xbean.xml contains:
> [...]
> xsi:schemaLocation="
> http://servicemix.apache.org/quartz/1.0
> http://servicemix.apache.org/schema/servicemix-quartz-2010.01.0-fuse-02-00.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd";>
> [...]
> The URL
> http://servicemix.apache.org/schema/servicemix-quartz-2010.01.0-fuse-02-00.xsd
> is unresolveable, and results in the XML editor claiming validation errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
