Hi,
servicemix-core 3.3.1 dependency are only for test purpose.
Freeman
On 2010-3-23, at 下午3:49, Handler Michael wrote:
Sorry - I might not have stated my problem clear enough.
We are writing our own service engines. All your examples are
service-units for one of the service-engines in the smx4 components
at [1].
The rest of my mail was about those service-engines and why they all
contain a dependency to servicemix 3.3.1.
[1] https://svn.apache.org/repos/asf/servicemix/components/engines/
kind regards,
Michael
Am 23.03.2010 06:10, schrieb Freeman Fang:
On 2010-3-23, at 上午2:44, Handler Michael wrote:
ad 3.)
we would need an example for a service-engine - there are only
examples of service units and service assemblies there.
Hi,
Sorry, I don't understand what you mean by "we would need an
example for a service-engine", could you please clarify?
The service unit must belong to a binding component or a service
engine, this the way how to use JBI component (BC or SE).
Freeman
I have taken a look into your core service-engines like servicemix-
bean etc. I guess these are good examples for service-engines.?
But you keep the dependency to ServiceMix 3 (servicemix-core) in
all of them - for testing purposes as it seems. Is this dependency
to the old version mandatory for all service engines? We tried to
remove the dependency to servicemix-core in our components to make
a clean migration without dependencies to the old version, but
this broke the maven xbean plugin (strange error message stating
something like "check these realms" with a list of URLs). Is there
an example for a service-engine without a dependency to components
from the old version?
kind regards,
michael
Am 22.03.2010 09:47, schrieb Freeman Fang:
Hi,
My comment inline
On 2010-3-22, at 下午4:21, Handler Michael wrote:
Hi!
Our project (openengsb.org) is currently migrating from
ServiceMix 3.3.1 to ServiceMix 4.1.0-snapshot (we decided to
skip ServiceMix 4.0.0).
The snapshot we used was built on 2010-03-16.
We will continue to use the JBI standard and the JBI style
packaging.
Unfortunately the documentation is very thin and leaves many
questions open - here are the most basic ones:
1.) Which dependencies are needed for developing JBI service-
engines (dependencies to the NMR, the JBI compability layer,
etc)? So the question is basically: Which components take the
part of servicemix-core now?
It's the bundles in jbi feature.
2.) Are there new versions of the maven plugins? We used
jbi:projectDeploy until now, which works fine for Servicemix 3
and 4.0.0 but does not work for ServiceMix 4.1.0 (Error
accessing ServiceMix administation)?
I think this comes from we use user/pass as karaf/karaf now
instead of smx/smx, we may need update the jbi maven plugin to
use smx4 side ant task, could you please raise a jira ticket for
this issue.
And for now just copy your SA to the $SMX_HOME/deploy folder
directly, or use osgi:install from shell which demostrated by the
cxf-wsdl-first/bridge/camel examples
3.) Are there any examples for JBI style projects in ServiceMix
4.1.0?
Yeah, please take a look at cxf-wsdl-first/bridge/camel examples
shipped with kit.
Freeman
These questions are only the tip of the iceberg - but it would
help us a great deal if you could answer them.
kind regards,
Michael Handler
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
