Hi Lakmali, You can mark the service as a "ListenerManagerRequiredServices", the the server won't startup until the osgi service is available ...
On Thu, Jul 25, 2013 at 12:19 PM, Lakmali Baminiwatta <[email protected]>wrote: > Hi all, > > I have a requirement to publish some internal APIs at the server startup. > We are planing to use the Publisher API for this. So in order to call > Publisher API, the publisher web app should be available and in that case, > the server should have been started. > > We thought of writing a new OSGI component, which will activate after the > server has started. I noticed that there are some components already there > which always get activated after the server is started. > > ex: In API Manager, ThriftAuthenticationServiceComponent[1] activate > method get invoked after the server has started (ie : server is accessible > at that point). > > I added all the @src references available in the > ThriftAuthenticationServiceComponent to a new component which I wrote. But > the new component starts before the server start completion. So I am unable > to find the reason which makes the ThriftAuthenticationServiceComponent > startup to happen last. > > Is there a way to make a component to start after the server startup is > completed? > > > [1] > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/identity/org.wso2.carbon.identity.thrift.authentication/src/main/java/org/wso2/carbon/identity/thrift/authentication/internal/ThriftAuthenticationServiceComponent.java > > Thanks, > Lakmali > > > > > > > -- > Lakmali Baminiwatta* > * > Software Engineer > WSO2, Inc.: http://wso2.com > lean.enterprise.middleware > mobile: +94 71 2335936 > blog : lakmali.com > * > * > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Thanks, Shariq. Phone: +94 777 202 225
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
