Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of gcjau-user-2@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: users@activemq.apache.org
From: Geoffrey De Smet <ge0ffrey.spam@gmail.com>
Subject: Re: Is there a patched version of activemq for spring (AMQ-1016)?
Date: Thu, 22 Mar 2007 14:36:45 +0100
Lines: 38
Message-ID: <etu0q1$54h$1@sea.gmane.org>
References: <etrlvl$2nf$1@sea.gmane.org> <4602797F.4070101@alewando.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
In-Reply-To: <4602797F.4070101@alewando.com>
Sender: news <news@sea.gmane.org>

My xsd is a copy from

http://picorg.net/schema/activemq-4.1-working-V4.2.xsd

Where in my jar should I drop it? In the META-INF directory?

With kind regards,
Geoffrey De Smet

Adam Lewandowski schreef:
> Geoffrey De Smet wrote:
>> AMQ-1016 is blocking our spring-based application.
>> So far we've used this stopgap in development:
>> xsi:schemaLocation="http://www.springframework.org/schema/beans 
>> http://www.springframework.org/schema/beans/spring-beans.xsd
>>   http://activemq.org/config/1.0 
>> http://mydomain.com/schema/activemq-4.1-working-V4.2.xsd"
> If you create your own META-INF/spring.schemas file and include it in 
> your application's classpath Spring's entity resolver will be able to 
> find the schema locally, as long as the system id ends in '.xsd' (yours 
> does). Using your example above, the spring.schemas file would read:
> 
> http\://mydomain.com/schema/activemq-4.1-working-V4.2.xsd=activemq.xsd
> 
> This will cause the entity resolver to look for a 'activemq.xsd' file on 
> the classpath. In the 4.1 release, this file is included in the 
> distributed jar file so it won't go out to find the file over the 
> network. However, I've not been able to use the included schema file due 
> to validation problems. Your mileage may vary, but I couldn't even get 
> the example from the wiki to work with the included schema. I was able 
> to hack on the schema to make it work, but I've decided to hold off on 
> using the Spring schema support for now until it's usable out of the box.
> See the thread at 
> http://www.nabble.com/Spring-2.0-schema-support-tf3411001s2354.html for 
> more details.
> 
> Adam Lewandowski
>