-
1. Re: "No component found" Issue in 4.3.0-fuse-03-00
Hi,
Please ensure you already install camel-restlet feature.
Freeman
-
-
3. Re: "No component found" Issue in 4.3.0-fuse-03-00
Since I can't see the attached file for some reason, let me paste the two files here.
SampleRouteBuilder.java
package br.eti.fernandoribeiro.sample;
import org.apache.camel.builder.RouteBuilder;
public final class SampleRouteBuilder extends RouteBuilder {
@Override
public void configure() throws Exception {
from("restlet:http://0.0.0.0:8192/sample").setBody(
constant("Simples Assim!"));
}
}
beans.xml
That simple.
Edited by: fribeiro on Dec 27, 2010 7:22 PM
-
4. Re: "No component found" Issue in 4.3.0-fuse-03-00
How did you deploy your route ?
Please make sure you deploy it after the install the camel-restlet feature.
-
5. Re: "No component found" Issue in 4.3.0-fuse-03-00
I certainly did.
Please note it may take a few restarts for the error to be thrown.
-
7. Re: "No component found" Issue in 4.3.0-fuse-03-00
Ok, only restart to see this problem means that the camel-restlet bundle not fully get started before your customer bundle started.
The solution could be in your beans.xml of customer bundle, import an OSGi service exposed by camel-restlet bundle.
FYI, camel-restlet expose an OSGi service which implements interface
org.apache.camel.spi.ComponentResolver
and using property
component = restlet
This way can ensure your customer bundle always started after camel-restlet bundle started.
Freeman
-
8. Re: "No component found" Issue in 4.3.0-fuse-03-00
Is this what you mean?
doesn't do the trick either.
-
9. Re: "No component found" Issue in 4.3.0-fuse-03-00
No, what I mean is using spring-dm or blueprint syntax(no much difference actually) to import OSGi service, something like(with spring-dm syntax)
<osgi:reference id="restlet" interface="org.apache.camel.spi.ComponentResolver"
cardinality="1..1" filter="(component=restlet)" />
You can google to get lots of material about OSGi service exporting/importing details, or take a look at , more importantly the "Importing a Service" chapter to know how is works
http://fusesource.com/docs/esb/4.3/esb_deploy_osgi/index.html
Freeman
-
-
11. Re: "No component found" Issue in 4.3.0-fuse-03-00
The issue seems to be resolved, thank you Freeman!
The updated bundle is at http://cid-edc5a8d96d9a227c.office.live.com/self.aspx/Public/sampleroute-1.0.jar.
-
12. Re: "No component found" Issue in 4.3.0-fuse-03-00
I have a few questions here.
1. Is this the expected behavior, or should all components actually be available before any routes are built? Should it be reported as a bug and/or an improvement?
2. I had worked around the issue by accessing the endpoint in Java code (getEndpoint("restlet")), how does it work there?
3. How exactly does the import in question fix the issue?
-
13. Re: "No component found" Issue in 4.3.0-fuse-03-00
I've created an issue at https://issues.apache.org/jira/browse/CAMEL-3517.
-
14. Re: "No component found" Issue in 4.3.0-fuse-03-00
Freeman why doesn't all Camel features and bundles not have a lower starting number than any end user bundle.
We should really have runtime and framework bundles start before any end user application.
For example I would have preferred that bundle starting level 0-99 was reserved for Karaf and frameworks. So any end user application has a higher starting level as its 100+.
Then camel-restlet would be started before end user application.