Hi,
My comment inline.
On 2010-3-17, at 上午7:15, raulvk.soa wrote:
Hi,
We are in the process of migrating from SMX 3.2.2 to SMX 3.3.1,
which comes
bundled with 2009.01 components.
During our adaptation works, we have found some 2009.01 to be faulty
(servicemix-camel and servicemix-cxf-bc), so we have upgraded them
to their
respective 2009.02 versions.
My question is: Should we be cautious with any problems or conflicts
that my
arise from the fact of having two versions of servicemix-shared in
place? (I
believe 2009.01 components need servicemix-shared-2009.01 and
2009.02 need
servicemix-shared-2009.02). Do we need to have both deployed on the
hotdeploy folder? What should the structure be?
I don't think you can use two different version servicemix-shared lib
in one smx3 container.
Could you only use the higher shared lib version?
What if we toss in some of the new 2010.01 components that are on
the verge
of being released soon?
Only use higher version for such component/shared lib should be fine,
but you should avoid using multiple version of same component/sharedlib.
And generally higher component version need higher shared lib version.
Freeman
Many thanks!
Raul.
--
View this message in context:
http://old.nabble.com/Mixing-2009.01%2C-2009.02-and-2010.01-components-tp27925875p27925875.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
