Seam doesn't inject components when using a custom ServletCo

[jdjasperson]

I have a non-Seam component that implements the ServletContextListener interface that is dependent upon Seam components being injected. However, it appears that Seam hasn't fully activated any contexts at the time that my Listener is called from the container.

This is a major problem for me and causes me to question using Seam since I will now have to refactor my previously Seamed components to work in a non-Seam environment...these components are infrastructural in nature (PersistenceFacade, etc) ..so if I have to go through the hassle of constructing them normally, why use Seam?

If anyone has a workaround, this would be great. The @Startup annotation might be helpful, but it only guarantees construction, not execution.

[paulconnor]

I'm in a similar spot and am trying out Component.getInstance() with (currently) mixed results.

[nickarls]

Could you start a thread that would execute every 10 seconds until you notice that Seam has been initialized? Then it would do its magic and exit. I'm sure there is some static boolean isInitialized() somewhere if you dig through the api. Or just try to access some well known component.

[shane.bryzak]

Aren't the listeners executed in the order that they are listed in web.xml? If this is the case, then simply list your listener after SeamListener, so that when it is invoked Seam has already been initialized.