You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by mmitchell <mm...@navis.com> on 2006/08/29 19:15:52 UTC
spring 2.0 rc3 and xbean incompatibility
Hello,
I'm using activemq 4.1 snapshot and xbean-spring 2.5 and trying to configure
an embedded broker. It seems with the Spring 2.0 rc3 there has been another
API change. Needless to say, XBeanNamespaceHandler is incompatible. Is
anyone aware of this?
thanks, Michael
--
View this message in context: http://www.nabble.com/spring-2.0-rc3-and-xbean-incompatibility-tf2184957.html#a6043598
Sent from the ActiveMQ - User forum at Nabble.com.
Re: spring 2.0 rc3 and xbean incompatibility
Posted by mmitchell <mm...@navis.com>.
Thanks, created Jira issue XBEAN-49.
gnodet wrote:
>
> The 2.6 has just been released, so i guess it will be fixed in 2.7.
> Could you raise a JIRA on xbean, please ?
> http://issues.apache.org/jira/browse/XBEAN
>
> So, in the mean time, you should revert to spring 2.0-rc2 :(
>
> On 8/29/06, mmitchell <mm...@navis.com> wrote:
>>
>>
>> Even if I upgrade to the xbean-spring 2.6 snapshot it has the following
>> incapatibilities:
>>
>> line: 205 BeanDefinitionHolder definition =
>> parserContext.getDelegate().parseBeanDefinitionElement(element, false);
>> //
>> parseBeanDefinitionElement(Element ele, boolean b) doesn't exist in
>> spring
>> 2.0 rc3 anymore
>>
>> line: 581 parserContext.getDelegate().parseListElement(element) //
>> parseListElement(element) doesn't exist anymore
>>
>> and so on.
>>
>> --Michael
>>
>>
>>
>> gnodet wrote:
>> >
>> > Do you know what are the incompatible changes ?
>> >
>> > On 8/29/06, mmitchell <mm...@navis.com> wrote:
>> >>
>> >>
>> >> Hello,
>> >>
>> >> I'm using activemq 4.1 snapshot and xbean-spring 2.5 and trying to
>> >> configure
>> >> an embedded broker. It seems with the Spring 2.0 rc3 there has been
>> >> another
>> >> API change. Needless to say, XBeanNamespaceHandler is incompatible. Is
>> >> anyone aware of this?
>> >>
>> >> thanks, Michael
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/spring-2.0-rc3-and-xbean-incompatibility-tf2184957.html#a6043598
>> >> Sent from the ActiveMQ - User forum at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/spring-2.0-rc3-and-xbean-incompatibility-tf2184957.html#a6044151
>> Sent from the ActiveMQ - User forum at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context: http://www.nabble.com/spring-2.0-rc3-and-xbean-incompatibility-tf2184957.html#a6045290
Sent from the ActiveMQ - User forum at Nabble.com.
Re: spring 2.0 rc3 and xbean incompatibility
Posted by Guillaume Nodet <gn...@gmail.com>.
The 2.6 has just been released, so i guess it will be fixed in 2.7.
Could you raise a JIRA on xbean, please ?
http://issues.apache.org/jira/browse/XBEAN
So, in the mean time, you should revert to spring 2.0-rc2 :(
On 8/29/06, mmitchell <mm...@navis.com> wrote:
>
>
> Even if I upgrade to the xbean-spring 2.6 snapshot it has the following
> incapatibilities:
>
> line: 205 BeanDefinitionHolder definition =
> parserContext.getDelegate().parseBeanDefinitionElement(element, false); //
> parseBeanDefinitionElement(Element ele, boolean b) doesn't exist in spring
> 2.0 rc3 anymore
>
> line: 581 parserContext.getDelegate().parseListElement(element) //
> parseListElement(element) doesn't exist anymore
>
> and so on.
>
> --Michael
>
>
>
> gnodet wrote:
> >
> > Do you know what are the incompatible changes ?
> >
> > On 8/29/06, mmitchell <mm...@navis.com> wrote:
> >>
> >>
> >> Hello,
> >>
> >> I'm using activemq 4.1 snapshot and xbean-spring 2.5 and trying to
> >> configure
> >> an embedded broker. It seems with the Spring 2.0 rc3 there has been
> >> another
> >> API change. Needless to say, XBeanNamespaceHandler is incompatible. Is
> >> anyone aware of this?
> >>
> >> thanks, Michael
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/spring-2.0-rc3-and-xbean-incompatibility-tf2184957.html#a6043598
> >> Sent from the ActiveMQ - User forum at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/spring-2.0-rc3-and-xbean-incompatibility-tf2184957.html#a6044151
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: spring 2.0 rc3 and xbean incompatibility
Posted by mmitchell <mm...@navis.com>.
Even if I upgrade to the xbean-spring 2.6 snapshot it has the following
incapatibilities:
line: 205 BeanDefinitionHolder definition =
parserContext.getDelegate().parseBeanDefinitionElement(element, false); //
parseBeanDefinitionElement(Element ele, boolean b) doesn't exist in spring
2.0 rc3 anymore
line: 581 parserContext.getDelegate().parseListElement(element) //
parseListElement(element) doesn't exist anymore
and so on.
--Michael
gnodet wrote:
>
> Do you know what are the incompatible changes ?
>
> On 8/29/06, mmitchell <mm...@navis.com> wrote:
>>
>>
>> Hello,
>>
>> I'm using activemq 4.1 snapshot and xbean-spring 2.5 and trying to
>> configure
>> an embedded broker. It seems with the Spring 2.0 rc3 there has been
>> another
>> API change. Needless to say, XBeanNamespaceHandler is incompatible. Is
>> anyone aware of this?
>>
>> thanks, Michael
>> --
>> View this message in context:
>> http://www.nabble.com/spring-2.0-rc3-and-xbean-incompatibility-tf2184957.html#a6043598
>> Sent from the ActiveMQ - User forum at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context: http://www.nabble.com/spring-2.0-rc3-and-xbean-incompatibility-tf2184957.html#a6044151
Sent from the ActiveMQ - User forum at Nabble.com.
Re: spring 2.0 rc3 and xbean incompatibility
Posted by Guillaume Nodet <gn...@gmail.com>.
Do you know what are the incompatible changes ?
On 8/29/06, mmitchell <mm...@navis.com> wrote:
>
>
> Hello,
>
> I'm using activemq 4.1 snapshot and xbean-spring 2.5 and trying to
> configure
> an embedded broker. It seems with the Spring 2.0 rc3 there has been
> another
> API change. Needless to say, XBeanNamespaceHandler is incompatible. Is
> anyone aware of this?
>
> thanks, Michael
> --
> View this message in context:
> http://www.nabble.com/spring-2.0-rc3-and-xbean-incompatibility-tf2184957.html#a6043598
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet