Eclipse Community Forums: Virgo » When does Virgo register the ApplicationContext service?

Home » Eclipse Projects » Virgo » When does Virgo register the ApplicationContext service?(get the service reference to ApplicationContext in Activator return null)

Show: Today's Messages :: Show Polls :: Message Navigator

When does Virgo register the ApplicationContext service? [message #632733]

Thu, 14 October 2010 06:22

guofeng zhang

Messages: 49
Registered: July 2009

Member

I used the following code in Activator to get a reference to ApplicationContext:

ServiceReference[] appContext = context.getAllServiceReferences("org.springframework.context.ApplicationContext", "(org.springframework.context.service.name=org.planner.service.member.management.implx)");

But the returned value is null.

Has Virgo not yet registered the service when Activator.start() is called, or is there any bug in the above code?

Report message to a moderator

Re: When does Virgo register the ApplicationContext service? [message #632734 is a reply to message #632733]

Thu, 14 October 2010 06:24

guofeng zhang

Messages: 49
Registered: July 2009

Member

The above code is to get the ApplicationContext service registered by its bundle.

Report message to a moderator

Re: When does Virgo register the ApplicationContext service? [message #632776 is a reply to message #632734]

Thu, 14 October 2010 09:04

guofeng zhang

Messages: 49
Registered: July 2009

Member

From the Virgo log, the Activator.start() is called before OsgiBundleXmlApplicationContext is loaded, so the ApplicationContext service is registered later than the call to Activator.start().

Write a class that implements "ApplicationContextAware" and define this class inside the application context is safe to get the instance of ApplicationContext.

Report message to a moderator

Re: When does Virgo register the ApplicationContext service? [message #632790 is a reply to message #632776]

Thu, 14 October 2010 09:41

Glyn Normington

Messages: 1222
Registered: July 2009

Senior Member

You seem to have answered your own question. Well done! Smile

The Spring DM extender in Virgo kicks in when the bundle STARTED event is broadcast, which is after any bundle activator has returned.

Note that for bundle artifacts deployed by Virgo, Virgo tracks the completion of both the synchronous portion of the start, which includes calling any bundle activator, and the asynchronous portion of the start, which includes the Spring DM extender building any application context and publishing it in the service registry, and only when both these have completed successfully changes the bundle install artifact state (visible on the admin console and elsewhere) from STARTING to ACTIVE. If either fail, there is appropriate error handling and diagnostics. If the asynchronous portion takes an extended time, then warnings are issued periodically.

Report message to a moderator

Previous Topic:	can't import groovy-all bundle
Next Topic:	Error on startup for Virgo M6

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 15:26:58 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter