servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geert Schuring (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (SM-1970) Schema location is incorrect for servicemix-quartz-2010.01.0-fuse-02-00.xsd in servicemix-quartz archetype
Date Thu, 12 Aug 2010 07:20:49 GMT

     [ https://issues.apache.org/activemq/browse/SM-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Geert Schuring reopened SM-1970:
--------------------------------


Thanks for commenting!

But my point was not that it didn't work in servicemix, because it does, like you describe.
My point is that XML editors can't assist me because they can't find the schema. This makes
it difficult to create configurations beyond the examples.
Eclipse for instance show a red cross icon in front of the filename because of the schema
resolution error.

I would strongly recommend to make the schema's available via URLs and to use those URLs in
the schemaLocation attribute.

> 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.


Mime
View raw message