camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-511) A method ala afterPropertiesSet() for programmatic validation that the endpoint is configured correctly
Date Tue, 20 Jan 2009 18:19:59 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-511.
-------------------------------

    Resolution: Won't Fix

> A method ala afterPropertiesSet() for programmatic validation that the endpoint is configured
correctly
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-511
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-511
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Claus Ibsen
>             Fix For: 2.0.0
>
>
> Currently the validation that certain properties is mandatory / optional and that they
value is validated is handled ad-hoc by each endpoint or component.
> There should be somekind of support from camel-core that creates these objects that it
has a callback method to allow the programmer of the component/endpoint to do some programmatic
validation that the endpoint is in a validate state before its let's loose on the playground.
> In spring this method is named afterPropertiesSet() AFAIR. We could have a similar callback
method in camel-core for this.
> We could also start to use somekind of annotations to mark what properties the endpoint/component
support and which is mandatory/optional - kinda like the stuff for the Camel DSL.
> I think there is a ticket for this already.

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


Mime
View raw message