activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Beams (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-3723) Namespace handler not compatible with Spring 3.1 bean profiles
Date Thu, 16 Feb 2012 17:37:01 GMT


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:
>             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 ("" 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|]
> There is a test project attached to [SPR-9119|]
and - as Chris Beams writes - a test project on the SpringSource GitHub:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message