5:56 p.m.
Hi all,
This topic (modifying bean meta data at runtime) has been coming and going
since CDI 1.0.
As we are moving to Java SE with potentially more dynamic env, I think
interesting to see if there is a real need to explore it.
It's a very disruptive feature and obviously costly to add to the spec, so
I think we should start gathering proof that it would bring more power and
new usage to CDI before discussing all the problems it could raise.
I propose to g that way:
1) Launch a public consultation to ask our user if they are interested and
more than all give use real use case where it would solve a problem
2) Analyse these use cases to see if they are real or as some people think
are only a lack of knowledge of the spec
3) From there we could either left this aside if nothing relevant comes out
or start discussing the constraint around this feature.
Wdyt?
Antoine
8:55 p.m.
Hi,
On Thu, Aug 27, 2015 at 5:56 PM, Antoine Sabot-Durand
<antoine(a)sabot-durand.net> wrote:
This topic (modifying bean meta data at runtime) has been coming and
going
since CDI 1.0.
Does this also mean that Bean<T> instances can be registered at runtime?
If so, there's maybe one common use, although it's a pretty restricted
version of "runtime"; the ability to register a Bean<T> and/or do
other things extensions typically do from a ServletContainerListener.
The reason to do those things from a ServletContainerListener is that
the ServletContext is available then, which in turn allows one to read
WEB-INF/web.xml. There are a number of requests to have the
ServletContext made available in extensions, but that's clearly very
difficult to do.
So if the ServletContext can't come to extensions, maybe extensions
can be brought to the ServletContext via this way?
Kind regards,
Arjan Tijms
9:19 p.m.
Yes, I guess it's the same limitation raised by JAX-RS regarding CDI
integration: when they are up, it's too late. Now perhaps this use case
could be addressed by adding a way to wait for servlet initialization
before triggering AfterDeploymentValidation event.
Le jeu. 27 août 2015 à 20:55, arjan tijms <arjan.tijms(a)gmail.com> a écrit :
Hi,
On Thu, Aug 27, 2015 at 5:56 PM, Antoine Sabot-Durand
<antoine(a)sabot-durand.net> wrote:
> This topic (modifying bean meta data at runtime) has been coming and
going
> since CDI 1.0.
Does this also mean that Bean<T> instances can be registered at runtime?
If so, there's maybe one common use, although it's a pretty restricted
version of "runtime"; the ability to register a Bean<T> and/or do
other things extensions typically do from a ServletContainerListener.
The reason to do those things from a ServletContainerListener is that
the ServletContext is available then, which in turn allows one to read
WEB-INF/web.xml. There are a number of requests to have the
ServletContext made available in extensions, but that's clearly very
difficult to do.
So if the ServletContext can't come to extensions, maybe extensions
can be brought to the ServletContext via this way?
Kind regards,
Arjan Tijms
3172
days inactive
3172
days old
2 comments
2 participants
participants (2)
-
Antoine Sabot-Durand -
arjan tijms