You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
| Online: | 4 Members of 12451 |
Work in progress list of enhancements to for the CDI 1.0 maintenance release and CDI 1.1.
The spec is underdefined in section 7.3.6. Various clarifications are needed, including that:
We should remove this sentence: When the destroy() method is called, the container discards this internal reference and performs any cleanup required of state associated with the client or transaction.
EE6 introduced the @DataSourceDefinition annotation without telling anyone. We should say that if it is used on a class annotated @Alternative, then it is only activated if the alternative is enabled.
We could support use of @Inject FacesContext fc as an alternative to FacesContext.getCurrentInstance(). This does actually save typing since you don't have to keep calling getCurrentInstance() in each method.
Built-in injection of HttpServletRequest, HttpSession and ServletContext has been requested by users. I'm kinda lukewarm on this idea, since we're trying to get away from the use of direct access to these objects. OTOH, it is very helpful for framework developers, I suppose.
We should extend the built-in @ConversationScope to servlets. The big challenge here is figuring out the propagation rules.
Currently the conversation context is required to be active only from within the faces servlet. You can't (portably) access it from a servlet filter.