Weld 1.1 + Solder causing unsatisfied dependencies?

352 Views Asked by At

I was experiencing weird occurences of "WELD-001408 Unsatisfied dependencies".

By all rules and docs, the dependency should be resolved. It was normal @Produces method and @Inject in some other bean.

@Produces @ApplicationScoped public Properties getEntityManagerFactoryProperties(){
    ...
}

@Inject
private Properties emfProperties;

Now I tried to upgrade from Weld 1.1.13 to 2.0.1, and started getting "WELD-001332 BeanManager method getBeans() is not available during application initialization", which is described in SOLDER-339.

Is it possible that solder is the culprit of the weird unsatisfied dependencies?

1

There are 1 best solutions below

1
On

Probably. We haven't been doing anything with Solder for over a year. Is there something you need from it which isn't in DeltaSpike?

EDIT: Yes, Solder does not work with Weld 2.0, there hasn't been any serious work on it for over a year. Efforts from the Seam team are being put into DeltaSpike. The vast majority of what you were using in Solder is now in DeltaSpike Core.