[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[glassfish-dev] Help needed in explaining why jakarta.el-api.version=4.0.0-RC2 causes com.sun.enterprise.module.ResolveError: Failed to start
|
Hi,
I opened el-ri/issues/130 [1] for the failure mentioned in [2]. The
theory as I recall, is that after GlassFish (master branch) upgraded to
jakarta.el-api.version=4.0.0-RC2, the following problem started occurring:
"
Could not load descriptor SystemDescriptor(
implementation=org.glassfish.jdbc.config.JdbcConnectionPoolInjector
name=jdbc-connection-pool
Caused by: com.sun.enterprise.module.ResolveError: Failed to start
OSGiModuleImpl...
"
Please see [2] for more of the exception call stack.
[1] is now closed as not related to the [2] described exception.
Is it possible that jakarta.el-api.version=4.0.0-RC2 is fine but that
something else went wrong in the GlassFish build that was being tested
with the jakartaee-tck?
Or is there a more specific reason why jakarta.el-api.version=4.0.0-RC2
is causing the com.sun.enterprise.module.ResolveError [2] failure?
If yes, could someone please help update [1] to describe that.
Thanks,
Scott
[1] https://github.com/eclipse-ee4j/el-ri/issues/130
[2] https://gist.github.com/scottmarlow/1dacd0f2d08c8e129b1702de0e74ddd3
[3]
https://github.com/eclipse-ee4j/glassfish/commit/a44fe7472d8c12ac624ffbbb016baf0b1d6f9676
