10:23 p.m.
It seems that CDI.current is failing in places where it used to succeed.
The scenarios seem to all be the same - JAR files that don't contain a beans.xml when
used in SE mode can no longer invoke CDI.current. In the past they could.
Caused by: java.lang.IllegalStateException: Unable to access CDI
at javax.enterprise.inject.spi.CDI.lambda$getCDIProvider$1(CDI.java:75)
at java.util.Optional.orElseThrow(Optional.java:290)
at javax.enterprise.inject.spi.CDI.getCDIProvider(CDI.java:75)
at javax.enterprise.inject.spi.CDI.current(CDI.java:51)
at
ws.ament.hammock.rest.resteasy.Cdi11InjectorFactory.lookupBeanManager(Cdi11InjectorFactory.java:32)
I'll raise an issue, but not sure since this was something not specified previously.
John
________________________________
NOTICE: This e-mail message and any attachments may contain confidential, proprietary,
and/or privileged information which should be treated accordingly. If you are not the
intended recipient, please notify the sender immediately by return e-mail, delete this
message, and destroy all physical and electronic copies. Thank you.
10:15 a.m.
Hi John,
could you provide more details (CDI impl, packaging, etc.)? Ideally a
link to a hammock test or something like that? I think this should work.
Martin
Dne 22.12.2016 v 22:23 John Ament napsal(a):
It seems that CDI.current is failing in places where it used to
succeed.
The scenarios seem to all be the same - JAR files that don't contain a
beans.xml when used in SE mode can no longer invoke CDI.current. In the
past they could.
Caused by: java.lang.IllegalStateException: Unable to access CDI
at javax.enterprise.inject.spi.CDI.lambda$getCDIProvider$1(CDI.java:75)
at java.util.Optional.orElseThrow(Optional.java:290)
at javax.enterprise.inject.spi.CDI.getCDIProvider(CDI.java:75)
at javax.enterprise.inject.spi.CDI.current(CDI.java:51)
at
ws.ament.hammock.rest.resteasy.Cdi11InjectorFactory.lookupBeanManager(Cdi11InjectorFactory.java:32)
I'll raise an issue, but not sure since this was something not specified
previously.
John
------------------------------------------------------------------------
NOTICE: This e-mail message and any attachments may contain
confidential, proprietary, and/or privileged information which should be
treated accordingly. If you are not the intended recipient, please
notify the sender immediately by return e-mail, delete this message, and
destroy all physical and electronic copies. Thank you.
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
Note that for all code provided on this list, the provider licenses the code under the
Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other
ideas provided on this list, the provider waives all patent and other intellectual
property rights inherent in such information.
--
Martin Kouba
Software Engineer
Red Hat, Czech Republic
1:04 p.m.
It actually looked to be a bad classpath. So nevermind.
________________________________
From: Martin Kouba <mkouba(a)redhat.com Sent:
Monday, January 2, 2017 4:15 AM
To: John Ament; cdi-dev
Subject: Re: [cdi-dev] Regression issue with CDI.current
Hi John,
could you provide more details (CDI impl, packaging, etc.)? Ideally a
link to a hammock test or something like that? I think this should work.
Martin
Dne 22.12.2016 v 22:23 John Ament napsal(a):
lists.jboss.org
List to discuss the development of CDI (the specification) To see the collection of prior
postings to the list, visit the cdi-dev Archives.
www.apache.org
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND
CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION. 1. Definitions.
--
Martin Kouba
Software Engineer
Red Hat, Czech Republic
________________________________
NOTICE: This e-mail message and any attachments may contain confidential, proprietary,
and/or privileged information which should be treated accordingly. If you are not the
intended recipient, please notify the sender immediately by return e-mail, delete this
message, and destroy all physical and electronic copies. Thank you.
It seems that CDI.current is failing in places where it used to
succeed.
The scenarios seem to all be the same - JAR files that don't contain a
beans.xml when used in SE mode can no longer invoke CDI.current. In the
past they could.
Caused by: java.lang.IllegalStateException: Unable to access CDI
at javax.enterprise.inject.spi.CDI.lambda$getCDIProvider$1(CDI.java:75)
at java.util.Optional.orElseThrow(Optional.java:290)
at javax.enterprise.inject.spi.CDI.getCDIProvider(CDI.java:75)
at javax.enterprise.inject.spi.CDI.current(CDI.java:51)
at
ws.ament.hammock.rest.resteasy.Cdi11InjectorFactory.lookupBeanManager(Cdi11InjectorFactory.java:32)
I'll raise an issue, but not sure since this was something not specified
previously.
John
------------------------------------------------------------------------
NOTICE: This e-mail message and any attachments may contain
confidential, proprietary, and/or privileged information which should be
treated accordingly. If you are not the intended recipient, please
notify the sender immediately by return e-mail, delete this message, and
destroy all physical and electronic copies. Thank you.
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
cdi-dev Info Page - JBoss
Developer<https://lists.jboss.org/mailman/listinfo/cdi-dev
Note that for all code provided on this list, the provider licenses the code under the
Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other
ideas provided on this list, the provider waives all patent and other intellectual
property rights inherent in such information.
Apache License, Version
2.0<http://www.apache.org/licenses/LICENSE-2.0.html
2670
days inactive
2682
days old
2 comments
2 participants
participants (2)
-
John Ament -
Martin Kouba