I have a route defined in a Camel-based service unit like this:
from("direct:my-from-endpoint").process(new
DoSomething()).to("http://localhost:9099/sayHello";)In some cases, the sayHello web service is not running at the point when the Camel route inside the service unit is getting defined. In such cases, the service unit deployment fails because Camel encounters an exception: org.apache.camel.NoSuchEndpointException: No endpoint could be found for: http://localhost:9099/sayHello, please check your classpath contains the needed camel component jar. Is there a way to ignore this exception and only complain when this route actually gets used for messages rather than die at the point of creation? In our deployment scenario, it is not always possible for the web service in question to be ready when the Camel services are being created, but the service is always available by the time messages start passing through the system. -- View this message in context: http://old.nabble.com/Camek-1.6.x-w--ServiceMix---HTTP-%22no-endpoint-could-be-found%22-tp27412165p27412165.html Sent from the Camel - Users mailing list archive at Nabble.com.
