[jira] Updated: (XBEAN-88) Xbean incompatible with Spring-2.1-m2
[ https://issues.apache.org/jira/browse/XBEAN-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Sherman updated XBEAN-88: -- Affects Version/s: 3.2 3.1 I believe that this issue is present under all versions and against Spring 2.5-rc1. > Xbean incompatible with Spring-2.1-m2 > - > > Key: XBEAN-88 > URL: https://issues.apache.org/jira/browse/XBEAN-88 > Project: XBean > Issue Type: Bug >Affects Versions: 2.8, 3.0, 3.1, 3.2 >Reporter: Cameron Braid > > I've been using ActiveMQ 4.1.1 with XBean 2.8 and Spring 2.0.5 without any > issues. > After upgrading to Spring-2.1-m2, using either xbean 2.8 or 3.0, I get this > exception : > Caused by: java.lang.NoSuchMethodError: > org.springframework.beans.factory.xml.XmlReaderContext.getReader()Lorg/springframework/beans/factory/xml/XmlBeanDefinitionReader; > at > org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.loadResource(XBeanNamespaceHandler.java:818) > at > org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.findNamespaceProperties(XBeanNamespaceHandler.java:778) > at > org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parseBeanFromExtensionElement(XBeanNamespaceHandler.java:257) > at > org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:155) > at > org.apache.xbean.spring.context.v2.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:49) > at > org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1114) > at > org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1104) > ... 36 more > Spring 2.1-m2 appears to change the XmlReaderContext.getReader from > public final org.springframework.beans.factory.xml.XmlBeanDefinitionReader > getReader() > to > public final org.springframework.beans.factory.support.BeanDefinitionReader > getReader() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (XBEAN-88) Xbean incompatible with Spring-2.1-m2
[ https://issues.apache.org/jira/browse/XBEAN-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron Braid updated XBEAN-88: --- Summary: Xbean incompatible with Spring-2.1-m2 (was: Xean incompatible with Spring-2.1-m2) > Xbean incompatible with Spring-2.1-m2 > - > > Key: XBEAN-88 > URL: https://issues.apache.org/jira/browse/XBEAN-88 > Project: XBean > Issue Type: Bug >Affects Versions: 2.8, 3.0 >Reporter: Cameron Braid > > I've been using ActiveMQ 4.1.1 with XBean 2.8 and Spring 2.0.5 without any > issues. > After upgrading to Spring-2.1-m2, using either xbean 2.8 or 3.0, I get this > exception : > Caused by: java.lang.NoSuchMethodError: > org.springframework.beans.factory.xml.XmlReaderContext.getReader()Lorg/springframework/beans/factory/xml/XmlBeanDefinitionReader; > at > org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.loadResource(XBeanNamespaceHandler.java:818) > at > org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.findNamespaceProperties(XBeanNamespaceHandler.java:778) > at > org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parseBeanFromExtensionElement(XBeanNamespaceHandler.java:257) > at > org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:155) > at > org.apache.xbean.spring.context.v2.XBeanNamespaceHandler.parse(XBeanNamespaceHandler.java:49) > at > org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1114) > at > org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1104) > ... 36 more > Spring 2.1-m2 appears to change the XmlReaderContext.getReader from > public final org.springframework.beans.factory.xml.XmlBeanDefinitionReader > getReader() > to > public final org.springframework.beans.factory.support.BeanDefinitionReader > getReader() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
