activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Endre Stølsvik (JIRA) <>
Subject [jira] Commented: (AMQ-1016) 4.1 RC1: META-INF/spring.schemas refers to building user "file:/Users/chirino/"
Date Thu, 14 Jun 2007 10:24:33 GMT


Endre Stølsvik commented on AMQ-1016:

James: It is SO AMAZINGLY REFRESHING to see you on this, and just KICKING this rather longstanding
bug outta here!

Seriously - I think this has annoyed several people, and just stagnated others. The file I'm
hosting as a "fix" to this is getting several hundred hits per week (admittedly not from that
many different hosts! But still!).

I saw you asked for ideas - is that still so? After that, you quickly added 4-5 more comments,
so I'm not sure you need me anymore? :) Do also note that I think I've stated most of my knowledge
on how this should be done on earlier comments.

> 4.1 RC1: META-INF/spring.schemas refers to building user "file:/Users/chirino/"
> -------------------------------------------------------------------------------
>                 Key: AMQ-1016
>                 URL:
>             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:
> The META-INF file spring.schemas have the single line.
> "http\://"
> 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
> refers as such:
> xmlns:amq=""
>  .. and ..
> xsi:schemaLocation=""
> 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.

View raw message