Now in Switchyard the CDI discovery and the SY application events (e.g. service registration) have independent lifecycles. CDI discovery happens first and beans are initialized before SY services are registered. This isn't a problem for SY applications unless you try to use SY services based on the CDI lifecycle, which is what happens when I try to invoke a service in the bean's constructor or even an @PostConstruct method. The best path forward is probably for bean service activator to push a CDI event when a service has been completely started - at this point the services and service references are available. In this case users could then add an @Observes method to bean service which performs the invocation based on the start event.