Yeah I received that same error. I guess I should have posted all my findings
after I got the SM stuff working in OpenESB.
The problem probably is that your Service Units don't contain a jbi.xml.
According to the spec, this is required. However SM doesn't require it.
There maven2 jbi plugin I think creates one automatically. But since we are
on maven 1.x, we didn't have one either.
The jbi.xml needs to contain a provides/consumes tags.
Here is an example.
<?xml version="1.0" encoding="UTF-8"?>
<jbi version="1.0"
xmlns="http://java.sun.com/xml/ns/jbi";
xmlns:jbi="http://java.sun.com/xml/ns/jbi";
xmlns:ns1="http://nettoolkit.gestalt.com/httpeip";>
<!-- Service Unit Descriptor required by Spec (see 6.3.4) -->
<!-- However it seems only needed for tooling -->
<!-- Contents are not used at runtime by container -->
<!-- Consequently for now just put place holder information -->
<services binding-component="false">
<provides interface-name="ns1:HttProxySa" service-name="ns1:HttProxySa"
endpoint-name="HttProxySa"/>
</services>
</jbi>
--
View this message in context:
http://www.nabble.com/ServiceMix-in-other-JBI-Containers-tf3188098s12049.html#a8925196
Sent from the ServiceMix - User mailing list archive at Nabble.com.
