[
https://issues.apache.org/jira/browse/TOMEE-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed TOMEE-3968.
----------------------------------
Resolution: Won't Fix
Closing as obsolete: TomEE 9.x (jakarta namespace) has shipped long ago and
this item from the migration umbrella (TOMEE-3862) saw no activity since 2022.
Please open a new issue if still relevant for current versions.
> Additionally scan for j"avax.enterprise.inject.spi.Extension"
> -------------------------------------------------------------
>
> Key: TOMEE-3968
> URL: https://issues.apache.org/jira/browse/TOMEE-3968
> Project: TomEE
> Issue Type: Sub-task
> Components: TomEE Core Server
> Affects Versions: 9.0.0-M7
> Reporter: Richard Zowalla
> Priority: Major
>
> Currently, TomEE 9.x only scans for "META-
> INF/services/jakarta.enterprise.inject.spi.Extension".
> This breaks, if 3rd party artifacts do not correctly relocate their
> "META-INF/services" files and still deliver
> "javax.enterprise.inject.spi.Extension". While we can fix that via PRs
> in OSS projects, it might be a problem in the wild.
> To compensate this for our users, i.e.
> - Additionally scan for "javax.enterprise.inject.spi.Extension"
> - If we find something, log a warning/info that this is not really
> expected (?) and load the extension instead of failing with an
> unsatisfied dependency error later.
> Note, that we also rewrite javax to jakarta in XML files on the fly, so
> it would probably be consistent to also scan for javax.enterprise.injec
> t.spi.Extension" but I would like to hear some opinions on i
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
