You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2019/07/06 09:49:00 UTC
[jira] [Updated] (CAMEL-13730) NotifyBuilder MockComponent methods
are deprecated and there is no replacement
[ https://issues.apache.org/jira/browse/CAMEL-13730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-13730:
--------------------------------
Fix Version/s: (was: 3.0.0.M4)
3.0.0.M5
> NotifyBuilder MockComponent methods are deprecated and there is no replacement
> ------------------------------------------------------------------------------
>
> Key: CAMEL-13730
> URL: https://issues.apache.org/jira/browse/CAMEL-13730
> Project: Camel
> Issue Type: Task
> Components: camel-test
> Affects Versions: 3.x
> Reporter: Dmitry Shultz
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.0.0, 3.0.0.M5
>
>
> Several methods of the NotifyBuilder that receive MockComponent as a parameter are deprecated and are going to be removed from version 3+, but there is no viable replacement at the moment.
> From related email conversation ([http://mail-archives.apache.org/mod_mbox/camel-users/201907.mbox/%3CMWHPR11MB138984E7FFB0DA82C043F4F395FA0%40MWHPR11MB1389.namprd11.prod.outlook.com%3E]):
> Claus> Well we can take a look at adding some kind of SPI interface that advice with can use and then mock implement that.
> And then potentially other components can be used too (in theory).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)