Re: Spring 2.0 and XBean
Just sent a mail on [email protected] On 2/21/07, Bruce Snyder <[EMAIL PROTECTED]> wrote: On 2/21/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > Good idea, I think we should do a 3.0 of xbean and > throwing away the spring 1.x support +1 on that ;-). We should ask about doing this on the geronimo-dev list just to make sure that others don't mind. Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://geronimo.apache.org/ Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Castor - http://castor.org/ -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: Spring 2.0 and XBean
On 2/21/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
Good idea, I think we should do a 3.0 of xbean and
throwing away the spring 1.x support
+1 on that ;-). We should ask about doing this on the geronimo-dev
list just to make sure that others don't mind.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
Re: Spring 2.0 and XBean
Good idea, I think we should do a 3.0 of xbean and throwing away the spring 1.x support Let me know if you need a hand with anything. -- Terry
Re: Spring 2.0 and XBean
Good idea, I think we should do a 3.0 of xbean and throwing away the spring 1.x support On 2/21/07, Terry Cox <[EMAIL PROTECTED]> wrote: > Well, I'm not sure how to solve the problem in the xbean build. Just a question, but does XBean need to evolve with backward compatability to multiple Spring versions in the trunk, or should it fork to a new release path that is maintained in parallel with the associated Spring release? -- Terry -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: Spring 2.0 and XBean
Well, I'm not sure how to solve the problem in the xbean build. Just a question, but does XBean need to evolve with backward compatability to multiple Spring versions in the trunk, or should it fork to a new release path that is maintained in parallel with the associated Spring release? -- Terry
Re: Spring 2.0 and XBean
Well, I'm not sure how to solve the problem in the xbean build.
Maven has not been designed to use more than one version of
the same dependency in the build, which leads to several problems.
One of them is that you can not downgrade a version, so you need to
use the oldest one and upgrade in other modules.
This means that xbean-spring depends on 1.2.4 or so.
When using xbean in servicemix, is usually end up adding a dependency
on spring in my pom with the correct version (2.0.1 for ex) and eventually
put it at the provided scope...
On 2/17/07, Bruce Snyder <[EMAIL PROTECTED]> wrote:
On Sat, 17 Feb 2007 16:07 + (GMT Standard Time), Terry Cox
<[EMAIL PROTECTED]> wrote:
> > Terry, what is the $xbean.version is used in the pom.xml?
>
> 2.8
>
> My code is built against the 3.1 release of ServiceMix.
>
> As an experiment, I just deleted all the 1.2.x versions of Spring from my
> repository and built ServiceMix 3.1 from source. Spring versions 1.2.4
> and 1.2.6 both re-appeared in the repository during the phase 1 build.
> Servicemix-core uses 1.2.4 and the xfire-maven-plugin uses 1.2.6.
>
> If you then check the build, you can see that the JSR-181 component build
> is over-riding the dependency management and substituting 1.2.6 instead
> of 2.0.1 so it looks as though there is some cross-contamination of
> Spring classes within ServiceMix.
Well evidently XBean 2.8 depends on Spring 1.2.4 which I don't
understand. I seem to recall that XBean used Spring 2.x so I'm rather
perplexed as to why a dep on Spring 1.2.4 is defined in the POM. I'm
sure Guillaume can shed some light on it, so let's wait for his
response.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
--
Cheers,
Guillaume Nodet
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: Spring 2.0 and XBean
On Sat, 17 Feb 2007 20:18 + (GMT Standard Time), Terry Cox
<[EMAIL PROTECTED]> wrote:
> Well evidently XBean 2.8 depends on Spring 1.2.4 which I don't
> understand. I seem to recall that XBean used Spring 2.x so I'm
> rather
> perplexed as to why a dep on Spring 1.2.4 is defined in the POM. I'm
> sure Guillaume can shed some light on it, so let's wait for his
> response.
XBean contains a series of parallel projects that seem to build support
for various specific versions of Spring, however because of this you
can't just switch the root dependency to 2.0.x as the 1.x sub-projects
won't build.
Yeah, I'm aware of this - what I'm questioning is the fact that a root
dep for Spring is defined at all. It seems to me that because each
module varies as to whether it supports Spring 1.2.x vs. 2.x then each
module should define it's own dep instead of a defining a root dep.
I'm sure Guillaume can add some clarity to this situation by
explaining the reason for the root dep on Spring 1.2.x.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
Re: Spring 2.0 and XBean
It is not possible to choose which version of spring to use. The reason is that you can't use both spring 1.x and 2.x at the same time, because there are too much classes that overlap and still are different. ServiceMix now uses spring 2, so the question is: why is there a spring 1.2.4 version in the classpath ? You need to remove it somehow. On Fri, 16 Feb 2007 22:26 + (GMT Standard Time), Terry Cox <[EMAIL PROTECTED]> wrote: This little error is causing me some fun: org.springframework.core.ConstantException: Field 'ISOLATION_' not found in class [org.springframework.transaction.TransactionDefinition] To explain, I am trying to use a POJO in a lightweight container and that POJO requires some injected dependencies that are configured using Spring 2.0. My lw-component is deployed in a service unit using the notation and the Spring 2.0 config for the dependencies is then imported within the same servicemix.xml using . This imported file is using AOP to wrap my injected bean in a transactional context and Spring is obviously getting close enough to doing this to generate the above error message. The reason for the error is that the Spring 2.0.1 version of TransactionDefinition declares ISOLATION_ but Spring 1.2.4 does not. Within ServiceMix, it appears that XBean defaults to Spring 1.2.4 classes rather than 2.0.1 and I cannot see how to prevent this. I have spent a pleasant evening trawling through the innards of XBean and can see that it acts as a pre-processor to Spring. Unfortunately, at the point at which a service unit is loaded in ServiceMix, the classpath for XBean is already defined and I can't see a way to influence the flavour of Spring to be used to process an individual service unit. I see that XBean has packages for a variety of Spring flavours, so I guess the question is "how do I make it use the one I want?". Thanks, Terry -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
