Hi,
yes, I second Freeman. ServiceMix 3.3.2 uses Spring 2.5.6. I have
already updated SMX3 trunk to use Spring 3.0.4.RELEASE (as the
components), it will be included in the next SMX 3.3.3.
Regards
JB
On 12/23/2010 02:27 AM, Freeman Fang wrote:
Hi,
I think smx 3.3.2 core still rely on spring 2.5.6, so you can't simply
replace spring jar in <SERVICEMIX>/lib with new versions.
So you may need wait for next Apache Servicemix 3.3.3 release, or you
can build a snapshot kit from trunk[1] which already upgrade to spring
3.0.4.RELEASE.
Or you can consider to use latest release FUSE ESB 3.x(which is based on
Apache Servicemix 3.x), the latest released version is 3.5.0-fuse-00-00,
which is also spring 3 compatible.
[1]https://svn.apache.org/repos/asf/servicemix/smx3/trunk/
[2]http://repo.open.iona.com/maven2/org/apache/servicemix/apache-servicemix/3.5.0-fuse-00-00/
Freeman
On 2010-12-22, at 下午10:35, Pavel Drášil wrote:
I think I found the cause, but have no idea how to solve it.
The org.apache.servicemix.common.xbean.AbstractXBeanDeployer class
from the
servicemix-common-2010.02 library contained in the
servicemix-shared-2010.02
package calls the setValidating() method on an instance of the
org.springframework.context.support.AbstractXmlApplicationContext class.
This method was added in Spring 3.0 and does not exist in Spring 2.5. For
some reason, the spring-context-2.5.6.jar library from the
<SERVICEMIX>/lib
folder is used here instead of the spring-context-3.0.4.RELEASE.jar
library
contained in the servicemix-shared-2010.02 package.
--
View this message in context:
http://servicemix.396122.n5.nabble.com/Problem-using-2010-02-components-in-Servicemix-3-3-2-tp3315070p3315103.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
