Next pull request introduces ApiContext which we can port to.  IMHO this is
the way to go back and eliminate a lot of calls like this.

On Tuesday, April 9, 2013, Andrew Phillips wrote:

> In
> apis/elasticstack/src/test/java/org/jclouds/elasticstack/ElasticStackClientLiveTest.java:
>
> > @@ -87,7 +85,7 @@ public void setupContext() {
> >        super.setupContext();
> >        imageId = view.getComputeService().templateBuilder().build().getImage().getId();
> >
> > -      client = view.unwrap(ElasticStackApiMetadata.CONTEXT_TOKEN).getApi();
> > +      client = view.utils().injector().getInstance(ElasticStackClient.class);
>
> I know this is a test, so this really doesn't matter, but would it make
> sense to add some kind of unwrapToApi method to View too? Or is the idea
> to replace contexts with APIs completely in the end?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jclouds/jclouds/pull/1508/files#r3721597>
> .
>