I think this list was meant more for what should/shouldn't be part of CDI Lite rather then whether those annotations should be housed in one specification or another.
I know it could be partially related in that having it moved would mean Lite doesn't need to do it.
I hear you, though the topic of the thread is "CDI future", not "What's in CDI Lite" ;) Hence why I took it to discuss the CDI Future and not just CDI Lite. Of course I realise most are eager to discuss CDI Lite as the next big future.
Apart from conceptual soundness, a practical reason to move some of these things is to evolve them. Given the current composition of the CDI team, I'm not sure people want to invest time in evolving Faces (JSF) or Servlet things. But maybe I'm wrong there.
Specifically for the injection of HttpServletRequest, there's the long running matter of *which* version of the HttpServletRequest is injected. The one as it enters the container? The one handed to the last Servlet (potentially wrapped by Filters), one as seen by an included resource? At the moment this is not at all clear, and containers essentially now just give you an arbitrary instance.
Kind regards,
Arjan Tijms
