[
https://issues.apache.org/activemq/browse/CAMEL-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42851#action_42851
]
Claus Ibsen commented on CAMEL-525:
-----------------------------------
I tried your code in the camel-jms component and also got the exception
{code}
org.apache.camel.NoSuchEndpointException: No endpoint could be found for:
test-jms4:queue:test.queue
at
org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:54)
public class Issue5252Test extends TestCase {
public void testXXX() throws Exception {
CamelContext context = new DefaultCamelContext();
ConnectionFactory connectionFactory = new ActiveMQConnectionFactory(
"vm://localhost?broker.persistent=false");
context.addComponent("test-jms",
JmsComponent.jmsComponentAutoAcknowledge(connectionFactory));
context.addRoutes(new RouteBuilder() {
public void configure() {
from("test-jms4:queue:test.queue").process(new Processor() {
public void process(Exchange e) {
System.out.println("This was called - Body: " +
e.getIn().getBody(String.class));
}
});
}
});
CamelTemplate template = new CamelTemplate(context);
context.start();
for (int i = 0; i < 3; i++) {
System.out.println("i is: " + i);
template.sendBody("test-jms:queue:test.queue", "" + i);
}
Thread.sleep(60000);
context.stop();
}
}
{code}
> Camel should throw a fatal exception if it can't resolve the component
> ----------------------------------------------------------------------
>
> Key: CAMEL-525
> URL: https://issues.apache.org/activemq/browse/CAMEL-525
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Glen Mazza
> Assignee: Claus Ibsen
> Priority: Minor
> Attachments: CamelSample2.java, pom.xml
>
>
> For that attached code, if I use the correct component URI prefix "test-jms"
> that I have registered, Camel runs fine:
> from("test-jms:queue:test.queue").process(new Processor() { ...
> [Registration done via:
> context.addComponent("test-jms",
> JmsComponent.jmsComponentAutoAcknowledge(connectionFactory));
> ]
> But if I misspell the component prefix (here, "test-jms4"), Camel halts with
> no output or feedback to the user informing him of the problem:
> from("test-jms4:queue:test.queue").process(new Processor() { ...
> No feedback about the problem is given in the log files either.
> I think in the from() and to() methods, Camel should be changed to throw an
> exception whenever it cannot resolve the component (i.e., if the user uses
> "test-jms4" instead of "test-jms", "cfx" instead of "cxf", etc.), not just
> halt silently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
