activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1016) 4.1 RC1: META-INF/spring.schemas refers to building user "file:/Users/chirino/"
Date Thu, 14 Jun 2007 11:06:33 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39399
] 

James Strachan commented on AMQ-1016:
-------------------------------------

Hey Endre

I think we're all on the same page; we all want to see an end to all these spring XML related
bugs, issues and discussions :)

I think I'm getting to the bottom of understanding this; apart from the various bugs mentioned
above that are now resolved, I think a misunderstanding of the role of the spring.schemas
file has caused some confusion & blind alleys.
To be fair quite a few folks dived in and tried to fix the various issues in this whole Spring
XML namespaces thing; it turned out there was quite a few things going wrong etc.

I think we're getting closer now.

trunk has a test case Spring2XmlNamespacesTest which uses this spring-embedded-xbean.xml
which at the time of writing looks like this...

{code}
<beans 
  xmlns="http://www.springframework.org/schema/beans" 
  xmlns:amq="http://activemq.org/config/1.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
  http://activemq.org/config/1.0 http://activemq.apache.org/snapshot-schema/activemq-core-5.0-SNAPSHOT.xsd">
{code}

which works fine. Then there's Spring2XmlNamespacesWithoutRemoteSchemaTest which uses spring-embedded-xbean-noversion.xml
which uses an XSD location that doesn't actually exist (rather like in spring using
http://www.springframework.org/schema/beans/spring-beans.xsd without using the 2.0 version)

{code}
<beans 
  xmlns="http://www.springframework.org/schema/beans" 
  xmlns:amq="http://activemq.org/config/1.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
  http://activemq.org/config/1.0 http://activemq.apache.org/schema/activemq-core.xsd">
{code}

this test case works too - showing that the spring.schemas is indeed finding the local activemq.xsd
file.

> 4.1 RC1: META-INF/spring.schemas refers to building user "file:/Users/chirino/"
> -------------------------------------------------------------------------------
>
>                 Key: AMQ-1016
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1016
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.1.0
>         Environment: n/a
>            Reporter: Endre StĂžlsvik
>            Assignee: Adrian Co
>            Priority: Minor
>             Fix For: 5.0.0
>
>
> Referring to the 4.1 RC1 posted by Hiram Chirino  Oct 06, here:
>   http://www.nabble.com/ActiveMQ-4.1-RC-1-tf2397970.html#a6686974
> The META-INF file spring.schemas have the single line.
> "http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd"
> Notice "file:/" and "Users/chirino". Referring to org.springframework.beans.factory.xml.PluggableSchemaResolver's
javadoc: "schema-location should also be a schema file in the classpath", and that no-one
can tell what structure I will have on my fs, this must be wrong. In addition, I most probably
won't have a user name "chirino".
> PS: In addition, the doc at
>   http://www.activemq.org/site/how-do-i-embed-a-broker-inside-a-connection.html
> refers as such:
> xmlns:amq="http://activemq.org/config/1.0"
>  .. and ..
> xsi:schemaLocation="http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd"
> Wouldn't it be nice if this was put at a better place than such a snapshot-build URI?
It could be put where it will reside when 4.1 actually is out, w/o anyone being to angry about
changes during the finalization period, I personally believe.

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