Overview
Other MyFaces Extensions
- ExtVal
- Ext-Script
- [Orchestra]
- [Portlet Bridge]
Community
Development
Sponsorship
Your browser does not support iframes
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
//... public class CustomWindowControllerBean2 { @Inject private WindowContext windowContext; //... public void finish() { this.windowContext.closeConversationGroup(WindowScoped.class); } } |
...
...
JSF 2.0 introduced new annotations as well as a new scope - the View Scope. CODI allows to use all the CDI mechanisms in beans annotated with:
javax.faces.bean.ApplicationScoped
javax.faces.bean.SessionScoped
javax.faces.bean.RequestScoped
javax.faces.bean.ViewScoped
Furthermore, the managed-bean annotation ( javax.faces.bean.ManagedBean
) is mapped to @Named
from CDI.
All these annotations are mapped automatically. So you won't face issues, if you import a JSF 2 annotation instead of the corresponding CDI annotation.
CODI provides a fine grained conversation scope with multiple parallel and isolated/independent conversations within a single window as well as a view-access scope (see above). So we (currently) don't think that we need a flash scope. Please contact us, if you find an use-case which needs the flash scope and you can't use the other CODI scopes. Other portable extensions (like Seam 3 btw. Seam-Faces) just provide this scope because they don't have such fine grained conversations.
...