You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Chris Beams (Commented) (JIRA)" <ji...@apache.org> on 2012/02/16 18:37:01 UTC
[jira] [Commented] (AMQ-3723) Namespace handler not compatible with
Spring 3.1 bean profiles
[ https://issues.apache.org/jira/browse/AMQ-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209525#comment-13209525 ]
Chris Beams commented on AMQ-3723:
----------------------------------
To be precise, this isn't an issue with bean _profiles_, i.e. {{<beans profile="...">}}, but rather with nested {{<beans>}} elements. The implementation of {{XBeanNamespaceHandler}} explicitly rejects {{<amq:*>}} elements unless they are declared at the first level of depth in the XML document. Those within nested {{<beans>}} elements are one level deeper, and so being excluded.
> 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: Bug
> Affects Versions: 5.5.1
> Environment: JDK 1.6, Spring Framework 3.1.0.RELEASE
> Reporter: Szczepan Kuzniarz
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira