As I mentioned I can see that after fresh start jbi provider was registered
as OSGi service with InternalEndpointWrapper. When I print command
*services:list 177* (177 is PID of org.apache.servicemix.jbi.osgi bundle) I
can see it in the list:
/Apache ServiceMix :: JBI :: OSGi (177) provides:
------------------------------------------------
objectClass = org.apache.servicemix.jbi.runtime.ComponentRegistry
osgi.service.blueprint.compname = componentRegistry
service.id = 330
----
......
----
*ENDPOINT_NAME = ID:myhost-13abc443ee9-0:0*
javax.jbi.servicedesc.ServiceEndpoint =
org.apache.servicemix.common.ExternalEndpoint@5e9e6837
jbi.external = true
NAME =
{http://camel.apache.org/schema/jbi}provider:ID:myhost-13abc443ee9-0:0
objectClass = org.apache.servicemix.nmr.api.Endpoint
service.id = 429
SERVICE_NAME = {http://camel.apache.org/schema/jbi}provider
UNTARGETABLE = true/
But when I execute same command after restart I can not see my jbi provider
in the list. Is there any way to enforce registration of my jbi provider? I
tried to add this to my blueprint:
/<bean class="org.apache.servicemix.common.osgi.EndpointExporter" />/
But nothing has changed.
--
View this message in context:
http://servicemix.396122.n5.nabble.com/Can-not-call-JBI-endpoint-from-blueprint-tp5714805p5714814.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
