[
https://issues.apache.org/jira/browse/XBEAN-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466774#comment-13466774
]
Claus Ibsen commented on XBEAN-227:
-----------------------------------
See the parse method
{code}
public BeanDefinition parse(Element element, ParserContext parserContext) {
this.parserContext = parserContext;
this.qnameHelper = new
XBeanQNameHelper(parserContext.getReaderContext());
BeanDefinitionHolder holder = parseBeanFromExtensionElement(element);
// Only register components: i.e. first level beans (or root element if
no <beans> element
if (element.getParentNode() == element.getOwnerDocument() ||
element.getParentNode().getParentNode() ==
element.getOwnerDocument()) {
BeanDefinitionReaderUtils.registerBeanDefinition(holder,
parserContext.getRegistry());
BeanComponentDefinition componentDefinition = new
BeanComponentDefinition(holder);
parserContext.getReaderContext().fireComponentRegistered(componentDefinition);
}
return holder.getBeanDefinition();
}
{code}
In this code it only parses the 1st level beans. And since <beans> with
profiles is often nested, then it no longer works.
> Add support for Spring 3.1 bean profiles
> ----------------------------------------
>
> Key: XBEAN-227
> URL: https://issues.apache.org/jira/browse/XBEAN-227
> Project: XBean
> Issue Type: Improvement
> Reporter: Claus Ibsen
> Priority: Critical
>
> When using the new feature of Spring 3.1 which is profiles, then the
> XBeanNamespaceHandler does not support parsing namespaces nested in <beans>
> which has a profile associated.
> See AMQ-3723.
--
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
