Does annotating a bean @DependsOn mean that the dependent bean will be instantiated or initialized?

I am using Spring 3.0.2. I have two relatively simple bean definitions. One has a @PostConstruct(bean 'A') which fires a series of events that need to prepare the @DependsOn bean(bean 'B'). However, even though I said bean 'A' depends on bean 'B', it seems that bean 'A''s events (lifecycle methods) are run before bean 'B' is fully initialized.

Does declaring a bean to be "dependent" (or, for that matter, dependent on the bean definition) via @DependsOn means that the lifecycle methods of that dependent bean will complete before the bean that depends on it?

Will the lifecycle methods of Bean 'B' complete before Bean 'A'?

renew

Bean A is a custom class that uses a JMS template to send a message announcing that it has been initialized.

The receiver of said message processes it and forwards its configuration to the MessageListeningContainer (Bean B).

The first part happens before Bean B is started by DefaultLifecycleProcessor.

@Component
@DependsOn("beanB")
public class BeanA {
    @PostConstruct
    public void init() {
        // do stuff
    }
}

<bean id="beanB" class="org.springframework.jms.listener.DefaultMessageListenerContainr">
    <!-- other configuration -->
</bean>

I added the injection of bean b in the init method along with two logging statements:

container.isRunning();
container.isActive();

I looked at the spring source and after the initialization method (doInitialized is done), isActive is set to true. After doStart completes, isRunning is set. doStart is triggered by DefaultLifecycleProcessor, which happens after the @PostConstruct annotated method is called.

How can I guarantee that my Postconstruct method is called AFTER bean b, and has been initialized and started?