I try to wire a bean in my application, but while I know it gets created, I still get an exception.

This is perhaps the most common problem when working with Across modules. It usually has one of the following causes:

The bean gets created in another module and is not exposed.

The most likely fix here is to expose that bean. See the question Can I manually expose existing beans from another module? for more information.

The module that creates the bean is bootstrapped after the one that tries to access it.

This usually indicates that the module does not define its dependencies on other modules correctly.

In some cases a cyclic dependency can occur when changing dependencies. To prevent this, you can use @PostRefresh to retrieve the bean after the context has bootstrapped.