activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3723) Namespace handler not compatible with Spring 3.1 bean profiles
Date Mon, 01 Oct 2012 12:45:07 GMT

    [ https://issues.apache.org/jira/browse/AMQ-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466763#comment-13466763
] 

Claus Ibsen commented on AMQ-3723:
----------------------------------

I have reproduced the issue. Will look into a fix. 

The 5.7 release is in progress, so scheduling this for the next release.
                
> Namespace handler not compatible with Spring 3.1 bean profiles
> --------------------------------------------------------------
>
>                 Key: AMQ-3723
>                 URL: https://issues.apache.org/jira/browse/AMQ-3723
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.5.1
>         Environment: JDK 1.6, Spring Framework 3.1.0.RELEASE
>            Reporter: Szczepan Kuzniarz
>            Assignee: Claus Ibsen
>             Fix For: 5.8.0
>
>
> I try to configure an ActiveMQ broker and a connection factory using "amq:" prefixed
tags ("http://activemq.apache.org/schema/core" namespace) placed in the Spring application
context definition. Namespaced tags placed inside a bean profile (profiles are a new feature
for Spring 3.1) are silently ignored. The same tags placed outside a profile are parsed correctly.
> It's not a bug in Spring Framework - see Chris Beams' comment to [SPR-9119|https://jira.springsource.org/browse/SPR-9119]
issue.
> There is a test project attached to [SPR-9119|https://jira.springsource.org/secure/attachment/19407/custom-namespace-test.zip]
and - as Chris Beams writes - a test project on the SpringSource GitHub: https://github.com/SpringSource/spring-framework-issues/tree/master/SPR-9119.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message