The smx components are JBI AND OSGi compliants. You can deploy it as a
bundle and use it via the service locator or the EndpointExporter. I
made a talk on this during the latest fuse community day. I will
provide the slideshow.
Anyway you use other bundles directly: cxf, camel, pax-web, etc. But
the smx components features are specific (wsdl support, multiple
operations, etc).
Regards
JB
On 6 janv. 2010, at 17:29, Raphaël Delaporte <[email protected]
m> wrote:
Ok, I agree JBI has nothing to do with OSGi.
Therefore, are there new SM components that are fully OSGi ?
Thanks.
Raphaël
2010/1/6 Ryan Moquin <[email protected]>
I actually ran into several backwards compatibility issues with SMX
4 when
deploying SAs that work on SMX3. I also ran into several classloader
issues
that don't exist in SMX3 (this is a common problem with OSGI is
appears).
One last thing, is that I have problems with SMX4 reliably
deploying my
SMX3
JBI components. It seems to randomly not deploy certain components
when
started up. I'd have to start it several times before all my
components
would appear. I ended up just moving back to SMX3 until SMX4
stabilizes
some more. Some of our other projects had the same issues with
SMX4 and
moved back to SMX3. The unfortunate thing is that I can't create a
simple
test case to illustrate these problems since I can't figured out
why SMX4
deploys our JBI components so indeterministically, but SMX3 always
deploys
then without issues.
Hopefully this helps a little. If you go with OSGI, hopefully you
will
avoid the issues I mentioned above.
Ryan
2010/1/6 Raphaël Delaporte <[email protected]>
Ok, I think I'm a bite confused ...
Where are the new OSGi components (or I think we call it bundle) ?
Is it possible to use only OSGi (and just forget and throw away
JBI) in
the
SM4 version ?
In a pure OSGi environnement, there is no more SU/SA ? just some
bundles
?
This was a little classpath issue. In my xbean.xml file, I use the
xmlns:context="http://www.springframework.org/schema/context";
namespace.
In
SM3, I don't need to add lib/spring-context.jar to the SU.jar. In
SM4, I
need to include the jar.
Thanks for your time !
Raphaël.
Le 6 janvier 2010 16:56, Grégory Le Bonniec <
[email protected]>
a
écrit :
So if I understand, your advice is to use OSGi components.
Is there a OSGi component collection available (like for JBI : cxf,
file
...) ?
Regards
Greg
2010/1/6 Jean-Baptiste Onofré <[email protected]>
Hi,
it's already the case, the JBI components are shared between
SMX3 and
SMX4.
Normally, you can deploy directly your SA in SMX4. What issue
had you
?
Concerning SMX4, the JBI support is mainly for backward
compatibility.
For new users, it's better to directly use OSGi and you can use
the
EndpointExport to use JBI components from your OSGi bundles.
Regards
JB
Raphaël Delaporte wrote:
Thanks.
Is it planned to migrate all the components from JBI to OSGi ?
There is something which afraid me. I just find very few
documentation
about
SM4.
And I've tried to run some SA which are working on SM3 but are
not
working
on SM4 (missing jar files from classpath for example).
An other question :
Does ServiceMix4 support JBI only for backward compatibility ?
Or is it a real foundation for this version ?
Because it seems you encourage us to use OSGi, and not JBI.
Thanks.
Raphaël
2010/1/6 Jean-Baptiste Onofré <[email protected]>
FYI,
We are working on a new homepage to give more visibility to
smx4:
http://servicemix.apache.org/home2
Regards
JB
-----Original Message-----
From: Raphaël Delaporte <[email protected]>
Date: Wed, 6 Jan 2010 15:42:49
To: <[email protected]>
Subject: ServiceMix 3 or 4 ?
Hi all,
I'm wondering which version of ServiceMix I should use (SM3 or
SM4)
to
start
new project for production.
I know the SM3 version is mature enough, has good examples, and
stable.
I guess the SM4 version is maybe a bit young. Very few examples,
small
doc...
For instance, the web home page of the SM project is for SM3,
not
SM4.
Am I wrong ? What are your opinions ?
Thanks for your replies.
Raphaël.
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
[email protected]
PGP : 17D4F086
