Ok, so here's the error that keeps the TomEE MicroProfile, Plus and Plume examples from booting.
It appears we get an AmbiguousResolutionException from OpenWebBeans because we
have these two beans getting picked up and they conflict with each other:
- TomEEOpenAPIExtension, WebBeansType:EXTENSION, Name:null, API
Types:[java.lang.Object,javax.enterprise.inject.spi.Extension,
org.apache.tomee.microprofile.config.TomEEOpenAPIExtension,
org.apache.geronimo.microprofile.openapi.cdi.GeronimoOpenAPIExtension],
Qualifiers:[javax.enterprise.inject.Default,javax.enterprise.inject.Any]
from
jar:file:/Users/dblevins/.m2/repository/org/apache/tomee/mp-common/8.0.5-SNAPSHOT/mp-common-8.0.5-SNAPSHOT.jar
!/org/apache/tomee/microprofile/config/TomEEOpenAPIExtension.class
- GeronimoOpenAPIExtension, WebBeansType:EXTENSION, Name:null, API
Types:[java.lang.Object,javax.enterprise.inject.spi.Extension,
org.apache.geronimo.microprofile.openapi.cdi.GeronimoOpenAPIExtension],
Qualifiers:[javax.enterprise.inject.Default,javax.enterprise.inject.Any]
from
jar:file:/Users/dblevins/.m2/repository/org/apache/geronimo/geronimo-openapi-impl/1.0.12/geronimo-openapi-impl-1.0.12.jar
!/org/apache/geronimo/microprofile/openapi/cdi/GeronimoOpenAPIExtension.class
It looks like TomEEOpenAPIExtension was added in this commit:
-
https://github.com/apache/tomee/commit/10265708029ab2d0576f03aa1d5bb0a8a20bfffd
Jon, looks like you added TomEEOpenAPIExtension. Is there any trick you needed
to do to avoid the above conflict in our standalone servers?
If anyone has any insight, it's very appreciated. This can be reproduced with
this example:
-
https://github.com/apache/tomee/tree/master/examples/serverless-tomee-microprofile
-David
smime.p7s
Description: S/MIME cryptographic signature
