camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Reopened] (CAMEL-3888) Tighten up @deprecated in camel-core to add more details what alternatives to use
Date Thu, 21 Apr 2011 13:50:05 GMT


Daniel Kulp reopened CAMEL-3888:

This is definitely not resolved.   There are a lot of tests that are using DefaultErrorHandlerBuilder.handled
which is marked deprecated.   So far, I haven't found any documentation about an alternative
to use.   THere are a bunch (22) of tests that use it and I haven't been able to figure out
any type of alternative for it.   Thus, IMO, if there isn't an alternative and is important
enough to be required by a bunch of tests, I have to wonder why it's deprecated.   But no
details on that either.

Similar situation for TryDefinition.handled.   Deprecated, no alternative.   For TryDefinition,
I could see a "rethrow()" or similar method added to define that behavior (which would match
the Java users expectation), but that certainly isn't there right now.

> Tighten up @deprecated in camel-core to add more details what alternatives to use
> ---------------------------------------------------------------------------------
>                 Key: CAMEL-3888
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.7.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.8.0
> We should ensure all deprecated classes/methods in camel-core is documented what alternatives
to use. Also if possible give a hint when it could be removed.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message