use CompletionStage instead of Future in java doc classes (#22472)

* use CompletionStage instead of Future in FactorialBackend.java #22393

* use CompletionStage instead of Future in FactorialBackend.java #22393 2
This commit is contained in:
ortigali 2017-03-14 15:51:44 +05:00 committed by Patrik Nordwall
parent eaf50405ab
commit db0a473cd5
23 changed files with 67 additions and 146 deletions

View file

@ -2,14 +2,14 @@ package docs.camel;
import java.util.HashMap;
import java.util.Map;
import java.util.concurrent.CompletionStage;
import akka.testkit.JavaTestKit;
import scala.concurrent.Future;
import akka.actor.ActorRef;
import akka.actor.ActorSystem;
import akka.actor.Props;
import akka.camel.CamelMessage;
import akka.pattern.Patterns;
import akka.pattern.PatternsCS;
public class ProducerTestBase {
public void tellJmsProducer() {
@ -29,7 +29,7 @@ public class ProducerTestBase {
ActorSystem system = ActorSystem.create("some-system");
Props props = Props.create(FirstProducer.class);
ActorRef producer = system.actorOf(props,"myproducer");
Future<Object> future = Patterns.ask(producer, "some request", 1000);
CompletionStage<Object> future = PatternsCS.ask(producer, "some request", 1000);
//#AskProducer
system.stop(producer);
JavaTestKit.shutdownActorSystem(system);