[
https://issues.apache.org/activemq/browse/CAMEL-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42852#action_42852
]
Claus Ibsen commented on CAMEL-525:
-----------------------------------
Damm the anwser is right before my eyes.
Glenn you swallow the exception yourself in your run method()
{code}
public static void main(String[] args) {
CamelSample2 cs = new CamelSample2();
try {
cs.run();
} catch (Exception e) {
}
}
{code}
You should remove the catch block
{code}
public static void main(String[] args) throws Exception {
CamelSample2 cs = new CamelSample2();
cs.run();
}
{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.
