You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2010/07/07 18:43:51 UTC

[jira] Created: (CAMEL-2920) more eager validation of routes

more eager validation of routes 
--------------------------------

                 Key: CAMEL-2920
                 URL: https://issues.apache.org/activemq/browse/CAMEL-2920
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-core
    Affects Versions: 2.3.0
            Reporter: James Strachan
             Fix For: 2.4.0


it seems you can dynamically create invalid routes which don't fail fast if there are errors.

e.g.

{code}
from("seda:foo").beanRef("doesNotExist", "noMethodCalledThis")
{code}


its only if a message is sent to "seda:foo" that the whole thing barfs. We should maybe check that the to can be validated first before allowing the consumer to startup? If nothing else failing faster and earlier helps users spot errors sooner

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-2920) more eager validation of routes

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60494#action_60494 ] 

Claus Ibsen commented on CAMEL-2920:
------------------------------------

Yeah we should take a 2nd look at each processor and validate in the start method.

> more eager validation of routes 
> --------------------------------
>
>                 Key: CAMEL-2920
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2920
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.3.0
>            Reporter: James Strachan
>            Assignee: Claus Ibsen
>             Fix For: 2.4.0
>
>
> it seems you can dynamically create invalid routes which don't fail fast if there are errors.
> e.g.
> {code}
> from("seda:foo").beanRef("doesNotExist", "noMethodCalledThis")
> {code}
> its only if a message is sent to "seda:foo" that the whole thing barfs. We should maybe check that the to can be validated first before allowing the consumer to startup? If nothing else failing faster and earlier helps users spot errors sooner

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-2920) more eager validation of routes

Posted by "James Strachan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60538#action_60538 ] 

James Strachan commented on CAMEL-2920:
---------------------------------------

great stuff! :)

> more eager validation of routes 
> --------------------------------
>
>                 Key: CAMEL-2920
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2920
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.3.0
>            Reporter: James Strachan
>            Assignee: Claus Ibsen
>             Fix For: 2.4.0
>
>
> it seems you can dynamically create invalid routes which don't fail fast if there are errors.
> e.g.
> {code}
> from("seda:foo").beanRef("doesNotExist", "noMethodCalledThis")
> {code}
> its only if a message is sent to "seda:foo" that the whole thing barfs. We should maybe check that the to can be validated first before allowing the consumer to startup? If nothing else failing faster and earlier helps users spot errors sooner

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CAMEL-2920) more eager validation of routes

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60546#action_60546 ] 

Claus Ibsen commented on CAMEL-2920:
------------------------------------

trunk: 962451.

Method name is now also validated

> more eager validation of routes 
> --------------------------------
>
>                 Key: CAMEL-2920
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2920
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.3.0
>            Reporter: James Strachan
>            Assignee: Claus Ibsen
>             Fix For: 2.4.0
>
>
> it seems you can dynamically create invalid routes which don't fail fast if there are errors.
> e.g.
> {code}
> from("seda:foo").beanRef("doesNotExist", "noMethodCalledThis")
> {code}
> its only if a message is sent to "seda:foo" that the whole thing barfs. We should maybe check that the to can be validated first before allowing the consumer to startup? If nothing else failing faster and earlier helps users spot errors sooner

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CAMEL-2920) more eager validation of routes

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-2920.
--------------------------------

    Resolution: Fixed

bean and method call using ref now check on startup if the bean exists in the registry

trunk: 962430.

> more eager validation of routes 
> --------------------------------
>
>                 Key: CAMEL-2920
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2920
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.3.0
>            Reporter: James Strachan
>            Assignee: Claus Ibsen
>             Fix For: 2.4.0
>
>
> it seems you can dynamically create invalid routes which don't fail fast if there are errors.
> e.g.
> {code}
> from("seda:foo").beanRef("doesNotExist", "noMethodCalledThis")
> {code}
> its only if a message is sent to "seda:foo" that the whole thing barfs. We should maybe check that the to can be validated first before allowing the consumer to startup? If nothing else failing faster and earlier helps users spot errors sooner

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (CAMEL-2920) more eager validation of routes

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reassigned CAMEL-2920:
----------------------------------

    Assignee: Claus Ibsen

> more eager validation of routes 
> --------------------------------
>
>                 Key: CAMEL-2920
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2920
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.3.0
>            Reporter: James Strachan
>            Assignee: Claus Ibsen
>             Fix For: 2.4.0
>
>
> it seems you can dynamically create invalid routes which don't fail fast if there are errors.
> e.g.
> {code}
> from("seda:foo").beanRef("doesNotExist", "noMethodCalledThis")
> {code}
> its only if a message is sent to "seda:foo" that the whole thing barfs. We should maybe check that the to can be validated first before allowing the consumer to startup? If nothing else failing faster and earlier helps users spot errors sooner

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.