Start Stop annotation to be trigger the methods at Impl level.

[mcculls]

Originally reported on Google Code with ID 75

What steps will reproduce the problem?

In a PeaberryActivationModule :     bind(PriceManager.class).to(PriceManagerImpl.class).in(Scopes.SINGLETON);
bindService(PriceManager.class).export();

PriceManager.class only have the method
Object getSomething(Object arg);

PriceManagerImpl.class override it's interface method and add @Start void start() and
@Stop void stop() methods.

What is the expected output? What do you see instead?

Expect the methods with @Start and @Stop to be executed.
I tested it and I should declare the @Stop and @Start method at the interface level,
but I don't want my interface to allow such power method because there will be more
than 1 service that will be using the PriceManager Singleton.

What version of the product are you using? On what operating system?
Peaberry 1.3 on windows 7.

Please provide any additional information below.

To get the expected result, I add a third line as follow :         bind(PriceManager.class).to(PriceManagerImpl.class).in(Scopes.SINGLETON);
bindService(PriceManager.class).export();

// Allow the @Start and @Stop to trigger.
bind(PriceManagerImpl.class).in(Scopes.SINGLETON);

Is it possible to allow @Start and @Stop method to be ran on both side ?

Reported by leclerc.luc on 2012-12-11 16:28:00

[mcculls]

I tried to switch the type in the form, from "Defect" to "Feature", but it seems to
have be stuck to Defect...

Reported by leclerc.luc on 2012-12-11 17:16:53