Skip to content

CDI extension should not require the PAX CDI capability for WeavingHook to apply [PAXCDI-215] #260

@ops4j-issues

Description

@ops4j-issues

Antonin Stefanutti created PAXCDI-215

In PAX CDI Weld, the ProxyWeavingHook hook adds the required dynamic imports for Weld classes in case a bundle requires the PAX CDI capability (org.ops4j.pax.cdi.extension).

However, for CDI extension bundle, that leads to having an empty CDI container started when the CDI extension bundle is deployed.

A better approach is to apply the weaving logic for CDI extension that instead provides a PAX CDI capability.


Affects: 1.0.0
Fixed in: 1.1.4
Votes: 0, Watches: 1

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions