This content has been marked as final.
Show 3 replies
-
1. Re: start() and stop() methods in a MC bean
alesj Feb 23, 2009 5:18 AM (in response to jaikiran)"jaikiran" wrote:
But shouldn't those methods be skipped during start/stop, if they are annotated for something else - as in this example @InstallMethod.
Could be done, but it's just too custom for my taste. :-)
Since in this case you can simply do @Start(ignored=true). -
2. Re: start() and stop() methods in a MC bean
jaikiran Feb 23, 2009 5:26 AM (in response to jaikiran)"alesj" wrote:
Since in this case you can simply do @Start(ignored=true).
Yep, i could do that :) Infact i just renamed the methods:@InstallMethod public void onInstall() throws Exception { // do something }
The reason why i would except the MC to skip this start is because if someone is annotating it to be an @InstallMethod, then he is treating that as a MC bean and hence no longer a legacy MBean :) Nothing major though, since we know the workarounds. -
3. Re: start() and stop() methods in a MC bean
alesj Feb 23, 2009 5:32 AM (in response to jaikiran)"jaikiran" wrote:
The reason why i would except the MC to skip this start is because if someone is annotating it to be an @InstallMethod, then he is treating that as a MC bean and hence no longer a legacy MBean :)
Just more (useless) custom details.
What about if someone actually really wanted to have start called twice, at start and install? ;-)
@SkipThinkingThisIsPlainPOJOAndDoOldMBeanNotion :-)